Cheshire

I have inherited a very botchy instal of RDP 3.81. I hoped an immediate upgrade would have corrected something, but with the amount of errors and prior mis-configurations, I havn't been so lucky.

Is there anything in particular I should be careful to ensure is backed and saved elsewhere if I was to go ahead with a complete uninstall before installing RDP 3.82?

Thank you in advance,


-Aaron

Brandon

Export all the (custom) jobs in 3.81 first to a bin file. Then perform an upgrade to 3.82 and back them up in the format as well. Then re-do a clean installation. If you don't have custom jobs then it doesn't matter. The problem is you can't import a 3.81 job into a 3.82 console I believe. To be safe I would back up the db as well (eXpress).

__________________
Brandon

Cheshire

Thanks Brandon, I'll try that and get back to you.

-Aaron

Cheshire

Alright, so I've completed the full uninstall and re-install. Unfortunatly the same issue is still there.

I've enabled any log files I could find associated with Altiris / SQL and looked over the computer's logs.
This is what it's turned up:

-----------
axengine.log;
- Unknown exception was caught in CRxEngineMMConnection::Connect.
- Error reading from socket (2068), Error: 10053 (10053 (WSAECONNABORTED))
- Error 10053 (WSAECONNABORTED) during recv () on socket (2068).

Agent communications with engine is clean.

SQL Server Logs are all empty.

SQL activity monitor has multiple entries with DOMAIN1/USER1 associated with the eXpress database & sleeping.

Altiris Console Log is clean.

Altiris Data Manager;
-eXpressDatabase; Error 11: General network error. Check your network documentation.
-eXpressDatabase
Error 4060: Cannot open database "eXpress" requested by the login. The login failed. Login failed for user 'DOMAIN1\USER1'.

Application Log;
-Altiris Deployment Server; Service cannot be started. The service process could not connect to the service controller.
-Altiris Deployment Server; Event ID 3; Incorrect syntax near the keyword 'and'. Statement(s) could not be prepared.
-MSSQLSERVER; Event ID 17187; SQL Server is not ready to accept new client connections;
-Altiris Deployment Server; Event ID 3;SQL Server does not exist or access denied. ConnectionOpen (Connect()).
-mm; Event ID 3; SQL Server does not exist or access denied. ConnectionOpen (Connect()).

System log;
Lots of DCOM errors
-----------

Regarding the WSAECONNABORTED errors with recv from the axengine.log. I was able to find it was supposedly a known issue with Server 2003 sp2 x86, and I applied the hotfix offered by Microsoft. Unfortunatly, that hasn't stopped it.

Anything regarding SQL and Altiris I've looked up and followed guide verbatim off Symantecs site.

Is there any additional logs I should enable / where would they be

My appoligies for coming here and asking so many questions. I do truly appreciate all the help and suggestions.

Sincerely,


-Aaron