| T O P I C R E V I E W |
| dewtell |
Posted - May 21 2018 : 4:15:42 PM
After a reboot, I've suddenly started getting a message from Visual C++ 2013 that the Visual Assist package did not load correctly when I start up VC++.
Text of the message is:
-------
The 'Visual Assist' package did not load correctly.
The problem may have been caused by a configuration change or by the installation of another extension. You can get more information by examining the file '<personal path>\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml'.
Restarting Visual Studio could help resolve this issue.
-------
Restarting Visual Studio didn't help, because this message recurs when I restart, and when I attempt to access any feature on the VA menu, including trying to access the options. As a precaution, I downloaded the latest VA build (2270), installed that, and tried again - same result. The last portion of the above xml file, starting with the first reference to Whole Tomato is below. It looks like it might be related my recent activation of the Debugger Tools - but now I can't get to the VA option menu to turn this off, if this is the problem. Any ideas?
<entry>
<record>216</record>
<time>2018/05/21 19:13:13.854</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [WholeTomatoSoftware.VaDebuggerTools.VaDebuggerToolsPackage, VaDebuggerTools, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]</description>
<guid>{66D044CF-265F-4BEB-A428-3D37A0835DD5}</guid>
</entry>
<entry>
<record>217</record>
<time>2018/05/21 19:13:13.874</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function CVsPackageInfo::HrInstantiatePackage</description>
<guid>{C9DD4A57-47FB-11D2-83E7-00C04F9902C1}</guid>
</entry>
<entry>
<record>218</record>
<time>2018/05/21 19:13:13.874</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [Visual Studio Debugger]</description>
<guid>{C9DD4A57-47FB-11D2-83E7-00C04F9902C1}</guid>
</entry>
<entry>
<record>219</record>
<time>2018/05/21 19:13:13.874</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Loading UI library</description>
<guid>{C9DD4A57-47FB-11D2-83E7-00C04F9902C1}</guid>
<path>C:\Program Files (x86)\Microsoft Visual Studio 12.0\\Common7\Packages\Debugger\*\VSDebugUI.dll</path>
</entry>
<entry>
<record>220</record>
<time>2018/05/21 19:13:13.894</time>
<type>Information</type>
<source>VisualStudio</source>
<description>End package load [Visual Studio Debugger]</description>
<guid>{C9DD4A57-47FB-11D2-83E7-00C04F9902C1}</guid>
</entry>
<entry>
<record>221</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function VBDispatch::GetTypeLib</description>
</entry>
<entry>
<record>222</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Leaving function VBDispatch::GetTypeLib</description>
<guid>{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}</guid>
</entry>
<entry>
<record>223</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function VBDispatch::GetTypeLib</description>
</entry>
<entry>
<record>224</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Leaving function VBDispatch::GetTypeLib</description>
<guid>{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}</guid>
</entry>
<entry>
<record>225</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function VBDispatch::GetTypeLib</description>
</entry>
<entry>
<record>226</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Leaving function VBDispatch::GetTypeLib</description>
<guid>{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}</guid>
</entry>
<entry>
<record>227</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function VBDispatch::GetTypeLib</description>
</entry>
<entry>
<record>228</record>
<time>2018/05/21 19:13:13.944</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Leaving function VBDispatch::GetTypeLib</description>
<guid>{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}</guid>
</entry>
<entry>
<record>229</record>
<time>2018/05/21 19:13:14.165</time>
<type>Information</type>
<source>VisualStudio</source>
<description>End package load [WholeTomatoSoftware.VaDebuggerTools.VaDebuggerToolsPackage, VaDebuggerTools, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]</description>
<guid>{66D044CF-265F-4BEB-A428-3D37A0835DD5}</guid>
</entry>
<entry>
<record>230</record>
<time>2018/05/21 19:13:14.165</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function CVsPackageInfo::HrInstantiatePackage</description>
<guid>{44630D46-96B5-488C-8DF9-26E21DB8C1A3}</guid>
</entry>
<entry>
<record>231</record>
<time>2018/05/21 19:13:14.165</time>
<type>Error</type>
<source>VisualStudio</source>
<description>No InprocServer32 registered for package [Visual Assist]</description>
<guid>{44630D46-96B5-488C-8DF9-26E21DB8C1A3}</guid>
<hr>8007007e</hr>
<errorinfo></errorinfo>
<path>C:\Users\dave\AppData\Local\Microsoft\VisualStudio\12.0\Extensions\3stxtg15.swq\VaPkg.dll</path>
</entry>
</activity>
|
| 6 L A T E S T R E P L I E S (Newest First) |
| sean |
Posted - May 21 2018 : 7:23:03 PM
F-Secure and BitDefender were flagging it this morning and now they aren't, so at least for those two it seems like it was a false positive. |
| dewtell |
Posted - May 21 2018 : 7:19:35 PM
Using Vipre, and yes, the quarantine area shows 4 entries for Gen:Variant.Johnnie.100936, which is found in VaPkg.dll. Is this a known false alarm? I've tried restoring it from the quarantine temporarily, and Viper keeps flagging it and returning it to quarantine when I restart the IDE. The info page on the alleged virus is http://www.sunbeltsecurity.com/ThreatDisplay.aspx?name=Gen:Variant.Johnnie.100936&tid=5226159&cs=F0EEB9FA1FABDD7549B7C8D8651D960B
|
| sean |
Posted - May 21 2018 : 7:17:01 PM
It appears that both F-Secure and BitDefender no longer flag it, but 6 other products that VirusTotal checks against are still flagging the dll:
https://www.virustotal.com/en/file/38c52b4f36165b51265822cae3b39233157c81e8965c32c02c9a5d5b6fb1f0e6/analysis/1526944012/
|
| sean |
Posted - May 21 2018 : 7:00:42 PM
The error listed in the log is 8007007e with reference to VaPkg.dll.
Error Lookup reports that error as "The specified module could not be found. "
What antivirus do you have installed? Check its quarantine log -- is VaPkg.dll listed there? F-Secure and BitDefender have started to flag that dll as having a virus. |
| dewtell |
Posted - May 21 2018 : 6:49:49 PM
No, I still get the message after re-enabling VA and restarting the IDE. Is there any way to disable the Debugger Tools without going through the VA Options menu in the IDE? I think enabling that may be the source of my problem, since I enabled them in the IDE only recently, and the xml file mentions them.
|
| feline |
Posted - May 21 2018 : 5:51:24 PM
Can you please go into:
IDE tools menu -> Extensions and Updates...
and find Visual Assist in the list of installed extensions. Now Disable VA, which will require an IDE restart. After the IDE restart can you please go back into the Extensions and Updates dialog again, and Enable VA, which will require a second restart.
Does this help? Normally this fixes this problem when this happens. Normally a change to the IDE, perhaps installing an update, can trigger this, but it is not something we have been able to reliably reproduce. |
|
|
