Deployment Solution

 View Only
  • 1.  Database Error

    Posted Oct 19, 2011 09:31 AM

    When setting the domain accounts in Altiris 6.9 SP5, I get the following error message. "Could not find server 'NameofServer' in sys.servers. Verify that the correct server name was specified. If necessary, execute the stored procedure sp_addlinkedserver to add the server to sys.servers.

    My question is from where is this process performed, and where is the stored procedure?



  • 2.  RE: Database Error

    Posted Oct 19, 2011 12:33 PM

    Hi Peter,

    1.Make sure that the Altiris Deployment Server DB Management service is actually running.

    2. It is required that the Altiris eXpress Server service and Altiris Deployment Server DB Management service are running as a user that has DBO rights to the eXpress database. Check to ensure that the account that the Altiris Deployment Server DB Management service is running as has DBO rights to the eXpress database.

    3. Another requirement of the Altiris Deployment Server DB Management service login is that it has administrative rights on the SQL machine as well as the machine it is running on. Check the Windows authentication on both the SQL machine and the machine running the Altiris Deployment Server DB Management service.

    4. Make sure that the Altiris Deployment Server DB Management service has rights to run as a service.

    Regards,



  • 3.  RE: Database Error
    Best Answer

    Trusted Advisor
    Posted Oct 20, 2011 04:06 PM

    Have you changed the name of the server where SQL is installed, after installing SQL? This error is normally seen after changing the computer name.

    See tech24682 for a resolution to this.



  • 4.  RE: Database Error

    Posted Nov 28, 2011 11:15 AM

    Thank you for reminding me that SQL is as persistent as a virus. Not only was the name changed, but so was the domain and IP. My eventual resolution was to reinstall the OS and SQL and then install the application and now everything seems to be funtioning correctly. I think in the long run, from moving from W2K3 and SQL 2005 to W2K8 and SQL 2008 will be a better solution and better results.