Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 181
  • Last Modified:

The wrong program starts when logging in - SPOOKY

I have a very crazy thing happening when loggin in to my application. I enter user and passw and then I click on my login button. What my program does first is to open a user db to check if user and passw is OK. If OK the program starts and if not an error message tells you so. The software I log in to is developed by me and I has never ever had this kind of problem:
When I click the log in button an instance of Windows installer starts to install a cad viewer. This happens on some pcs where one or more cadviers is installed. What in the world could make this happen!?? Anyone to solve this spooky problem?
0
soft4u
Asked:
soft4u
  • 2
  • 2
1 Solution
 
TaconvinoCommented:
I had this problem before in an old Win98 box... it turned out to be a virus, although I don't remember what specific virus was causing this problem (the box was infected with several viruses)...

TCV
0
 
fostejoCommented:
soft4u,

It sounds like Windows Installer is correcting an issue its noticed with the CAD Viewer (that's already installed on the machine)  This is normal MSI "self-repair" behaviour and occurs if an MSI based installation detects that one of its 'components' isn't as expected (which usually means missing but could also mean that the version has been downgraded by another non-MSI based install for instance)

At the same time as the self-repair kicking off an event should be written into the Application event log saying exactly why the MSI is self-repairing. The event ID is usually '1001' and the description will probably be along the lines of:

"Detection of product 'TheCADApplication', feature 'FeatureName' failed during request for component '{ABCDEFA-9999-8888-7777-00105A9846E9}'"

The component ID referenced is the actual item that's 'missing' (or damaged or the incorrect version) on the machine - the ID directly refers to one of the components in the applications MSI and establishing which particular component it is will allow you to identify the other potentially rogue app that's also distributing the same component incorrectly etc.

To 'fix' you need to identify exactly why the Windows Installer feels it needs to 'correct' itself - the Event Log should give you some clues here and it will probably come down to 'something' inadvertely 'updating' a file the CAD application also uses.  Have in a look in the Applications log just after the Installer shows the dialog and paste the event detail here if it's not immediately apparent what the issue may be.

cheers
0
 
soft4uAuthor Commented:
Sounds like a possible reason to me since when the installer starts it asks for msi file that dont even exists on the pc. I assume you mean that I should look in the installers log to find out what the app (Autodesk viewer) is missing but where can I find the log file?

I have noticed another weird thing thats happening when I monitor with filemon, every time I log in to my app and some other commercial apps with log in procedures the path to Autodesk is visible in the filemon log. I can also see that some DLL files in the Autodesk dir is accessed or at least the system tries to access them.

/cheers to you too
0
 
fostejoCommented:
soft4u,

In order for the Windows Installer to correct the problem its found, it expects (in this case) to have access to the original MSI that was used to install the Autodesk viewer - the "best" solution here would be to give it access to the MSI it's looking for; it would then correct the issue and that *may* be the last you see of it..

"...I assume you mean that I should look in the installers log to find out what the app (Autodesk viewer) is missing..."
- No, I did mean the Event Log:  from Start/Run, enter 'eventvwr' and select to view the application log and look out for any entries where the EventSource is 'msiinstaller' - these events may well indicate the exact file / component it's trying to repair.

The important thing to note is that this issue is likely nothing to do with your log in application (that's just 'triggering' the repair) , the problem is probably just the Autodesk Viewer itself so we need to concentrate on correcting that - is it possible for you to supply the original Autodesk Viewer installation media to the Windows Installer when it asks for it? (is it downloadable perhaps?)

Alternatively, is it used/needed on the machine? If not, we could look at removing it off the machine, either the official way via Add/Remove programs or - if that doesn't work (because it again needs the original MSI) - by 'forcing it' off the machine with something like the Microsoft MSI Clean Up Utility at http://technet2.microsoft.com/WindowsServer/en/Library/99c9ed66-bfa2-45f7-87c8-7a54c34941c01033.mspx?mfr=true


hope that helps.
0
 
soft4uAuthor Commented:
We managed to fix it on one pc so I expect it to work on the rest also. Thanks alot
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now