locked
Service difference between XP, Vista, 7 - and Error 1053 RRS feed

  • Question

  • We're testing out Windows 7 and it looks like some of our software that works on XP (64 bit) doesn't run properly on Vista or 7 (64 bit). In particular, several services are returning a 1053 error when I try to start them. I looked into it: http://support.microsoft.com/kb/839174

    The difference however is that it's not a timeout - the error occurs instantly when trying to start the service. I installed and updated .NET 1.1 as a suggestion to solve the problem, but it didn't do anything. I also tried to run the service executables and the program executables in compatibility mode (XP SP3), to no avail. This leads me to believe that there are some fundamental differences in how services are handled in XP, Vista, and 7.

    Can anyone explain what these differences are and what possible steps I can take to get our software running on 7?
    • Moved by Carey FrischMVP Wednesday, September 2, 2009 2:52 PM Moved to relevant category (From:Windows 7 Miscellaneous)
    Wednesday, September 2, 2009 1:06 PM

Answers

  • Hi,

     

    May I know if you are developing application for Windows 7? If so, it is better to post a new thread to our MSDN forum for help:

     

    Software Development for Windows Client Forums

     

    Thanks you for your cooperation. Hope this issue can be resolved soon.


    Nicholas Li - MSFT
    • Marked as answer by Nicholas Li Thursday, September 10, 2009 1:14 AM
    Wednesday, September 9, 2009 10:58 AM
  • Well - one major change is Session 0 isolation in Vista and Windows 7 (see http://www.microsoft.com/whdc/system/vista/services.mspx for details).  If your service is trying to interact with the user directly, you'll run in to problems.  A 1053 would be thrown if the service does not properly register its state as started with the service control manager.  If you are developing the service, look into the code path up to the point where the service is marked as started.
    -Matt
    Wednesday, September 9, 2009 8:39 PM

All replies

  • anyone?
    Thursday, September 3, 2009 1:41 PM
  • Hi,

     

    May I know if you are developing application for Windows 7? If so, it is better to post a new thread to our MSDN forum for help:

     

    Software Development for Windows Client Forums

     

    Thanks you for your cooperation. Hope this issue can be resolved soon.


    Nicholas Li - MSFT
    • Marked as answer by Nicholas Li Thursday, September 10, 2009 1:14 AM
    Wednesday, September 9, 2009 10:58 AM
  • Well - one major change is Session 0 isolation in Vista and Windows 7 (see http://www.microsoft.com/whdc/system/vista/services.mspx for details).  If your service is trying to interact with the user directly, you'll run in to problems.  A 1053 would be thrown if the service does not properly register its state as started with the service control manager.  If you are developing the service, look into the code path up to the point where the service is marked as started.
    -Matt
    Wednesday, September 9, 2009 8:39 PM