There are seven causes listed in order of occurence:
Note: These steps have worked for some users and are quick to try, so try these steps before trying the other solutions.
The best option is to Highlight where it states Unable to connect. The second paragraph will give you a more detail resolution.
Give domain users who are going to be using the console read/execute access permissions to C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys.
Allow this right to propagate to all files and directories under it.
There are two things that you need to make sure of with this solution.
Run the DSDBsecurity located in the .\techup\windows directory. Located in the Deployment Share.
(DS 6.1) Change the serverProviders line in the DataManager.exe.config file (which located in the Deployment Server Directory), by default 6.5 already has this change:
formatter ref="binary" typeFilterLevel="Full"/>
This disables encryption between DataManager and the Web Console.
(DS 6.5) Delete the Providers line in the DSWeb.dll.config file (which is located in the Deployment Web Console\DSWeb directory):
<provider type="Altiris.DSSDK.Remoting.SecureClientChannelSinkProvider, AxDsDm" algorithm="DES" oaep="false" maxRetries="1" />
(DS 6.8) Delete the Providers type line in the DataManager.exe.Config file (which is located in the Deployment Server directory):
<provider type="Altiris.DSSDK.Remoting.SecureServerChannelSinkProvider, AxDsDm" algorithm="DES" oaep="false" requireSecurity="true" connectionAgeLimit="900" sweepFrequency="450"/>
Make certain to leave this line <formatter ref="binary" typeFilterLevel="Full"/> in the file though.
Note - Port 8080 is the default port used by the Deployment Server GUI installation; however if axinstall.exe is used to script the installation of Deployment Server (using a silent.ini file), make sure the value SeDataManagerPort=8080 is defined in the silent.ini - otherwise Deployment Server will use Port 80 as its default port.
Make sure the user account that the Data Manager is using to log on to the database is a domain admin account or an account that is a DBO for the database, not just an account that has the DBO role right.
Reload the .NET framework by doing the following:
This procedures need to be done on the Deployment Server computer. After applying each solution, verify that the error still exists before trying the next solution.
Deployment Solution 6.1, 6.5 or 6.9
Deployment Server Stand-alone Web Consoles 6.1, 6.5, 6.9
Deployment Solution 6.1, 6.5 or 6.9 Deployment tab within the Altiris Notification Server Console.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.