There an unique issue that i had come across while testing the APP V Visio package in UAT Phase,guys any help and insights would be appreciated from my end,the problem is described below.
Visio has an extension named .vsd when we launch the extension by creating a dummy file in the desktop the application seems to work fine which is the .vsd reads the necessay ProgIds and then it launches the file extension with visio.exe which is the correct exe.
But the problem is faced suppose we have a .vsd file in the sharepoint and then we use this virtual solution to click on this .vsd,while streaming of this application happens ,Word 2007 is opened and in the task manager one can see WinWord.exe.The following steps of how the testing is done is said below
When you click directly on the file and select edit…Word pops up with the same file conversion window as seen before… if you click out of that… and close Word… behind it there is another prompt to Open-Save-Cancel… if you click on open… it opens normally in Visio. When you click on the down arrow for the file and select “Edit with Microsoft Office Visio”… you see Word… then the same file conversion windows… this time when all is closed… the file does NOT come up in Visio… did see a window with the message “The document could not be opened for editing. A Windows SharePoint Services compatible application could not be found to edit the document”. and the following window popus up..

TroubleShooting Steps i had tried..

1 Had deleted all the instances of WinWord.exe form my App V Solution which were present in the virtual Registry.
2 Tried the Option "Merge with Local" for the .vsd resources but aint working.

0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity