Problem

User has found in Asset Reliability r25.0.0 when packaging the Smart Client that they could not deploy the smart client to the server manager. The packaging would appear to package successfully but when the user selected the option to deploy they would receive a "(500) Internal Server Error.".

 

Solution

This was reported as a bug, VSTS #1588913, 

The workaround is to manually copy the smart client package to the server manager share. This is done by choosing No to deploying when the smart client package has finished generating.

The resulting files will be placed into a share and open automatically. Manually copy these files to the server manager's deployment folder.

Alternatively, the user can deploy using Bentley Connect Authentication, instead of MSWindows Authentication.