topic Maybe. Other tip is that you in Analyzers

Error message after software update when starting VS2013

davidlofstrand — Tue, 22 Apr 2014 09:12:24 GMT

Hello,

I'm using your product in our software to profile and optimize code but after the recent update (this morning) your software refuses to load properly when I start VS2013 and I get a dialog box with the following error message:

---

The 'Intel Inspector XE 213' 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 'C:\Users\$user\AppData\Roaming\Microsoft\VisualStudio\12.0\ActivityLog.xml'.

Continue to show this error message?

---

Since you suggest not to put any user information here I replaced my login name with $user above.

The contents of the file contains some entries and I chosen to post the last of them here. The entire file is attached where I replaced my username with $user.

Contents of ActivityLog.xml

---

<?xml version="1.0" encoding="utf-16"?>
<?xml-stylesheet type="text/xsl" href="ActivityLog.xsl"?>
<activity>

<entry> ... most entries skipped here</entry>

<entry>
<record>295</record>
<time>2014/04/22 08:33:58.615</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function CVsPackageInfo::HrInstantiatePackage</description>
<guid>{54AB0332-9EC4-4535-BBE1-7CE49F13170C}</guid>
</entry>
<entry>
<record>296</record>
<time>2014/04/22 08:33:58.631</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [Intel Advisor XE 2013]</description>
<guid>{54AB0332-9EC4-4535-BBE1-7CE49F13170C}</guid>
</entry>
<entry>
<record>297</record>
<time>2014/04/22 08:33:58.631</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Loading UI library</description>
<guid>{54AB0332-9EC4-4535-BBE1-7CE49F13170C}</guid>
<path>C:\Program Files (x86)\Intel\Advisor XE 2013\bin32\*\advixe_vspkgui11.dll</path>
</entry>
<entry>
<record>298</record>
<time>2014/04/22 08:33:58.693</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function VBDispatch::GetTypeLib</description>
</entry>
<entry>
<record>299</record>
<time>2014/04/22 08:33:58.693</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Leaving function VBDispatch::GetTypeLib</description>
<guid>{80CC9F66-E7D8-4DDD-85B6-D9E6CD0E93E2}</guid>
</entry>
<entry>
<record>300</record>
<time>2014/04/22 08:33:58.693</time>
<type>Information</type>
<source>VisualStudio</source>
<description>End package load [Intel Advisor XE 2013]</description>
<guid>{54AB0332-9EC4-4535-BBE1-7CE49F13170C}</guid>
</entry>
<entry>
<record>301</record>
<time>2014/04/22 08:33:58.693</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Entering function CVsPackageInfo::HrInstantiatePackage</description>
<guid>{809594C7-C986-4413-850B-F27598154998}</guid>
</entry>
<entry>
<record>302</record>
<time>2014/04/22 08:33:58.693</time>
<type>Error</type>
<source>VisualStudio</source>
<description>No InprocServer32 registered for package [Intel Inspector XE 2013]</description>
<guid>{809594C7-C986-4413-850B-F27598154998}</guid>
<hr>8007007e</hr>
<errorinfo></errorinfo>
<path>C:\Program Files (x86)\Intel\Inspector XE 2013\bin32\inspxe_vspkg.dll</path>
</entry>

</activity>

---

Any hints of what I should do?

Best regards,

David Löfstrand

It seems that Microsoft*

Peter_W_Intel — Wed, 23 Apr 2014 03:18:22 GMT

It seems that Microsoft* Visual Studio* 2013 has been supported since Inspector XE 2013 Update 8 and later. Please check your using version.

This VS integration issue, you might verify if this has been installed in command line:

Open a cmd windows as administrator privilege. Go Inspector 2013 XE\bin32 -

Inspector XE 2013\bin32>inspxe-vsreg.exe --status-all

Inspector XE 2013\bin32>inspxe-vsreg.exe --disable-all

Inspector XE 2013\bin32>inspxe-vsreg.exe --integrate-all

Thanks for the feedback.

davidlofstrand — Wed, 23 Apr 2014 07:35:39 GMT

Thanks for the feedback.

I think something must have gone partially wrong during the upgrade process since the folder "C:\Program Files (x86)\Intel\Inspector XE 2013" is empty and contain no files or folders while the other products seems to be in order.

I'll try to reinstall the software.

Maybe. Other tip is that you

Peter_W_Intel — Wed, 23 Apr 2014 07:49:26 GMT

Maybe. Other tip is that you may check if Inspector XE folder exists after uninstalling old product, manually delete it then install new one.

Some users worked on VTune(TM) Amplifier XE, who met similar problem, I remember.

Hi again,

davidlofstrand — Wed, 23 Apr 2014 08:04:00 GMT

Hi again,

I'm downloading the software now but recognized a spelling error in my original post.

The 'Intel Inspector XE 213' package did not load correctly.

Should be:

The 'Intel Inspector XE 2013' package did not load correctly.

For some reason I couldn't edit my post.

Thanks for the help again,

David

InprocServer32 registered for

Bernard — Tue, 06 May 2014 18:42:28 GMT

InprocServer32 registered for package

The error seems to be related to InprocServer32 registration.

I do not know if inspxe_vspkg.dll is the implemetation of InprocServer32,but if you could try to register inspxe_vspkg.dll with regsvr32 command and look for the result?

Hello there,

davidlofstrand — Thu, 08 May 2014 07:55:27 GMT

Hello there,

It's been a while since I fixed it but what had happened was that all software products were ok except Intel Inspector.

When I browsed the product folders, after it was supposed to be installed, the folder was there but it was empty. I assume that the uninstallation process during the update had gone well or at least partially well while the installation process did not.

The solution for me was simply to uninstall everything I could then download and reinstall the software again. After this everthing worked fine.

Best Regards,

David

I am glad that your problem

Bernard — Thu, 08 May 2014 17:50:51 GMT

I am glad that your problem was solved.

I'm glad to see that the

Peter_W_Intel — Fri, 09 May 2014 00:44:57 GMT

I'm glad to see that the problem has been solved, too:-)

Another tip is : if Inspector standalone can work smoothly, using inspxe-vsreg.exe to reinstall vs integration is first consideration. Second option is to uninstall/reinstall the product.