VSTO SE + Outlook 2003 on Vista -> Addin does not start after upda

B

BillyD

I have an addin that was devd and deployed to 100+ users. These users are
running XP PRO and Office 2003.
THe addin has a cas policy, and a second addin that forces updates. This
method is working without an issue on the xp boxes. However, testing this on
a Vista box shows the addin updater update the addin (the one that actually
does stuuf :) ) and start(maybe). However it does not run and it does not
give ANY errors at all. When I check to see if it is loaded in outlook it
shows that it is. I do not have a dev box (vista) to run on to SEE what if
anything errors out. Does anyone have any suggestions to look at to see why
this does not work in vista.

THanks BillyDvd
 
B

BillyD

Ken,
Thanks for the response!
I have looked into the debugging for managed addins (NICE to know that this
stuff is there and can be used :) )
However, you state :
Since it's a Vista problem it could be permissions of the current user if
the addin isn't updating, missing strong naming or dll/exe signing, lack of
a proper manifest file and a few other things.
-----------------------------------------------------------------|||
If any of these where true in the XP enviornment would they bomb out, or
because its XP will certain errors be passed by?
All code/installers/updates are the same for both the XP and Vista.

Everything works on XP - updates included.
In vista - After the initial install everything works, after the update
nothing works...
I granted full rights to the dir that needs to have the files copied into
it, so at least the files are getting updated, however they will not load the
addin any longer and there is no errors or anything ...
All the log files look the same as the initial loaded log files....

Any other ideas?

Thanks again for your time!!!

BillyDvd
 
K

Ken Slovak - [MVP - Outlook]

Some things that don't matter much with XP do matter with Vista, such as
manifest files.

I can't tell you what's missing or not done right with your update, it could
be anything. As I said, the first thing to do is use all the tricks
mentioned in that debugging article. I've found it very useful to review the
Fusion logs when something is there and fires the load errors message. That
shows the addin tried to load but failed. To me that means permissions,
something missing or something incorrectly set up. Only you can tell what
that is with the troubleshooting information from that article.

Did you set up Fusion logging and review the load log files, as mentioned in
that article?
 
B

BillyD

Ken,
I set up the fusion logs ...

*** Assembly Binder Log Entry (9/12/2008 @ 8:44:29 AM) ***

The operation failed.
Bind result: hr = 0x80070002. The system cannot find the file specified.

Assembly manager loaded from:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
Running under executable C:\Program Files\Microsoft
Office\OFFICE11\OUTLOOK.EXE
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: User = SENTINEL-DG\wdomenz
LOG: DisplayName = ConferenceRoomScheduler.resources, Version=1.0.0.0,
Culture=en-US, PublicKeyToken=d958ed45ea2f3d27
(Fully-specified)
LOG: Appbase = file:///C:/Program Files/Sentinel Technologies, Inc/Outlook
Addins/Conference Room Scheduler/
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : ConferenceRoomScheduler, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=d958ed45ea2f3d27.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Program Files\Sentinel
Technologies, Inc\Outlook Addins\Conference Room
Scheduler\ConferenceRoomScheduler.dll.config
LOG: Using machine configuration file from
C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
LOG: Post-policy reference: ConferenceRoomScheduler.resources,
Version=1.0.0.0, Culture=en-US, PublicKeyToken=d958ed45ea2f3d27
LOG: The same bind was seen before, and was failed with hr = 0x80070002.
ERR: Unrecoverable error occurred during pre-download check (hr = 0x80070002).

<Hmmmm> THis really means nothing to me... :(

What is it failing for?

Is there a guide or read somewhere on what all this means?

Thanks
BillyDvd
 
K

Ken Slovak - [MVP - Outlook]

It's failing on trying to load the machine.config file. Whether or not that
exists on that system I have no idea. You might want to run the logging on a
machine where it works, both XP with your update and Vista with the original
code that worked and see what differences there are.

At worst, you might have to open a case with PSS and let them analyze your
Fusion logs.
 
B

BillyD

Ken,
Thanks again for the reply...
I will give that a go!

BillyDvd
--
What are we talking about?


Ken Slovak - said:
It's failing on trying to load the machine.config file. Whether or not that
exists on that system I have no idea. You might want to run the logging on a
machine where it works, both XP with your update and Vista with the original
code that worked and see what differences there are.

At worst, you might have to open a case with PSS and let them analyze your
Fusion logs.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top