Showing posts with label errors. Show all posts

Monday, March 12, 2012

MSSQLSERVER errors on PC running MSDE

I have a retail account with 2 PC's running the latest version of
Microsofts RMS. One of the PC's
acts as the server using MSDE. In the event viewer for this PC there are
hundreds of
errors that show this:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17052
Date: 11/25/2004
Time: 2:55:04 AM
User: N/A
Computer: W_CM1
Description:
Error: 644, Severity: 21, State: 3
Could not find the index entry for RID '160000019f9af100' in index page
(1:28465), index ID 0, database 'conrevhb2'.
Data:
0000: 84 02 00 00 15 00 00 00 ?......
0008: 06 00 00 00 57 00 5f 00 ...W._.
0010: 43 00 4d 00 31 00 00 00 C.M.1...
0018: 0a 00 00 00 63 00 6f 00 ...c.o.
0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
0028: 68 00 62 00 32 00 00 00 h.b.2...
Can someone help me out?
Thanks
John"John" <jk@.rt.com> wrote in message
news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
>I have a retail account with 2 PC's running the latest version of
>Microsofts RMS. One of the PC's
> acts as the server using MSDE. In the event viewer for this PC there are
> hundreds of
> errors that show this:
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 11/25/2004
> Time: 2:55:04 AM
> User: N/A
> Computer: W_CM1
> Description:
> Error: 644, Severity: 21, State: 3
> Could not find the index entry for RID '160000019f9af100' in index page
> (1:28465), index ID 0, database 'conrevhb2'.
> Data:
> 0000: 84 02 00 00 15 00 00 00 ?......
> 0008: 06 00 00 00 57 00 5f 00 ...W._.
> 0010: 43 00 4d 00 31 00 00 00 C.M.1...
> 0018: 0a 00 00 00 63 00 6f 00 ...c.o.
> 0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
> 0028: 68 00 62 00 32 00 00 00 h.b.2...
> Can someone help me out?
> Thanks
> John
>
>
Your clustered index on database conrevhb2 has problems with it. Take a
look at the BOL for DBCC CHECKDB command. There are some repair options.
If that doesn't work, you may need to drop and recreate your clustered
index. (Keep in mind that it may be your Primary key constraint as well, as
this automatically creates a clustered index by default.).
HTH
Rick Sawtell
MCT, MCSD, MCDBA|||Rick,
Thanks for the reply but, I am not a database admin so I know I can do a
google search and see what you are suggesting but is this correct for a
database using the MSDE engineon a Win2K Pro machine?
TIA
John
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
> "John" <jk@.rt.com> wrote in message
> news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
>>I have a retail account with 2 PC's running the latest version of
>>Microsofts RMS. One of the PC's
>> acts as the server using MSDE. In the event viewer for this PC there are
>> hundreds of
>> errors that show this:
>> Event Type: Error
>> Event Source: MSSQLSERVER
>> Event Category: (2)
>> Event ID: 17052
>> Date: 11/25/2004
>> Time: 2:55:04 AM
>> User: N/A
>> Computer: W_CM1
>> Description:
>> Error: 644, Severity: 21, State: 3
>> Could not find the index entry for RID '160000019f9af100' in index page
>> (1:28465), index ID 0, database 'conrevhb2'.
>> Data:
>> 0000: 84 02 00 00 15 00 00 00 ?......
>> 0008: 06 00 00 00 57 00 5f 00 ...W._.
>> 0010: 43 00 4d 00 31 00 00 00 C.M.1...
>> 0018: 0a 00 00 00 63 00 6f 00 ...c.o.
>> 0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
>> 0028: 68 00 62 00 32 00 00 00 h.b.2...
>> Can someone help me out?
>> Thanks
>> John
>>
> Your clustered index on database conrevhb2 has problems with it. Take a
> look at the BOL for DBCC CHECKDB command. There are some repair options.
> If that doesn't work, you may need to drop and recreate your clustered
> index. (Keep in mind that it may be your Primary key constraint as well,
> as this automatically creates a clustered index by default.).
> HTH
> Rick Sawtell
> MCT, MCSD, MCDBA
>|||MSDE uses the same DLLs that SQL Server uses. It has certain built-in
limitations on how it operates, but this is essentially what needs to be
fixed.
If you don't have Query Analzer, you may try to use osql and do this work
from the command line.
Rick
"John" <jk@.rt.com> wrote in message
news:ec$IJyi1EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Rick,
> Thanks for the reply but, I am not a database admin so I know I can do a
> google search and see what you are suggesting but is this correct for a
> database using the MSDE engineon a Win2K Pro machine?
> TIA
>
> John
>
> "Rick Sawtell" <quickening@.msn.com> wrote in message
> news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
>> "John" <jk@.rt.com> wrote in message
>> news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
>>I have a retail account with 2 PC's running the latest version of
>>Microsofts RMS. One of the PC's
>> acts as the server using MSDE. In the event viewer for this PC there
>> are hundreds of
>> errors that show this:
>> Event Type: Error
>> Event Source: MSSQLSERVER
>> Event Category: (2)
>> Event ID: 17052
>> Date: 11/25/2004
>> Time: 2:55:04 AM
>> User: N/A
>> Computer: W_CM1
>> Description:
>> Error: 644, Severity: 21, State: 3
>> Could not find the index entry for RID '160000019f9af100' in index page
>> (1:28465), index ID 0, database 'conrevhb2'.
>> Data:
>> 0000: 84 02 00 00 15 00 00 00 ?......
>> 0008: 06 00 00 00 57 00 5f 00 ...W._.
>> 0010: 43 00 4d 00 31 00 00 00 C.M.1...
>> 0018: 0a 00 00 00 63 00 6f 00 ...c.o.
>> 0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
>> 0028: 68 00 62 00 32 00 00 00 h.b.2...
>> Can someone help me out?
>> Thanks
>> John
>>
>>
>> Your clustered index on database conrevhb2 has problems with it. Take a
>> look at the BOL for DBCC CHECKDB command. There are some repair options.
>> If that doesn't work, you may need to drop and recreate your clustered
>> index. (Keep in mind that it may be your Primary key constraint as well,
>> as this automatically creates a clustered index by default.).
>> HTH
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
>|||Thanks Rick!!
John
"Rick Sawtell" <quickening@.msn.com> wrote in message
news:%23xY1J%23i1EHA.2540@.TK2MSFTNGP09.phx.gbl...
> MSDE uses the same DLLs that SQL Server uses. It has certain built-in
> limitations on how it operates, but this is essentially what needs to be
> fixed.
> If you don't have Query Analzer, you may try to use osql and do this work
> from the command line.
> Rick
>
> "John" <jk@.rt.com> wrote in message
> news:ec$IJyi1EHA.3596@.TK2MSFTNGP12.phx.gbl...
>> Rick,
>> Thanks for the reply but, I am not a database admin so I know I can do a
>> google search and see what you are suggesting but is this correct for a
>> database using the MSDE engineon a Win2K Pro machine?
>> TIA
>>
>> John
>>
>> "Rick Sawtell" <quickening@.msn.com> wrote in message
>> news:uLLOjpi1EHA.1264@.TK2MSFTNGP12.phx.gbl...
>> "John" <jk@.rt.com> wrote in message
>> news:%23EknDWi1EHA.304@.TK2MSFTNGP11.phx.gbl...
>>I have a retail account with 2 PC's running the latest version of
>>Microsofts RMS. One of the PC's
>> acts as the server using MSDE. In the event viewer for this PC there
>> are hundreds of
>> errors that show this:
>> Event Type: Error
>> Event Source: MSSQLSERVER
>> Event Category: (2)
>> Event ID: 17052
>> Date: 11/25/2004
>> Time: 2:55:04 AM
>> User: N/A
>> Computer: W_CM1
>> Description:
>> Error: 644, Severity: 21, State: 3
>> Could not find the index entry for RID '160000019f9af100' in index page
>> (1:28465), index ID 0, database 'conrevhb2'.
>> Data:
>> 0000: 84 02 00 00 15 00 00 00 ?......
>> 0008: 06 00 00 00 57 00 5f 00 ...W._.
>> 0010: 43 00 4d 00 31 00 00 00 C.M.1...
>> 0018: 0a 00 00 00 63 00 6f 00 ...c.o.
>> 0020: 6e 00 72 00 65 00 76 00 n.r.e.v.
>> 0028: 68 00 62 00 32 00 00 00 h.b.2...
>> Can someone help me out?
>> Thanks
>> John
>>
>>
>> Your clustered index on database conrevhb2 has problems with it. Take a
>> look at the BOL for DBCC CHECKDB command. There are some repair
>> options. If that doesn't work, you may need to drop and recreate your
>> clustered index. (Keep in mind that it may be your Primary key
>> constraint as well, as this automatically creates a clustered index by
>> default.).
>> HTH
>> Rick Sawtell
>> MCT, MCSD, MCDBA
>>
>>
>

MSSQLSERVER errors on PC running MSDE

MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
Bryan
If I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.
|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:

> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>
|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:

> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times in
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>
|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
[vbcol=seagreen]
> All of the errors point to disk problems, but given you are on a SAN(NAS?) I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the error
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:

MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
BryanIf I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:
> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:
> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times in
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
> All of the errors point to disk problems, but given you are on a SAN(NAS?) I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the error
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:
> > Hi
> >
> > W2K3 std edition (no SP) - SQL Server Std SP3
> >
> > I have a lot of errors showing up in app log on different days and times in
> > the form of:
> >
> > ***********************************
> > MSSQLSERVER, Category (2), Event ID: 17055
> > Description:
> > 18052
> > Error: 3314, Severoty:21, State: 4
> > ***********************************
> > The 'error' number varies between, 3314, 9001 and 823.
> >
> > The account is always the same one.
> >
> > Trawling through the SQL log - I can see some entries with the following
> > detail:
> >
> > ***********************************
> > database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
> > the event log for more information.
> > ***********************************
> >
> > DBCC CHECKDB shows no errors on this database.
> > Any pointers on this very much appreciated.
> >
> > All SQL services are currently running.
> >
> > Thanks
> > Bryan
> >
> >
> >

MSSQLSERVER error(s) - severity and state

Hi
W2K3 std edition (no SP) - SQL Server Std SP3
I have a lot of errors showing up in app log on different days and times in
the form of:
***********************************
MSSQLSERVER, Category (2), Event ID: 17055
Description:
18052
Error: 3314, Severoty:21, State: 4
***********************************
The 'error' number varies between, 3314, 9001 and 823.
The account is always the same one.
Trawling through the SQL log - I can see some entries with the following
detail:
***********************************
database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. See
the event log for more information.
***********************************
DBCC CHECKDB shows no errors on this database.
Any pointers on this very much appreciated.
All SQL services are currently running.
Thanks
BryanIf I were you, I would suck and backup as much of the data as you can
from the database files / disks. Seems to me that this is a hard error
inidcating that your underlying disks are about to die (or the
controller has a defect). Backup up and then checking / replacing the
databases would be the best to do. (for me)
HTH, Jens Suessmeyer.|||Hi Jens
Thanks for the prompt reply.
Would this still be the case, as I have a whole bunch of DBs stting on the
same disk location.
I should have also noted that this is a SAN attached server.
Are there any particular tools (that are non intrusive as this is a
production server) that can check the integrity of a particular database
(other than DBCC CHECKDB/CHECKALLOC/CHECKCATALOG)?
Thanks
Bry
"Jens" wrote:

> If I were you, I would suck and backup as much of the data as you can
> from the database files / disks. Seems to me that this is a hard error
> inidcating that your underlying disks are about to die (or the
> controller has a defect). Backup up and then checking / replacing the
> databases would be the best to do. (for me)
> HTH, Jens Suessmeyer.
>|||All of the errors point to disk problems, but given you are on a SAN(NAS?) I
would expect the problem is not hardware, but either overloading or
networking.
If you NAS/SAN configuration is not tuned properly, you could get the error
codes you listed.
Another possibility (which is why I added NAS rather than SAN) is that if
you have a bad or misconfigured switch, you could be seeing packe drops if
your server is 100MB and the switch port is 10MB.
Just ideas.
--
Joseph R.P. Maloney, CSP,CCP,CDP
"bryan" wrote:

> Hi
> W2K3 std edition (no SP) - SQL Server Std SP3
> I have a lot of errors showing up in app log on different days and times i
n
> the form of:
> ***********************************
> MSSQLSERVER, Category (2), Event ID: 17055
> Description:
> 18052
> Error: 3314, Severoty:21, State: 4
> ***********************************
> The 'error' number varies between, 3314, 9001 and 823.
> The account is always the same one.
> Trawling through the SQL log - I can see some entries with the following
> detail:
> ***********************************
> database 'XYZ' cannot be opened. it has been marked SUSPECT by recovery. S
ee
> the event log for more information.
> ***********************************
> DBCC CHECKDB shows no errors on this database.
> Any pointers on this very much appreciated.
> All SQL services are currently running.
> Thanks
> Bryan
>
>|||Hi Joseph
Thanks for your comments, always appreciated. I shall certainly take a look
at all your suggestions.
I will update any progress I make.
Best rgds
Bryan
"jrpm" wrote:
[vbcol=seagreen]
> All of the errors point to disk problems, but given you are on a SAN(NAS?)
I
> would expect the problem is not hardware, but either overloading or
> networking.
> If you NAS/SAN configuration is not tuned properly, you could get the erro
r
> codes you listed.
> Another possibility (which is why I added NAS rather than SAN) is that if
> you have a bad or misconfigured switch, you could be seeing packe drops if
> your server is 100MB and the switch port is 10MB.
> Just ideas.
> --
> Joseph R.P. Maloney, CSP,CCP,CDP
>
> "bryan" wrote:
>

Saturday, February 25, 2012

mssql service manager don't start

after a black out mssqlservice doesn't start also if i try to start it manually
it say no errors or alert windows just return to stop status after few second
have an idea?
i don't know much about mssql this program is used only by my main
billing/accountacy program
thank you for your answer
exscuse for my bad english i am italian
Stivi,
I'm not sure that the problem have something to do with this but i think you
can try.
Sometimes happens that the account used with mssqlservice is not well
configured.
Use Services in the administrative tools to see wich account is used to
authenticate mssqlservice. This account must have administrative permissions
in the machine and the password must not expire or be changed by anyone.
after verifying this try to restart the service.
"stivi" wrote:

> after a black out mssqlservice doesn't start also if i try to start it manually
> it say no errors or alert windows just return to stop status after few second
> have an idea?
> i don't know much about mssql this program is used only by my main
> billing/accountacy program
> thank you for your answer
> exscuse for my bad english i am italian
|||Check the application and system event logs to see why the service
isn't starting. If your server didn't have a UPS then the abrupt
shutdown could've damaged files on the hard drive. As a consequence
the service encounters a damaged file and is unable to start.
Hopefully you (or your system administrator) can fix the
problem...otherwise, be prepared to uninstall/reinstall SQL Server
:-(.
On Sat, 26 Nov 2005 03:56:01 -0800, "stivi"
<stivi@.discussions.microsoft.com> wrote:

>after a black out mssqlservice doesn't start also if i try to start it manually
>it say no errors or alert windows just return to stop status after few second
>have an idea?
>i don't know much about mssql this program is used only by my main
>billing/accountacy program
>thank you for your answer
>exscuse for my bad english i am italian

mssql service manager don't start

after a black out mssqlservice doesn't start also if i try to start it manua
lly
it say no errors or alert windows just return to stop status after few secon
d
have an idea?
i don't know much about mssql this program is used only by my main
billing/accountacy program
thank you for your answer
exscuse for my bad english i am italianStivi,
I'm not sure that the problem have something to do with this but i think you
can try.
Sometimes happens that the account used with mssqlservice is not well
configured.
Use Services in the administrative tools to see wich account is used to
authenticate mssqlservice. This account must have administrative permissions
in the machine and the password must not expire or be changed by anyone.
after verifying this try to restart the service.
"stivi" wrote:

> after a black out mssqlservice doesn't start also if i try to start it man
ually
> it say no errors or alert windows just return to stop status after few sec
ond
> have an idea?
> i don't know much about mssql this program is used only by my main
> billing/accountacy program
> thank you for your answer
> exscuse for my bad english i am italian|||Check the application and system event logs to see why the service
isn't starting. If your server didn't have a UPS then the abrupt
shutdown could've damaged files on the hard drive. As a consequence
the service encounters a damaged file and is unable to start.
Hopefully you (or your system administrator) can fix the
problem...otherwise, be prepared to uninstall/reinstall SQL Server
:-(.
On Sat, 26 Nov 2005 03:56:01 -0800, "stivi"
<stivi@.discussions.microsoft.com> wrote:

>after a black out mssqlservice doesn't start also if i try to start it manu
ally
>it say no errors or alert windows just return to stop status after few seco
nd
>have an idea?
>i don't know much about mssql this program is used only by my main
>billing/accountacy program
>thank you for your answer
>exscuse for my bad english i am italian

mssql service manager don't start

after a black out mssqlservice doesn't start also if i try to start it manually
it say no errors or alert windows just return to stop status after few second
have an idea?
i don't know much about mssql this program is used only by my main
billing/accountacy program
thank you for your answer
exscuse for my bad english i am italianStivi,
I'm not sure that the problem have something to do with this but i think you
can try.
Sometimes happens that the account used with mssqlservice is not well
configured.
Use Services in the administrative tools to see wich account is used to
authenticate mssqlservice. This account must have administrative permissions
in the machine and the password must not expire or be changed by anyone.
after verifying this try to restart the service.
"stivi" wrote:
> after a black out mssqlservice doesn't start also if i try to start it manually
> it say no errors or alert windows just return to stop status after few second
> have an idea?
> i don't know much about mssql this program is used only by my main
> billing/accountacy program
> thank you for your answer
> exscuse for my bad english i am italian|||Check the application and system event logs to see why the service
isn't starting. If your server didn't have a UPS then the abrupt
shutdown could've damaged files on the hard drive. As a consequence
the service encounters a damaged file and is unable to start.
Hopefully you (or your system administrator) can fix the
problem...otherwise, be prepared to uninstall/reinstall SQL Server
:-(.
On Sat, 26 Nov 2005 03:56:01 -0800, "stivi"
<stivi@.discussions.microsoft.com> wrote:
>after a black out mssqlservice doesn't start also if i try to start it manually
>it say no errors or alert windows just return to stop status after few second
>have an idea?
>i don't know much about mssql this program is used only by my main
>billing/accountacy program
>thank you for your answer
>exscuse for my bad english i am italian

MSSQL Server 2005 Not Reporting Errors to Windows Event Log

Hello All,

I just performed a fresh install of MSSQL 2005 Server Developer Edition on my XPSP2 machine along with MSSQL 2005 SP1 and I noticed that errors are not being reported in the Windows Event Viewer. Is there a way to enable/disable logging here?

I need to view these logs because when the tasks > 'copy database' task fails it submits its error in the Windows Event Log however since I reinstalled MSSQL 2005 these log entries don't appear here.

thanks in advance.

Hi,

if you are using a job for this you can switch the Windows event logging on.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Its not a job. I just manually select the task from Management Studio. In the last installation performing this task created log entries in the windows event log but for some reason they aren't appearing now.

|||

Hi:

The main log for SQL Server 2005 installation has changed, and placed in the following location:

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

For more information, please refer to the following MSDN reference.

http://msdn2.microsoft.com/en-us/library/ms143702.aspx

Hope this helps. :-)

Thanks.

|||

Interesting... I wonder why events don't show up in the Windows Event Log anymore? Especially since MSSQL 2005 specifically says that it will make log entries in the Windows Event Log in the Copy Database task wizard.

|||

Hi,

If the Severity Level is 19 or Higher then only it will be logged in the Windows Event Log.

HTH

Hemantgiri S. Goswami

Monday, February 20, 2012

MSSQL SELECT error

I've the following Select Statement that generates errors, could someone tells me why? :(

SELECT TOP 20 * FROM tickets WHERE ticket_ID NOT IN (SELECT TOP 20 * FROM tickets ORDER BY ticket_ID DESC) ORDER BY ticket_ID DESC;

Warning: mssql_query() [function.mssql-query]: message: Only one expression can be specified in the select list when the subquery is not introduced with EXISTS. (severity 16) in c:\Inetpub\wwwroot\schoolProject\admin\show.php on line 437Try this ??

SELECT TOP 20 * FROM tickets WHERE ticket_ID NOT IN (SELECT TOP 20 ticket_ID FROM tickets ORDER BY ticket_ID DESC) ORDER BY ticket_ID DESC

You had it checking the id against all columns - take it you are trying to get the 21st to 40th most recent??

MSSQL Replication (Type Merge)

Hello, i have this 2 errors. Pleas for help.
The process could not check existence of generation at the 'Subscriber'.
(Source: Merge Replication Provider (Agent); Error number: -2147201003)
General network error. Check your network documentation.
(Source: SERWER (Data source); Error number: 11)
Access to internet is ok.
On Firewall all is allow.
Greeting Huryn Adrian.
You are having one of two issues.
1. Network connectivity
2. You are having blocking issues within the merge metadata tables which
means you are probably carrying around too much tracking information.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Adrian Huryn" <ahuryn@.ist.net.pl> wrote in message
news:20060210100829.af82c9a0.ahuryn@.ist.net.pl...
> Hello, i have this 2 errors. Pleas for help.
> The process could not check existence of generation at the 'Subscriber'.
> (Source: Merge Replication Provider (Agent); Error number: -2147201003)
> General network error. Check your network documentation.
> (Source: SERWER (Data source); Error number: 11)
> Access to internet is ok.
> On Firewall all is allow.
> Greeting Huryn Adrian.
|||On Fri, 10 Feb 2006 12:43:22 -0600
"Michael Hotek" <mike@.solidqualitylearning.com> wrote:

> You are having one of two issues.
> 1. Network connectivity
I have this check, pings/tracerouts are good. On bouth sites all work fine.

> 2. You are having blocking issues within the merge metadata tables which
> means you are probably carrying around too much tracking information.
What i can make here ?
Greeting, Huryn Adrian.
|||You need to validate that you get make a connect from your Subscriber to your
Publisher. If you can make a SQL connection then look at adjusting the
Subscriber Merge Agent Profile to a Slow Link Profile because this your
subscriber might have a slow connection and you need to lengthen the timeout
settings.
The blocking issues and/or large number of records in the merge replication
tables. I have used the following process successfully but I have one
replication which makes this process easier to implement.
Look up in BOL: sp_mergecleanupmetadata
"Adrian Huryn" wrote:

> On Fri, 10 Feb 2006 12:43:22 -0600
> "Michael Hotek" <mike@.solidqualitylearning.com> wrote:
> I have this check, pings/tracerouts are good. On bouth sites all work fine.
> What i can make here ?
> Greeting, Huryn Adrian.
>

MSSQL Nested queries

Hi,

I have been trying to write a nested query, however i am facing errors while executing that.

The code is as below.

Dim MyConnection =New SqlConnection()

MyConnection.ConnectionString = ConfigurationManager.ConnectionStrings("AppConnectionString1").ConnectionString

MyConnection.Open()

Dim cmdAsNew SqlCommandDim rsAs SqlDataReaderDim rs2As SqlDataReaderDim query ="select count(bank_id) from bank_master"Dim query2AsString

cmd.CommandType = CommandType.Text

cmd.Connection = MyConnection

cmd.CommandText = queryrs = cmd.ExecuteReaderIf rs.Read()ThenDim rec = rs(0)If (rec > 0)Then

Response.Write(rec &

" banks registered in the system")rs.Close()

query2 ="select * from bank_master order by bank_id"

rs2 = cmd.ExecuteReader(query2)

If rs2.Read()Then

Response.Write(rs2(0))

Else

Response.Write(

"No banks yet registered in the system")EndIfElse

Response.Write(

"No banks yet registered in the system")EndIfEndIf

The error message that i am getting at runtime:

Server Error in '/Accounts' Application.

Input string was not in a correct format.

Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details:System.FormatException: Input string was not in a correct format.

Source Error:

Line 117: Line 118: query2 = "select * from bank_master order by bank_id"Line 119: rs2 = cmd.ExecuteReader(query2)Line 120: If rs2.Read() ThenLine 121: Response.Write(rs2(0))

Source File:E:\WEBHOME\Accounts\bank.aspx Line:119

Could you please help?

Best Regards,

Debashis

Hi Debashis,

It looks to me like the problem may be that you don't have the line:

cmd.CommandText = query2

So you could have your code like:

 Dim MyConnection =New SqlConnection() MyConnection.ConnectionString = ConfigurationManager.ConnectionStrings("AppConnectionString1").ConnectionString MyConnection.Open()Dim cmdAs New SqlCommandDim rsAs SqlDataReaderDim rs2As SqlDataReaderDim queryAs String ="select count(bank_id) from bank_master"Dim query2As String ="select * from bank_master order by bank_id" cmd.CommandType = CommandType.Text cmd.Connection = MyConnection cmd.CommandText = query rs = cmd.ExecuteReaderIf rs.Read()Then Dim rec = rs(0)If (rec > 0)Then Response.Write(rec &" banks registered in the system") rs.Close() cmd.CommandText = query2 rs2 = cmd.ExecuteReader()If rs2.Read()Then Response.Write(rs2(0))Else Response.Write("No banks yet registered in the system")End If Else Response.Write("No banks yet registered in the system")End If End If

I haven't actually tried this code yet, but if this doesn't work, you could try having a cmd2 instead of re-using the single cmd line. I'm also not too sure why you need to run two queries as you could try this instead (unless I missed something Smile ):

 Dim resultAs Integer = 0' Initialise connectionDim MyConnection =New SqlConnection(ConfigurationManager.ConnectionStrings("AppConnectionString1").ConnectionString)' Initialise commandDim cmdAs SqlCommand =New SqlCommand() cmd.Connection = MyConnection cmd.CommandText ="select count(bank_id) from bank_master"' Execute command Using MyConnection result =CType(cmd.ExecuteScalar(),Integer)End UsingIf result > 0Then Response.Write(result &" banks registered in the system")Else Response.Write("No banks yet registered in the system")End If

Hope this helps.

All the best,

Paul

|||

Hi Peter,

Hi Peter,
Thanks for your reply. It seems to be working with: cmd.CommandText = query2
However I am still unable to workout the recordcount from the query, as it returns -1.
The code is:

query2 = "select * from bank_master order by bank_id"
cmd2.CommandType = CommandType.Text
cmd2.Connection = MyConnection
cmd2.CommandText = query2
rs2 = cmd2.ExecuteReader
If rs2.HasRows Then

%>
<table>
<%
While rs2.Read()
%>
<tr>
<td>
<%=rs2(1)%>
</td>
</tr>
<%
End While
%>
</table>
<%
Else
Response.Write("No banks yet registered in the system")
End If

Please note that I havent included the recordcount code, as it wrong!

Thanks

Debashis

|||

Hi Debashis,

Sorry, I had missed a line from my code:

Dim resultAs Integer = 0' Initialise connectionDim MyConnection =New SqlConnection(ConfigurationManager.ConnectionStrings("AppConnectionString1").ConnectionString)' Initialise commandDim cmdAs SqlCommand =New SqlCommand() cmd.Connection = MyConnection cmd.CommandText ="select count(bank_id) from bank_master"' Execute command Using MyConnectionMyConnection.open() result =CType(cmd.ExecuteScalar(),Integer)End UsingIf result > 0Then Response.Write(result &" banks registered in the system")Else Response.Write("No banks yet registered in the system")End If

I've tested it this time and is fine. The other code I gave you also worked, but because there was an extra If ... End if statement than necessary, it also puts the id of the last bank at the end of the line 'banks registered in the system'. therefore, going back to your original code, this also works:

Imports System.DataImports System.Data.SqlClientPartialClass BankInherits System.Web.UI.PageProtected Sub Page_Load(ByVal senderAs Object,ByVal eAs System.EventArgs)Handles Me.LoadDim MyConnection =New SqlConnection() MyConnection.ConnectionString = ConfigurationManager.ConnectionStrings("AppConnectionString1").ConnectionString MyConnection.Open()Dim cmdAs New SqlCommandDim rsAs SqlDataReaderDim queryAs String ="select count(bank_id) from bank_master" cmd.CommandType = CommandType.Text cmd.Connection = MyConnection cmd.CommandText = query rs = cmd.ExecuteReaderIf rs.Read()Then Dim recAs Integer = Convert.ToInt32(rs(0))If (rec > 0)Then Response.Write(rec &" banks registered in the system")Else Response.Write("No banks yet registered in the system")End If rs.Close()End If End SubEnd Class

I put this code in the Page_Load event, and ran it OK.

If this has resolved the issue, please don't forget to mark it as the Answer.

Hope it helps,

Paul (not Peter !)

|||

Hi Paul,

Apologies for the mistake.

It seems to be working fine. Thanks for the help..

Monday, March 12, 2012

MSSQLSERVER errors on PC running MSDE

MSSQLSERVER errors on PC running MSDE

MSSQLSERVER errors on PC running MSDE

MSSQLSERVER error(s) - severity and state

MSSQLSERVER error(s) - severity and state

MSSQLSERVER error(s) - severity and state

Saturday, February 25, 2012

mssql service manager don't start

mssql service manager don't start

mssql service manager don't start

MSSQL Server 2005 Not Reporting Errors to Windows Event Log

Monday, February 20, 2012

MSSQL SELECT error

MSSQL Replication (Type Merge)

MSSQL Nested queries

Server Error in '/Accounts' Application.

Input string was not in a correct format.

MSSQL Mistake

Blog Archive

About Me