Client Management Suite

OK - had an issue yesterday where my licensing seemed to go haywire due to outdated certs .(eh!) I removed these and reapplied the licnses - that seemd to be fine. Now I have lodas of errors in the logs erlating to SQL - Can anyone help. No changes have been made - the service account altiris uses is fine.

see screenshot :

Looks like a simple communications problem, the NS can't see the SQL server.

Go to the Database Settings page in NS and see if the drop down list under "Use existing database" shows any other databases on the SQL server, can they be read?

The DB connection is fine as far as I can see - I went into SQL studio manager and tested in there and it accesses OK.

"Go to the Database Settings page in NS and see if the drop down list under "Use existing database" shows any other databases on the SQL server, can they be read?"

I did that and the drop downlist shows the CMDB DB and all other arcserve DB's. If I chnage it, then change back to CMDB its still OK>

Can you open SQL Server Management Studio "run as" the Altiris service account and check connection like that?

Check the SQL Server Error logs too.

There was nothing wrong with the account or SQL. I've repaired CMS using SIM which has fixed some issues. Still have problems with deploying Windows now. do you know if you run a repair it recreates the preboot environemnt ?

I'm afraid I don't know. You could recreate the preboots your self, or check the status from the recreate screen.

Spoke too soon - the erros are back. Deployment doesn't work. Logged a ticket with support. The galling thing is I have MS deployment toolkit running on our own system and I never get problems like this. Grrr - If only I could travel back in time!

OK, how about the SQL Server log?

Maybe try a SQL trace and examine the times you've got the error in detail.

Lookslike this may have been the issue.

http://www.symantec.com/business/support/index?page=content&id=TECH194869

Looking OK so far but still testing.

Or it could be something slightly different.

If you have SQL named instances then the SMP will first query the server on port 1434 via UDP. Once the server responded the connection will be established on port 1433.

Now, I had this issue with a customer a few weeks back, and it turned out that the SQL Browser service just needed a little restart to get back to work. With that done the server was back in workign order, connecting to SQL with no fuss.

BTW, on that case the worse thing was that it happened whilst the customer upgraded to MP1, so it first felt like an installation problem when it was just a SQL connectivity issue.