Hallo zusammen,
als erstes mal ein dickes Lob für eure Arbeit, wir benutzen seit mittlerweile 1 1/2 Jahren die Wawi(0.9.9.626) mit JTL- Shop(2.17) produktiv und warten Nägelkauend drauf, dass die neue beta fertig wird, vor allem ich wegen der Ameise^^.
Wir haben mittlerweile 4 Clients, welche über Dyndns auf unseren Server zugreifen.
Der Server hat XP-Pro drauf mit SP3, .NET Framework 2.0 Service Pack 1, es läuft MSSQL Server 2005 drauf.
Falls ich mal irgendwelche Probleme hatte habe ich bisher immer was im Forum dazu gefunden, weshalb ich selbst nie nen Thread eröffnen musste, nur dieses mal stehe ich auf dem schlauch:
Seit ein paar Wochen schaltet sich der Dienst SQL Server (JTLWAWI) über Nacht von selbst ab!
Starten wir den Server neu oder gehe ich in >Systemsteuerung>Verwaltung>Dienste kann ich den Dienst manuell wieder starten und alles läuft wieder einwandfrei... bis zum nächsten Morgen!
Nach einem halben Sonntag Forum durchforsten bin ich dahinter gekommen, das wohl das errorlog recht interessant wäre, also hier mal die letzte von 7 errorlogs:
2009-07-05 08:14:38.68 Server Microsoft SQL Server 2005 - 9.00.3077.00 (Intel X86)
Dec 17 2008 15:19:45
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2009-07-05 08:14:38.68 Server (c) 2005 Microsoft Corporation.
2009-07-05 08:14:38.68 Server All rights reserved.
2009-07-05 08:14:38.68 Server Server process ID is 3084.
2009-07-05 08:14:38.68 Server Authentication mode is MIXED.
2009-07-05 08:14:38.68 Server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\ LOG\ERRORLOG'.
2009-07-05 08:14:38.68 Server This instance of SQL Server last reported using a process ID of 556 at 05.07.2009 03:00:30 (local) 05.07.2009 01:00:30 (UTC). This is an informational message only; no user action is required.
2009-07-05 08:14:38.68 Server Registry startup parameters:
2009-07-05 08:14:38.68 Server -d C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-07-05 08:14:38.68 Server -e C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-07-05 08:14:38.68 Server -l C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-07-05 08:14:38.68 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-07-05 08:14:38.68 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-07-05 08:14:38.84 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-07-05 08:14:38.85 Server Database mirroring has been enabled on this instance of SQL Server.
2009-07-05 08:14:38.87 spid5s Starting up database 'master'.
2009-07-05 08:14:38.93 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-07-05 08:14:38.96 spid5s SQL Trace ID 1 was started by login "sa".
2009-07-05 08:14:38.98 spid5s Starting up database 'mssqlsystemresource'.
2009-07-05 08:14:38.99 spid5s The resource database build version is 9.00.3077. This is an informational message only. No user action is required.
2009-07-05 08:14:39.14 spid8s Starting up database 'model'.
2009-07-05 08:14:39.14 spid5s Server name is 'SERVER\JTLWAWI'. This is an informational message only. No user action is required.
2009-07-05 08:14:39.14 spid5s Starting up database 'msdb'.
2009-07-05 08:14:39.37 spid8s Clearing tempdb database.
2009-07-05 08:14:39.43 Server A self-generated certificate was successfully loaded for encryption.
2009-07-05 08:14:39.45 Server Server is listening on [ 'any' <ipv4> 3861].
2009-07-05 08:14:39.45 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2009-07-05 08:14:39.45 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2009-07-05 08:14:39.45 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2009-07-05 08:14:39.54 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2009-07-05 08:14:39.54 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-07-05 08:14:39.82 spid8s Starting up database 'tempdb'.
2009-07-05 08:14:39.92 spid5s Recovery is complete. This is an informational message only. No user action is required.
2009-07-05 08:14:39.92 spid11s The Service Broker protocol transport is disabled or not configured.
2009-07-05 08:14:39.92 spid11s The Database Mirroring protocol transport is disabled or not configured.
2009-07-05 08:14:39.93 spid11s Service Broker manager has started.
2009-07-05 08:14:56.32 spid51 Starting up database 'eazybusiness'.
2009-07-05 08:34:38.85 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 09:00:19.92 spid1s Server resumed execution after being idle 1792 seconds. Reason: timer event.
2009-07-05 10:06:38.85 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 10:31:14.92 spid1s Server resumed execution after being idle 1792 seconds. Reason: timer event.
2009-07-05 11:10:38.85 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 11:16:19.92 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-07-05 12:01:24.92 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-07-05 12:18:38.87 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 12:46:29.92 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-07-05 13:06:21.42 Server Server resumed execution after being idle 278 seconds: user activity awakened the server. This is an informational message only. No user action is required.
ich hoffe ich habe nichts an Infos vergessen und ihr könnt mir weiterhelfen.
viele Grüße
Marcus
als erstes mal ein dickes Lob für eure Arbeit, wir benutzen seit mittlerweile 1 1/2 Jahren die Wawi(0.9.9.626) mit JTL- Shop(2.17) produktiv und warten Nägelkauend drauf, dass die neue beta fertig wird, vor allem ich wegen der Ameise^^.
Wir haben mittlerweile 4 Clients, welche über Dyndns auf unseren Server zugreifen.
Der Server hat XP-Pro drauf mit SP3, .NET Framework 2.0 Service Pack 1, es läuft MSSQL Server 2005 drauf.
Falls ich mal irgendwelche Probleme hatte habe ich bisher immer was im Forum dazu gefunden, weshalb ich selbst nie nen Thread eröffnen musste, nur dieses mal stehe ich auf dem schlauch:
Seit ein paar Wochen schaltet sich der Dienst SQL Server (JTLWAWI) über Nacht von selbst ab!
Starten wir den Server neu oder gehe ich in >Systemsteuerung>Verwaltung>Dienste kann ich den Dienst manuell wieder starten und alles läuft wieder einwandfrei... bis zum nächsten Morgen!
Nach einem halben Sonntag Forum durchforsten bin ich dahinter gekommen, das wohl das errorlog recht interessant wäre, also hier mal die letzte von 7 errorlogs:
2009-07-05 08:14:38.68 Server Microsoft SQL Server 2005 - 9.00.3077.00 (Intel X86)
Dec 17 2008 15:19:45
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 3)
2009-07-05 08:14:38.68 Server (c) 2005 Microsoft Corporation.
2009-07-05 08:14:38.68 Server All rights reserved.
2009-07-05 08:14:38.68 Server Server process ID is 3084.
2009-07-05 08:14:38.68 Server Authentication mode is MIXED.
2009-07-05 08:14:38.68 Server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\ LOG\ERRORLOG'.
2009-07-05 08:14:38.68 Server This instance of SQL Server last reported using a process ID of 556 at 05.07.2009 03:00:30 (local) 05.07.2009 01:00:30 (UTC). This is an informational message only; no user action is required.
2009-07-05 08:14:38.68 Server Registry startup parameters:
2009-07-05 08:14:38.68 Server -d C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-07-05 08:14:38.68 Server -e C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-07-05 08:14:38.68 Server -l C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-07-05 08:14:38.68 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-07-05 08:14:38.68 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-07-05 08:14:38.84 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-07-05 08:14:38.85 Server Database mirroring has been enabled on this instance of SQL Server.
2009-07-05 08:14:38.87 spid5s Starting up database 'master'.
2009-07-05 08:14:38.93 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-07-05 08:14:38.96 spid5s SQL Trace ID 1 was started by login "sa".
2009-07-05 08:14:38.98 spid5s Starting up database 'mssqlsystemresource'.
2009-07-05 08:14:38.99 spid5s The resource database build version is 9.00.3077. This is an informational message only. No user action is required.
2009-07-05 08:14:39.14 spid8s Starting up database 'model'.
2009-07-05 08:14:39.14 spid5s Server name is 'SERVER\JTLWAWI'. This is an informational message only. No user action is required.
2009-07-05 08:14:39.14 spid5s Starting up database 'msdb'.
2009-07-05 08:14:39.37 spid8s Clearing tempdb database.
2009-07-05 08:14:39.43 Server A self-generated certificate was successfully loaded for encryption.
2009-07-05 08:14:39.45 Server Server is listening on [ 'any' <ipv4> 3861].
2009-07-05 08:14:39.45 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\JTLWAWI ].
2009-07-05 08:14:39.45 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$JTLWAWI\sql\query ].
2009-07-05 08:14:39.45 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.
2009-07-05 08:14:39.54 Server The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2009-07-05 08:14:39.54 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-07-05 08:14:39.82 spid8s Starting up database 'tempdb'.
2009-07-05 08:14:39.92 spid5s Recovery is complete. This is an informational message only. No user action is required.
2009-07-05 08:14:39.92 spid11s The Service Broker protocol transport is disabled or not configured.
2009-07-05 08:14:39.92 spid11s The Database Mirroring protocol transport is disabled or not configured.
2009-07-05 08:14:39.93 spid11s Service Broker manager has started.
2009-07-05 08:14:56.32 spid51 Starting up database 'eazybusiness'.
2009-07-05 08:34:38.85 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 09:00:19.92 spid1s Server resumed execution after being idle 1792 seconds. Reason: timer event.
2009-07-05 10:06:38.85 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 10:31:14.92 spid1s Server resumed execution after being idle 1792 seconds. Reason: timer event.
2009-07-05 11:10:38.85 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 11:16:19.92 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-07-05 12:01:24.92 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-07-05 12:18:38.87 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-07-05 12:46:29.92 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-07-05 13:06:21.42 Server Server resumed execution after being idle 278 seconds: user activity awakened the server. This is an informational message only. No user action is required.
ich hoffe ich habe nichts an Infos vergessen und ihr könnt mir weiterhelfen.
viele Grüße
Marcus
