Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Instance of MSSQL 2005 database in Microsoft cluster no more reachable

Posted on 2014-03-14
8
Medium Priority
?
458 Views
Last Modified: 2014-03-29
Hello,
one of our customers has a Windows 2003 Enterprise 64bit cluster with an instance of MSSQL server 2005 standard sp2 that is no more reachable by the clients and via management studio we get a timeout.
Could we try to upgrade to sp4?
Which logs we have to look for to have more information on the issue?
In event viewer we see these errors (in italian):

Tipo evento:      Errore
Origine evento:      SQLSERVERAGENT
Categoria evento:      Service Control
ID evento:      103
Data:            14/03/2014
Ora:            14.56.06
Utente:            N/D
Computer:      SQLSERVER
Descrizione:
SQLServerAgent could not be started (reason: Impossibile connettersi al server '(local)'. Impossibile avviare SQLServerAgent.).

Per ulteriori informazioni, consultare la Guida in linea e supporto tecnico all'indirizzo http://go.microsoft.com/fwlink/events.asp.

Tipo evento:      Errore
Origine evento:      WinMgmt
Categoria evento:      Nessuno
ID evento:      10
Data:            14/03/2014
Ora:            14.57.25
Utente:            N/D
Computer:      SQLB
Descrizione:
Impossibile attivare il filtro eventi con query "select * from __InstanceModificationEvent within 10 where TargetInstance isa 'Win32_Service'" nello spazio dei nomi "//./root/Microsoft/SqlServer/ComputerManagement"  a causa dell'errore 0x80041010. Potrebbe essere impossibile utilizzare questo filtro per consegnare gli eventi se  non sarà risolto il problema.

Per ulteriori informazioni, consultare la Guida in linea e supporto tecnico all'indirizzo http://go.microsoft.com/fwlink/events.asp.

Thanks
0
Comment
Question by:SIES di Andrea Barbon
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
8 Comments
 
LVL 20

Expert Comment

by:Marten Rune
ID: 39930985
Don't upgrade an instanse thats unresponsivt!

Is the sql server service started?

What does the errorlog say?
http://technet.microsoft.com/en-us/library/ms187885(v=sql.90).aspx

What does application log say when sql starts?

Regards Marten
0
 

Author Comment

by:SIES di Andrea Barbon
ID: 39933783
Hello Marten thanks,
yes the sql server service is started, the sql server agent service does not start and gives the error 103.
The error log doesn't tell me anything but I never work with sql... so I attached it.
The aplication log shows only the two errors I posted even when I restart it.
regards
Andrea
ERRORLOG
0
 
LVL 18

Expert Comment

by:x-men
ID: 39933878
look like a problem in the WMI database/repository.

cjeck this article http://networkadminkb.com/KB/a193/how-to-fix-missing-wbemadap-registry-value-names.aspx
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
LVL 20

Expert Comment

by:Marten Rune
ID: 39934113
Make sure you use SSCM (SQL Server Configuration Manager) when changing the account,
http://msdn.microsoft.com/en-us/library/ms191543.aspx

Regards Marten
0
 

Author Comment

by:SIES di Andrea Barbon
ID: 39934842
They did not change the user of the service and is a domain admins member.
0
 

Accepted Solution

by:
SIES di Andrea Barbon earned 0 total points
ID: 39950301
Hello everyone,
the problem was caused by a faulty memory bank in the server sqla, the failure probably happened when they were moving the sql service between cluster members.
The issue has been fixed reinstalling from scratch the servers.

Thank you for all the answers.

Andrea
0
 

Author Closing Comment

by:SIES di Andrea Barbon
ID: 39963516
It's not a solution, the problem was caused by a hardware failure.
After having changed the faulty memory bank we reinstalled.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windocks is an independent port of Docker's open source to Windows.   This article introduces the use of SQL Server in containers, with integrated support of SQL Server database cloning.
Ready to get certified? Check out some courses that help you prepare for third-party exams.
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
Via a live example, show how to backup a database, simulate a failure backup the tail of the database transaction log and perform the restore.

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question