Access denied error when starting DIAdem from LabVIEW

[DRock]

Hey Ken,

I'll be completely honest with you, I have little to no experience with group policy as well.  That being said, I personally can't fathom any other reasons as to why the instantiation of the ToCommand object would be prohibited given all that we've tried.

We're running this issue by DIAdem R&D (Thursday is a holiday in Germany so please allow us a day or two).  I will post any further findings to this thread.

[kennymolc]

DRock,

I posed the group policy question to the customer's IT consultant and discovered that their domain does NOT utilize any custom group or site policies which would effect this behavior (or any other behavior for that matter).  So it is not possible that this machine inherited a policy from the domain which is denying access.

That being said, the "access denied" error seemed only to become a problem after the customer joined the machine to the domain (which is what lead me to investigate inherited policies in the first place).

I am still concerned that I don't know the cause of the error 1601 we received when attempting to repair the DIAdem installation.  So while we're waiting on a response from Germany, I am going to have the customer setup a new machine which is already joined to the domain, then install DIAdem 10.2 evaluation version, and attempt to run the VBscript we've been testing with.  I think this will help to uncover whether we're working with a corrupt DIAdem installation, or perhaps a domain related issue as I previously suspected.

I don't know if it's a possibility, but do you know if there is any way to retrieve the installation log file for the DIAdem repair operation which caused the 1601 error?  Perhaps this could tell us what components of the install were causing this error to occur?

I'll keep an eye on the forum for any responses from Germany.

Thanks,

Ken

[kennymolc]

Just a quick Friday update before we're outta here for the weekend.

I decided to have the customer install DIAdem and LVRT on another machine within his domain to see whether domain policy was really the correct problem to be hunting down, and we were able to successfully execute the ToCommand.vbs script, as well as a custom LabVIEW application which creates references to the DD toolkit (thus opening DD, then closing it).  Both trials ran successfully (though we ran into a minor error initially when attempting to launch DIAdem remotely without first opening it manually).

This shows that the problem is certainly not related to group policy as I once suspected.  The next step (prior to wipeing the machine clean) is to completely uninstall DIAdem using the uninstaller and MSIBlast to completely remove it from the system, and then perform a fresh installation.

We attempted to uninstall DIAdem using the "Add or Remove Programs" panel in Windows, and the uninstall operation failed with the 1601 error we encountered earlier.  R&D indicate that this error is associated with "Windows Installer Service" being inaccessible.

On Monday, we will be trying the following to remove DIAdem from the customer's machine:

1. We'll try to perform the uninstall in Safe Mode to ensure there are no strange services running in the background to interrupt our uninstall.
2. We'll try to remove DIAdem using the MSIBlast utility mentioned above.
3. If we are still unable to complete an uninstall, I will attempt to repair the Windows installer using the methods described below:

• try to re-register msiexec with the system via the command prompt
• msiexec /unregister
• msiexec /regserver
• Reinstall windows installer (per Microsoft KB article KB893803 v2)

I'd like to try to avoid a complete system restore, but we'll keep that in the back of our mind as we continue hunting for the solution for this problem.

- Ken

[DRock]

Any luck, Ken?  Hope your weekend was rewarding.

[kennymolc]

Hello Derrick,

Unfortunately, we've stepped into a whole new pile of goo .

We were unable to uninstall the DIAdem application, and since this machine has been giving us nothing but trouble, we've decided that any further attempts could result in hunting down unrelated problems/corruptions in the Windows OS ... so we're formatting and restarting from scratch.

Thanks for your help investigating the problems, I'll post again once we're up and running again to ensure things are working again (it'll probably be a couple days).


Message Edited by DarkCloud on 05-07-2008 08:39 AM

[kennymolc]

Ok, back to the begining.

I had the customer format and install a fresh copy of Windows XP Professional SP2.  I had him apply all windows updates patches, and join the machine to his domain (so he could put antivirus on it).  After all this, the first thing I had him do is run the DIAdem 10.2 installation CD, and the first thing it tells us (as the installer wizard is starting) is that DIAdem 10.2 is already installed (see the attached log file - "install_try1.txt") and the installer cannot continue.  The only option we're left with at this point is to click OK.

This certainly adds to the confusion.  Still looking for a solution.  Suggestions?

- Ken

[DRock]

Hey Ken,

I've been trying to follow your email chain with R&D, but I'm admittedly out of the loop - hopefully I'm not too far behind.  I'm trying to stay up-to-date on the communication chain for my own knowledge and so that I can continue to update the thread for the general knowledge of the forum in the future.

Any updates?  Have you had a chance to grab the installation file recorded with the /log option?

[kennymolc]

DRock,

We generated the following log file, and we've sent it to the DIAdem installation development team for inspection.  I've also attached a copy of the log file to this post.

Best regards,
Ken

[kennymolc]

Hello Derrick,

After a long process of beating our heads against the wall, we have concluded that the problematic DIAdem installation was most likely due to a corrupt system component which appears to be limited to the PC in question.  As such, we chose to replace the PC with a new Windows XP machine which was loaded with the latest XP updates and joined to the customer domain.  DIAdem installed successfully, as did the LabVIEW runtime engine and our commercial software package as well.  Everything appears to be running fine at this point.

Thank you for your help.

[DRock]

Ken -

I'm just glad you found a solution.  Thanks for posting a followup - we had no internal documentation on issues like this occuring, but future customers will be able to refer to this, should they encounter the same type of problem...

Now, if only we knew how the PC got into that state...