Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • #18823

    After a power outage server service did not restart.

    Have had 2 clients call this week because of this problem.

    Had to log in to there system and start service manually.

    When this happened on my system last year the only thing that helped was creating a registry key to increase the timeout from 30000 to 60000. Is there another solution ?

    Log Name: System
    Source: Service Control Manager
    Date: 22/02/2016 9:02:09 AM
    Event ID: 7000
    Task Category: None
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: sharron
    The NewViews Server service failed to start due to the following error:
    The service did not respond to the start or control request in a timely fashion.
    Event Xml:
    <Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
    <Provider Name=”Service Control Manager” Guid=”{555908d1-a6d7-4695-8e1e-26931d2012f4}” EventSourceName=”Service Control Manager” />
    <EventID Qualifiers=”49152″>7000</EventID>
    <TimeCreated SystemTime=”2016-02-22T13:02:09.572149500Z” />
    <Correlation />
    <Execution ProcessID=”756″ ThreadID=”1252″ />
    <Security />
    <Data Name=”param1″>NewViews Server</Data>
    <Data Name=”param2″>%%1053</Data>


    Ideally after a server reboot/power outage the NV2 server service restarts automatically without the need to manually start the service.

    I have seen this error with Win server 2003 and XP but newer Windows Operating Systems do not experience this problem.

    I’ll make a note of this and see if future NV2 updates will include the doubled timeout setting.

    Thanks for the information.

    Regards to All,



    For your information computers are windows 7 pro


Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.