Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Symantec Management Server Error

Updated: 21 May 2010 | 9 comments
Qwerty's picture
0 0 Votes
Login to vote

I Installed Symantec Management Platform 7.0.3876, SP1 7.0.4739 with MSSQL 2005 Express Edition, everything worked fine. I wanted to upgrade to MSSQL 2005 Standard Edition so I didn't have as many limitations. First I Installed 2 updates for the Management Platform SP1 HF2 7.0.4756 and Documentation Update 7.0.1010 then I unistalled MSSQL EE & Installed MSSQL 2005 SE. (I'm not surprised something went wrong). Now when I try to activate the Console the big Symantec Management Server Error Sign shows up. Here is the Error Log:

(I'm pretty sure the server allows remote connections, when I go to the surface area configuration for services and connections->MSSQLSERVER->database Engine->Remote Connections the local and remote connections are enabled).

Log File Name: C:\Program Files\Altiris\Notification Server\Logs\a.log

Priority: 1

Date: 7/17/2009 3:16:41 PM

Tick Count: 3925125

Host Name: CS-ALTIRECO

Process: w3wp (5744)

Thread ID: 17

Module: w3wp.exe

Source: Altiris.TaskManagement.ClientTask.*

Description: BaseXmlCallback Exception: Altiris.NS.Exceptions.DatabaseNotReadyException: Failed to construct DatabaseContext object. Connection to database failed. ---> Altiris.NS.Exceptions.AeXException: Failed to open database connection. Current user is CS-ALTIRECO\Administrator. Error: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) ---> System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)

at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)

at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)

at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)

at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)

at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)

at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)

at System.Data.SqlClient.SqlConnection.Open()

at Altiris.NS.Utilities.DbUtils.OpenConnection(SqlConnection dbConn)

--- End of inner exception stack trace ---

at Altiris.NS.Utilities.DbUtils.OpenConnection(SqlConnection dbConn)

at Altiris.NS.Utilities.DbUtils.CreateConnection(String configKey)

at Altiris.NS.ContextManagement.AdminDatabaseContext.OpenDbConnection()

at Altiris.Database.DatabaseContext`1.Initialize(Boolean beginTransaction, IsolationLevel isolationLevel)

--- End of inner exception stack trace ---

at Altiris.NS.ContextManagement.AdminDatabaseContext.ThrowDatabaseNotReadyException(String exceptionDetails, Exception innerException)

at Altiris.Database.DatabaseContext`1.Initialize(Boolean beginTransaction, IsolationLevel isolationLevel)

at Altiris.Database.DatabaseContext`1.GetContext(Boolean createNewTransaction, IsolationLevel isolationLevel, Boolean independentContext)

at Altiris.Database.DatabaseContext`1.GetContext(Boolean createNewTransaction, IsolationLevel isolationLevel)

at Altiris.Database.DatabaseContext`1.GetContext(Boolean createNewTransaction)

at Altiris.NS.ContextManagement.DatabaseContext.GetContext(Boolean createNewTransaction)

at Altiris.TaskManagement.ClientTask.BaseWeb.RegisterTaskServer.WriteResponse(XmlTextWriter wr)

at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)
at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)

Comments

jharings's picture
20
Jul
2009
0 Votes 0
Login to vote

Once you replaced your SQL version

did you do a repair of NS to get the configuration confirmed and setup? In v7 this is done from Symantec Installation Tool, accessible from start - programs.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Qwerty's picture
20
Jul
2009
0 Votes 0
Login to vote

Repair

No I didn't - would that be the Symanet Management Platform, SP1, HF2 or recovery solutions that needs the repair?

Qwerty's picture
20
Jul
2009
0 Votes 0
Login to vote

It doesnt look like I can

It doesnt look like I can repair or modify the Symantec Management Platform 7.0.3876, only uninstall.

Qwerty's picture
20
Jul
2009
0 Votes 0
Login to vote

I repaired all of the

I repaired all of the programs I could, didn't help.

jharings's picture
20
Jul
2009
0 Votes 0
Login to vote

Are you doing this from add\remove or from the SIM platform?

You should be able to repair everything from the SIM installer platform.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Qwerty's picture
20
Jul
2009
0 Votes 0
Login to vote

From the SIM platform. I'm

From the SIM platform. I'm just unistalling everything now and starting from scratch.

jharings's picture
20
Jul
2009
1 Vote +1
Login to vote

Ok, sorry to not be of more help

If you database is still good, make sure to point the install to the existing database. It will save  you some hassle.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

sdudnik@croc.ru's picture
23
Jul
2009
0 Votes 0
Login to vote

Error during intallation

Hi! I have a problem.

Log File Name: C:\Program Files\Altiris\Notification Server\Logs\a3.log
Priority: 2
Date: 7/23/2009 4:34:03 PM
Tick Count: 2133515
Host Name: ALTIRIS2
Process: AeXSvc (1264)
Thread ID: 25
Module: AeXSVC.exe
Source: NSMessageQueue
Description: Failed to receive NS message (GUID: '9f8e5f34-3d89-4b01-b738-eaebab72edf6' Class: '77c3cbc7-fca4-4cfb-abf9-af6845b1ff39'): Failed to construct DatabaseContext object. Connection to database failed.

imagebrowser image

telegon's picture
23
Jul
2009
1 Vote +1
Login to vote

Database error

Looks like the account your using to access and create the database doesn't have the necessary privileges.

Try restarting the installation process after you create and verify ODBC access to the server.

Hope that helps,
Jim