Re: [Emerald] SQL 6.5

Josh Hillman ( (no email) )
Wed, 19 May 1999 15:52:54 -0400

From: John Roman <>
>This error is reported in event viewer, when I try to manually start SQL
>it says that it cannot start because of an internal windows error.

This may be a stupid question, but have you tried rebooting the machine?
Maybe that'd help.
Try starting SQL in single-user mode. I don't have any idea if it'll get
you anywhere or not, but it can't hurt:
sqlservr -m
If it does start in single-user mode, maybe you can sift through the SQL
logs from within Enterprise Manager and see what's going on with it. Also,
take a look in the mssql\log directory for any pointers.


>-----Original Message-----
>From: Dale E. Reed Jr. []
>Sent: Wednesday, May 19, 1999 10:54 AM
>Subject: Re: [Emerald] SQL 6.5
>John Roman wrote:
>> I know this is not a emerald problem but my SQL server will not start
>> and therefore Emerald will not start.
>> I am receiving the following message on my SQL server today
>> Can't allocate space for object 'Syslogs' in database 'model' because
>> the 'logsegment' segment is full. If you ran out of space in Syslogs,
>> dump the transaction log. Otherwise, use ALTER DATABASE or
>> sp_extendsegment to increase the size of the segment.
>> Does anyone know what file I need to delete or modify so that I can
>> SQL to start??
>This shouldn't prevent your SQL Server from starting. I'd be
>real curious who/what was changing anything in the model
>database. It is was SQL Server uses as a "model" when you
>create a new database. Its very rare to see anything using
>The above error message is usually given when you are changing
>something in a database. Where did you get this error message
>Dale E. Reed Jr. Emerald and RadiusNT
>IEA Software, Inc.