ContactReview :: View topic

mesteel · GoldMine Apprentice

Dear all,

We recently installed GMPE 8.01 on 2 servers (A, B).

Recently, one of the server (A) got shutdown abruptly after which GMPE stopped generating automatic backup files. The other server (B) is all ok.

I did below to rectify it:

1) I checked the SQL SERVER AGENT, if it is running and noticed that it was not, though automatic.
2) I tried to start it, but failed with below message:
"The SQL SERVER AGENT service on the local computer started and stopped. Some services stop automatically if they have no work to do, for example, the Performance Logs and Alerts services."
3) I did a cold startup again, but the problem persists.
4) I logged into the SQL Server Management Studio and checked for the database and its all ok. Under Management, when I click on Maintenance Plans, it gives me an error, from which I understand that there is some problem with that part of it and not whole database as such.

When I checked on the error log, I found below error:

"SQL Server detected a logical consistency-based I/O error: incorrect checksum (expected: 0x582a3378; actual: 0x59f15a83). It occurred during a read of page (1:800) in database ID 4 at offset 0x00000000640000 in file 'E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\MSDBData.mdf'. "

My question is:
Can I copy MSDBData.mdf from the other server (B), which is working properly and paste it in server (A), so that the maintenance plans trigger as and when necessary.

Otherwise, I would appreciate an alternate solution for this to get rectivied.

By the way, is there an any manual way to get around on this. Does linking server A & B yield any results, using Linked Servers?

Raj

DJ · GoldMine Guru

Detach the database that you believe to be corrupt.

Copy it to another location.

Detach the good database.

Copy the good database to the other Server.

Attach the good database on the good Server.

Attach the good database on the bad Server.

Cross your fingers.

DougCastell · GoldMine Guru

if you have a lot of SQL users and permissions defined, a database from another server needs some tweaking in that regard since user BOB on one SQL server is not the same sid as used BOB on another SQL server.

I would also suggest patching your SQL server to the latest service pack...

As to your SQL Agent no starting issue, there is a known problem (I believe it's fixed in later service packs) where SQL Agent will fail to start due to the order the other SQL services are started in... Short of monkeying around with windows to properly time the services to start in proper order to work-around the bug, just patch it and get the fix...

mesteel · GoldMine Apprentice

Dear Hunt & Castell,

Thank you for your replies. We are trying to restored the corrupted one from our backup.

I am faced with a new problem. I tried to stop the SQL Agent service on one of our server and tried to restart it, but I get Error 1058 with below message. We have windows 2003 server with all latest updates installed.

Could not start SQL Server Agent (MSSQLSERVER) service on Local Computer.
Error 1058: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Raj

DJ · GoldMine Guru

Is this installation on a true Server operating system?

Is it a Peer-to-Peer with no true Server operating system?

mesteel · GoldMine Apprentice

This GMPE installation is on our Domain Controller.
Didnt get what you meant by true Server!

DJ · GoldMine Guru

Server 2000?

Server 2003?

Server 2008?

DougCastell · GoldMine Guru

have you patched to the most recent SP of SQL? Does the problem persist?