PDA module installation fatal error. Why?

[MitsuMan]

Why do I get this Fatal Error: Installation ended prematurely because of an error.

I had the module installed and working fine. The only changes I have made recently is updating the toolkit software with my developer suit package. I noticed some of my express VI's were broken when I did the update, but I fixed those.

When I tried to build a Palm OS .prc that I updated, I received a build script error.

I then uninstalled the program and received some fatal errors during the uninstall.

It did though uninstall the module, but now I can't reinstall it.

Help!

[Ankita]

Hi MitsuMan,

What version of the PDA module were you using before using the Developer suite. Looking at your post, it looks like a problem of registry corruption. I would suggest that you contact the technical support team at National Instruments via phone/email regarding this issue.

Regards,

Ankita

[lleida]

Hi!

I uninstall the modul pda once, and I have not had any problem install it again. I don't understand it.

G

[Ankita]

It looks like you had to uninstall the module twice before you could install it. It seems that the uninstall did not work the first time or could it be that you did not restart your machine before installing?

Regards,

Ankita

[MitsuMan]

The NI help desk has asked that I try cleaning the registry with this program called msiblast, which almost sounds like a virus.

I will try it and see what happens. I think I will have to reload all of my Labview stuff again though.

I will back up all my programs first and go from there.

[MitsuMan]

OK, it turns out there wasn't a problem with the PDA Module at all.

There was a problem with my default access permissions in my DCOM configuration.

I recently was trying to connect to a remote OPC server which required some changes in the DCOM settings. Evidently I changed the wrong setting and removed everyone from the default access. This change didn't affect installations or programs that didn't access the registry, but any programs that did were effected.

Here is the windows app note: http://support.microsoft.com/default.aspx?scid=kb;en-us;909444

To fix I had to simply go into the DCOM configuration by typing 'dcomcnfg' at the command prompt without the quotes.

Under the tab default security permissions click edit default. Add the group everyone to the Default Access permissions..