Author |
Topic ![Next Topic Next Topic](icon_go_right.png) |
|
mugen
New Member
![](icon_star_green.gif)
7 Posts |
Posted - Nov 28 2023 : 02:12:59 AM
|
I have old license. I changed my computer system and reinstalled Windows. (Windos 10 Enterprise. version: 22H2, OS build 19045.3693, Korean)
I installed Visual Studio 2017 as usual and tried to install the VA_X 2283 version downloaded from the Archive, but it could not be installed.
![](https://forums.wholetomato.com/forum/uploaded/mugen/2023112815931_va-error-01.png) * (English) This extension is already installed on all applicable products.
![](https://forums.wholetomato.com/forum/uploaded/mugen/202311282413_va-error-02.png) * (English) 'VaDebuggerToolsPakage' package did not load properly.
![](https://forums.wholetomato.com/forum/uploaded/mugen/202311282424_va-error-03.png) * (English) 'Visual Assist' package did not load properly.
The following error remain in the activityLog of visual studio. -------------------------------- <entry> <record>379</record> <time>2023/11/28 06:26:45.756</time> <type>Error</type> <source>VisualStudio</source> <description>No InprocServer32 registered for package [Visual Assist]</description> <guid>{removed}</guid> <hr>8007007e</hr> <errorinfo></errorinfo> <path>\AppData\Local\Microsoft\VisualStudio\15.0_4f655589\Extensions\utrviazs.atf\VaPkgAsync.dll</path> </entry> --------------------------------
|
|
feline
Whole Tomato Software
![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif)
United Kingdom
18915 Posts |
Posted - Nov 28 2023 : 06:55:41 AM
|
VA 2283 loads without any problems for me, under Windows 10, with Visual Studio 2017. The first error, VA is already installed, is interesting. Which version number of VA is shown if you look for Visual Assist as an installed extension in the dialog:
IDE tools menu -> Extensions and Updates...
I am wondering if a different version is installed. Can you please try uninstalling VA from this dialog, which will require an IDE restart to take effect, then when you reload the IDE, see if VA is still listed as installed or not?
Assuming VA is no longer listed as installed, if you now run the installer again, do you still get the error about VA being already installed? If so please cancel the install and do a file search of your C drive for the file "VA_X.dll" and see if any instances show up. |
zen is the art of being at one with the two'ness |
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
mugen
New Member
![](icon_star_green.gif)
7 Posts |
Posted - Nov 28 2023 : 7:25:27 PM
|
Among the things I didn't mention, I have install new version from IDE's 'Extensions and Updates' and it worked normally. However, my license was not allowed, so I deleted it and tried to install 2283.
![](https://forums.wholetomato.com/forum/uploaded/mugen/2023112819517_va-error-04.png)
I tried uninstalling and reinstalling according to the guide, but the problem still occurs. Additionally, instances of VA_X.dll are not existed.
quote: Originally posted by feline
VA 2283 loads without any problems for me, under Windows 10, with Visual Studio 2017. The first error, VA is already installed, is interesting. Which version number of VA is shown if you look for Visual Assist as an installed extension in the dialog:
IDE tools menu -> Extensions and Updates...
I am wondering if a different version is installed. Can you please try uninstalling VA from this dialog, which will require an IDE restart to take effect, then when you reload the IDE, see if VA is still listed as installed or not?
Assuming VA is no longer listed as installed, if you now run the installer again, do you still get the error about VA being already installed? If so please cancel the install and do a file search of your C drive for the file "VA_X.dll" and see if any instances show up.
|
Edited by - mugen on Nov 28 2023 7:51:10 PM |
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
mugen
New Member
![](icon_star_green.gif)
7 Posts |
Posted - Nov 28 2023 : 7:55:32 PM
|
Also, there was a compatibility issue, so I installed it in Windows 7 mode.
quote: Originally posted by feline
VA 2283 loads without any problems for me, under Windows 10, with Visual Studio 2017. The first error, VA is already installed, is interesting. Which version number of VA is shown if you look for Visual Assist as an installed extension in the dialog:
IDE tools menu -> Extensions and Updates...
I am wondering if a different version is installed. Can you please try uninstalling VA from this dialog, which will require an IDE restart to take effect, then when you reload the IDE, see if VA is still listed as installed or not?
Assuming VA is no longer listed as installed, if you now run the installer again, do you still get the error about VA being already installed? If so please cancel the install and do a file search of your C drive for the file "VA_X.dll" and see if any instances show up.
|
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
mugen
New Member
![](icon_star_green.gif)
7 Posts |
Posted - Nov 28 2023 : 8:09:40 PM
|
I followed the guide below to completely uninstall the new version.
https://docs.wholetomato.com/default.asp?W388
quote: Originally posted by feline
VA 2283 loads without any problems for me, under Windows 10, with Visual Studio 2017. The first error, VA is already installed, is interesting. Which version number of VA is shown if you look for Visual Assist as an installed extension in the dialog:
IDE tools menu -> Extensions and Updates...
I am wondering if a different version is installed. Can you please try uninstalling VA from this dialog, which will require an IDE restart to take effect, then when you reload the IDE, see if VA is still listed as installed or not?
Assuming VA is no longer listed as installed, if you now run the installer again, do you still get the error about VA being already installed? If so please cancel the install and do a file search of your C drive for the file "VA_X.dll" and see if any instances show up.
|
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
mugen
New Member
![](icon_star_green.gif)
7 Posts |
Posted - Nov 28 2023 : 8:48:09 PM
|
I installed the latest version using the IDE's 'Extensions and Updates', and downloaded VA 2399, the last version of my license, through 'Revert' in the Visual Assist menu that appears after running the IDE. Similarly, if I run it, a crash occurs, so I attached this Windows Crash report file.
------------------------------------------------ Version=1 EventType=APPCRASH EventTime=133456954282228289 ReportType=2 Consent=1 UploadTime=133456954285541160 ReportStatus=268435456 ReportIdentifier=102e9b94-5539-4bc0-a434-7739394da84e IntegratorReportIdentifier=b51e9530-e522-4a64-a7dd-9c2b6b242798 Wow64Host=34404 Wow64Guest=332 NsAppName=VA_X_Setup2399_0.exe AppSessionGuid=00003da0-0001-000f-ec29-4e906422da01 TargetAppId=W:0006cf279011e9894ab0655fd6fbcb9841b300000904!0000593b50d227ea4a5f53773f5c761c07f2092bbaf8!VA_X_Setup2399_0.exe TargetAppVer=2021//01//26:00:23:49!28f0215!VA_X_Setup2399_0.exe BootId=4294967295 TargetAsId=6219 IsFatal=1 EtwNonCollectReason=4 Response.BucketId=c0bc1d10f68f72ec0bd2ef3f2ee427f5 Response.BucketTable=1 Response.LegacyBucketId=2004927838781974517 Response.type=4 Sig[0].Name=application name Sig[0].Value=VA_X_Setup2399_0.exe Sig[1].Name=application version Sig[1].Value=10.9.2399.0 Sig[2].Name=Application timestamp Sig[2].Value=600f6115 Sig[3].Name=fault module name Sig[3].Value=VA_X_Setup2399_0.exe Sig[4].Name=fault module version Sig[4].Value=10.9.2399.0 Sig[5].Name=fault module timestamp Sig[5].Value=600f6115 Sig[6].Name=exception code Sig[6].Value=c0000005 Sig[7].Name=exception offset Sig[7].Value=0000836b DynamicSig[1].Name=OS version DynamicSig[1].Value=10.0.19045.2.0.0.256.4 DynamicSig[2].Name=locale ID DynamicSig[2].Value=1042 DynamicSig[22].Name=Additional information 1 DynamicSig[22].Value=2beb DynamicSig[23].Name=Additional information 2 DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46 DynamicSig[24].Name=Additional information 3 DynamicSig[24].Value=4db1 DynamicSig[25].Name=Additional information 4 DynamicSig[25].Value=4db1143ed14b8699986099351e36ff6c UI[2]=C:\Users\Removed\Downloads\VA_X_Setup2399_0.exe LoadedModule[0]=C:\Users\Removed\Downloads\VA_X_Setup2399_0.exe LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\windows\System32\KERNEL32.DLL LoadedModule[3]=C:\windows\System32\KERNELBASE.dll LoadedModule[4]=C:\ProgramData\Symantec\Symantec Endpoint Protection\14.3.8268.5000.105\Data\Sysfer\x86\sysfer.dll LoadedModule[5]=C:\windows\System32\USER32.dll LoadedModule[6]=C:\windows\System32\win32u.dll LoadedModule[7]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.3636_none_a863d714867441db\COMCTL32.dll LoadedModule =C:\windows\System32\GDI32.dll LoadedModule[9]=C:\windows\System32\gdi32full.dll LoadedModule[10]=C:\windows\System32\msvcrt.dll LoadedModule[11]=C:\windows\System32\msvcp_win.dll LoadedModule[12]=C:\windows\System32\ucrtbase.dll LoadedModule[13]=C:\windows\System32\ADVAPI32.dll LoadedModule[14]=C:\windows\System32\sechost.dll LoadedModule[15]=C:\windows\System32\RPCRT4.dll LoadedModule[16]=C:\windows\System32\SHELL32.dll LoadedModule[17]=C:\windows\System32\ole32.dll LoadedModule[18]=C:\windows\System32\combase.dll LoadedModule[19]=C:\windows\System32\OLEAUT32.dll LoadedModule[20]=C:\windows\System32\psapi.dll LoadedModule[21]=C:\windows\System32\IMM32.DLL LoadedModule[22]=C:\windows\SYSTEM32\kernel.appcore.dll LoadedModule[23]=C:\windows\System32\bcryptPrimitives.dll LoadedModule[24]=C:\windows\system32\uxtheme.dll LoadedModule[25]=C:\windows\System32\MSCTF.dll LoadedModule[26]=C:\windows\System32\clbcatq.dll LoadedModule[27]=C:\ProgramData\Microsoft\VisualStudio\Setup\x86\Microsoft.VisualStudio.Setup.Configuration.Native.dll LoadedModule[28]=C:\windows\System32\SHLWAPI.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=19045 OsInfo[3].Key=ubr OsInfo[3].Value=3693 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1042 OsInfo[7].Key=geoid OsInfo[7].Value=134 OsInfo .Key=sku OsInfo .Value=4 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=256 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=222425424 OsInfo[15].Key=osinsty OsInfo[15].Value=2 OsInfo[16].Key=iever OsInfo[16].Value=11.3636.19041.0-11.0.1000 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=32437 OsInfo[19].Key=svolsz OsInfo[19].Value=475 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=191206 OsInfo[22].Key=bldtm OsInfo[22].Value=1406 OsInfo[23].Key=bldbrch OsInfo[23].Value=vb_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.19041.3693.amd64fre.vb_release.191206-1406 OsInfo[30].Key=buildflightid OsInfo[31].Key=edition OsInfo[31].Value=Enterprise OsInfo[32].Key=ring OsInfo[33].Key=expid OsInfo[34].Key=fconid OsInfo[35].Key=containerid OsInfo[36].Key=containertype OsInfo[37].Key=edu OsInfo[37].Value=0 FriendlyEventName=stopped working ConsentKey=APPCRASH AppName=Visual Assist Installer AppPath=C:\Users\Removed\Downloads\VA_X_Setup2399_0.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=55219C8802DECF76C642EEE4F77459B5 MetadataHash=-1734186446 ------------------------------------------------
quote: Originally posted by feline
VA 2283 loads without any problems for me, under Windows 10, with Visual Studio 2017. The first error, VA is already installed, is interesting. Which version number of VA is shown if you look for Visual Assist as an installed extension in the dialog:
IDE tools menu -> Extensions and Updates...
I am wondering if a different version is installed. Can you please try uninstalling VA from this dialog, which will require an IDE restart to take effect, then when you reload the IDE, see if VA is still listed as installed or not?
Assuming VA is no longer listed as installed, if you now run the installer again, do you still get the error about VA being already installed? If so please cancel the install and do a file search of your C drive for the file "VA_X.dll" and see if any instances show up.
|
Edited by - mugen on Nov 28 2023 8:56:12 PM |
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
feline
Whole Tomato Software
![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif)
United Kingdom
18915 Posts |
Posted - Nov 29 2023 : 07:23:44 AM
|
OK, lets try a different approach. I am going to explain how to install VA 2399 into a new, default test profile, which should give us a clean install, and tell us if this is a machine problem or a problem with your default profile.
Can you first download the VS2017 specific installer for Visual Assist from:
https://downloadfiles.idera.com/WholeTomato/VA_X_Setup2399_0.vsix
Next you will need extra details about the IDE install to create a test profile. To get these details, please open a Windows command prompt window, and inside the window run the command:
"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe"
There will be a set of lines for each different version of Visual Studio that you have installed. For the version you want to install into, you want the "productPath", "dispalyName" and "installationVersion" lines, e.g.
productPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe displayName: Visual Studio Professional 2017 installationVersion: 15.9.28307.1927
You can then use the information from these three lines to make sure that the following command has the correct command line parameters. The values are:
/appidname: = displayName: /appidinstallpath: = productPath: /skuVersion: = installationVersion:
The "/skuName:" value is one of "Community / Pro / Enterprise", note for the Professional version it is "Pro", not the expected "Professional".
The working command, for VS2017 Professional, using the values above, is - split into lines to make it easier to read and edit:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe" /appidinstallpath:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe" /skuName:Pro /appidname:"Visual Studio Professional 2017" /skuVersion:15.9.28307.1974 /rootSuffix:"VATest" "C:\Users\%USERNAME%\Downloads\VA_X_Setup2399_0.vsix"
The "rootSuffix" is the name of the test profile you want to install to, and this will be created if it does not already exist. The final parameter is the path of the VSIX installer for Visual Assist that you want to install. Once you have the command set up, the only parts you should need to edit are the skuVersion and the path to the VSIX file, can you please close all instances of Visual Studio and run this command.
Running this command installs VA into the test profile, but it does not load the test profile. If you created the test profile by installing VA, when you run the test profile it will be using the default IDE settings, without asking you which settings you want to use.
To now load the test profile you use the command:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest
To load your normal, default profile just load the IDE normally. To return to this test profile again, pass the /RootSuffix command line switch when loading the IDE. You can run both profiles at the same time, next to each other. In VS2019 and VS2022 the profile name will be shown just under the close button, in the top right hand corner of the main IDE window. If you export your IDE settings from your main profile you can them import them into the test profile.
Do you see any problems when running the test profile, or does VA load and work correctly? |
zen is the art of being at one with the two'ness |
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
mugen
New Member
![](icon_star_green.gif)
7 Posts |
Posted - Nov 29 2023 : 7:33:37 PM
|
I applied your guide and ran the command without including the 'rootSuffix' parameter as shown below. ----------------------------------------------------------- "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VSIXInstaller.exe" /appidinstallpath:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe" /skuName:Enterprise /appidname:"Visual Studio Enterprise 2017" /skuVersion:15.9.34118.181 "C:\Users\Removed\Downloads\VA_X_Setup2399_0.vsix" -----------------------------------------------------------
The installation was successful and I was able to enter my license. Everything is perfect.
Thank you for all your assistance.
quote: Originally posted by feline
OK, lets try a different approach. I am going to explain how to install VA 2399 into a new, default test profile, which should give us a clean install, and tell us if this is a machine problem or a problem with your default profile.
Can you first download the VS2017 specific installer for Visual Assist from:
https://downloadfiles.idera.com/WholeTomato/VA_X_Setup2399_0.vsix
Next you will need extra details about the IDE install to create a test profile. To get these details, please open a Windows command prompt window, and inside the window run the command:
"%ProgramFiles(x86)%\Microsoft Visual Studio\Installer\vswhere.exe"
There will be a set of lines for each different version of Visual Studio that you have installed. For the version you want to install into, you want the "productPath", "dispalyName" and "installationVersion" lines, e.g.
productPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe displayName: Visual Studio Professional 2017 installationVersion: 15.9.28307.1927
You can then use the information from these three lines to make sure that the following command has the correct command line parameters. The values are:
/appidname: = displayName: /appidinstallpath: = productPath: /skuVersion: = installationVersion:
The "/skuName:" value is one of "Community / Pro / Enterprise", note for the Professional version it is "Pro", not the expected "Professional".
The working command, for VS2017 Professional, using the values above, is - split into lines to make it easier to read and edit:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\VSIXInstaller.exe" /appidinstallpath:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe" /skuName:Pro /appidname:"Visual Studio Professional 2017" /skuVersion:15.9.28307.1974 /rootSuffix:"VATest" "C:\Users\%USERNAME%\Downloads\VA_X_Setup2399_0.vsix"
The "rootSuffix" is the name of the test profile you want to install to, and this will be created if it does not already exist. The final parameter is the path of the VSIX installer for Visual Assist that you want to install. Once you have the command set up, the only parts you should need to edit are the skuVersion and the path to the VSIX file, can you please close all instances of Visual Studio and run this command.
Running this command installs VA into the test profile, but it does not load the test profile. If you created the test profile by installing VA, when you run the test profile it will be using the default IDE settings, without asking you which settings you want to use.
To now load the test profile you use the command:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe" /RootSuffix VATest
To load your normal, default profile just load the IDE normally. To return to this test profile again, pass the /RootSuffix command line switch when loading the IDE. You can run both profiles at the same time, next to each other. In VS2019 and VS2022 the profile name will be shown just under the close button, in the top right hand corner of the main IDE window. If you export your IDE settings from your main profile you can them import them into the test profile.
Do you see any problems when running the test profile, or does VA load and work correctly?
|
Edited by - mugen on Nov 29 2023 7:34:15 PM |
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
feline
Whole Tomato Software
![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif) ![](icon_star_red.gif)
United Kingdom
18915 Posts |
Posted - Nov 30 2023 : 05:27:17 AM
|
Interesting, and thank you for the update. This suggests that the exe installer was having problems, but you might have been fine just double clicking the VSIX installer without using the command line.
I have now seen a few cases where older exe installers struggle on newer versions of Visual Studio, so I am guessing you had a similar, but much more sever form of that problem. |
zen is the art of being at one with the two'ness |
![Go to Top of Page Go to Top of Page](icon_go_up.png) |
|
|
Topic ![Next Topic Next Topic](icon_go_right.png) |
|
|
|