March 31, 2009 at 2:51 pm
this is the error log generated when I try to run a program that builds on sql express 2005:
009-03-30 13:46:58.89 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2009-03-30 13:46:58.89 Server Error: 17054, Severity: 16, State: 1.
2009-03-30 13:46:58.89 Server The current event was not reported to the Windows Events log. Operating system error = 1502(The event log file is full.). You may need to clear the Windows Events log if it is full.
2009-03-30 13:46:58.89 Server (c) 2005 Microsoft Corporation.
2009-03-30 13:46:58.89 Server All rights reserved.
2009-03-30 13:46:58.89 Server Server process ID is 1908.
2009-03-30 13:46:58.89 Server Authentication mode is MIXED.
2009-03-30 13:46:58.89 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2009-03-30 13:46:58.89 Server This instance of SQL Server last reported using a process ID of 940 at 3/30/2009 1:43:31 PM (local) 3/30/2009 6:43:31 PM (UTC). This is an informational message only; no user action is required.
2009-03-30 13:46:58.89 Server Registry startup parameters:
2009-03-30 13:46:58.89 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2009-03-30 13:46:58.89 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2009-03-30 13:46:58.89 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2009-03-30 13:46:58.93 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-03-30 13:46:58.93 Server Detected 2 CPUs. This is an informational message; no user action is required.
2009-03-30 13:46:59.96 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-03-30 13:47:00.01 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-03-30 13:47:00.01 Server Database mirroring has been enabled on this instance of SQL Server.
2009-03-30 13:47:00.03 spid4s Starting up database 'master'.
2009-03-30 13:47:00.15 spid4s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2009-03-30 13:47:00.48 spid4s SQL Trace ID 1 was started by login "sa".
2009-03-30 13:47:00.54 spid4s Starting up database 'mssqlsystemresource'.
2009-03-30 13:47:00.59 spid4s The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2009-03-30 13:47:00.85 spid4s Server name is 'EM_55719\HAZUSPLUSSRVR'. This is an informational message only. No user action is required.
2009-03-30 13:47:00.96 spid8s Starting up database 'model'.
2009-03-30 13:47:00.98 spid4s Starting up database 'msdb'.
2009-03-30 13:47:01.10 Server A self-generated certificate was successfully loaded for encryption.
2009-03-30 13:47:01.10 Server Server is listening on [ 'any' 1059].
2009-03-30 13:47:01.10 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\HAZUSPLUSSRVR ].
2009-03-30 13:47:01.10 Server Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$HAZUSPLUSSRVR\sql\query ].
2009-03-30 13:47:01.10 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-03-30 13:47:01.29 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2009-03-30 13:47:01.31 spid8s Clearing tempdb database.
2009-03-30 13:47:02.43 spid8s Starting up database 'tempdb'.
2009-03-30 13:47:02.59 spid4s Recovery is complete. This is an informational message only. No user action is required.
2009-03-30 13:47:02.59 spid11s The Service Broker protocol transport is disabled or not configured.
2009-03-30 13:47:02.59 spid11s The Database Mirroring protocol transport is disabled or not configured.
2009-03-30 13:47:02.64 spid11s Service Broker manager has started.
2009-03-30 13:57:35.70 Server Server resumed execution after being idle 600 seconds: user activity awakened the server. This is an informational message only. No user action is required.
2009-03-30 13:57:37.92 spid51 Starting up database 'syHazus'.
2009-03-30 13:57:38.75 spid14s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-03-30 13:57:38.75 spid14s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-03-30 13:57:38.75 spid14s SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2009-03-30 13:58:25.54 spid51 Starting up database 'syHazus'.
2009-03-30 13:58:31.49 spid51 Starting up database 'syHazus'.
2009-03-30 13:58:45.12 spid51 Starting up database 'syHazus'.
2009-03-30 13:58:48.16 spid51 Starting up database 'mnmbmbm'.
2009-03-30 13:58:50.12 spid51 Starting up database 'mnmbmbm'.
2009-03-30 13:58:52.57 spid51 Starting up database 'syBIT'.
2009-03-30 13:58:53.43 spid51 Starting up database 'syBIT'.
2009-03-30 13:58:53.84 spid51 Starting up database 'syHazus'.
2009-03-30 13:58:55.76 spid51 Starting up database 'mnmbmbm'.
2009-03-30 13:59:00.06 spid51 Starting up database 'syHazus'.
2009-03-30 13:59:01.44 spid52 Starting up database 'mnmbmbm'.
2009-03-30 13:59:10.99 spid52 Starting up database 'syBIT'.
2009-03-30 13:59:11.60 spid52 Starting up database 'syBIT'.
2009-03-30 13:59:17.04 spid52 Starting up database 'mnmbmbm'.
2009-03-30 14:44:34.34 spid1s Server resumed execution after being idle 1792 seconds. Reason: timer event.
2009-03-30 14:50:57.92 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-03-30 15:29:38.37 spid1s Server resumed execution after being idle 1791 seconds. Reason: timer event.
2009-03-30 15:54:34.60 Server The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2009-03-30 16:27:29.53 spid1s Server resumed execution after being idle 2557 seconds. Reason: timer event.
2009-03-30 16:51:00.04 spid11s Service Broker manager has shut down.
2009-03-30 16:51:00.38 spid4s SQL Server is terminating in response to a 'stop' request from Service Control Manager. This is an informational message only. No user action is required.
2009-03-30 16:51:00.38 spid4s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
March 31, 2009 at 3:33 pm
2009-03-30 13:46:58.89 Server The current event was not reported to the Windows Events log. Operating system error = 1502(The event log file is full.).
This is the reason for your problem but I need more information like operating system and what application before I can give you my fix because I think this is a bug in SQL Server Express relational engine. So post detailed information about your setup.
Kind regards,
Gift Peddie
March 31, 2009 at 4:15 pm
Thanks so much for trying to help-it is Windows XP, SP2-the software that uses sql is HAZUS-from FEMA-it is a lost estimation software for natural hazards-all of its information is within sql-the program then uses ArcGIS (ESRI product) to "display" the data-that is an extremely condensed version-so basically, it's three apps working together-- thanks for any advice you can give!
Dana
March 31, 2009 at 4:26 pm
Also, ArcGIS version is ArcInfo that has a license server/sentinel key on the local machine-I don't know if that may be a problem as far as sql server trying to access it to "build a region"
March 31, 2009 at 4:28 pm
Your XP needs to be Pro with Admin tool installed go to Control panel then Admin tool then computer management Event Viewer and right click on Application and go to properties and you could increase the log it increases by 64k increment so you could increase by either 320 or 640. I don't know what is causing this problem it is related to SQL Server Express running a User Instance maybe your application is running a User Instance.
Kind regards,
Gift Peddie
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply