The wrong program starts when logging in - SPOOKY

Posted on 2006-05-18
Last Modified: 2010-05-01
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?
Question by:soft4u
    LVL 6

    Expert Comment

    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)...

    LVL 10

    Expert Comment


    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.


    Author Comment

    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
    LVL 10

    Accepted Solution


    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

    hope that helps.

    Author Comment

    We managed to fix it on one pc so I expect it to work on the rest also. Thanks alot

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    When trying to find the cause of a problem in VBA or VB6 it's often valuable to know what procedures were executed prior to the error. You can use the Call Stack for that but it is often inadequate because it may show procedures you aren't intereste…
    Article by: Martin
    Here are a few simple, working, games that you can use as-is or as the basis for your own games. Tic-Tac-Toe This is one of the simplest of all games.   The game allows for a choice of who goes first and keeps track of the number of wins for…
    Get people started with the process of using Access VBA to control Excel using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Excel. Using automation, an Access application can laun…
    This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…

    794 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now