Deployment Manager - 1.0

 

Common errors - Deployment Manager

This page describes the following common errors:

'Unable to generate a temporary class (result=1)' error

If the IIS_IUSRS group does not have permission to read/write from the Windows Temp folder, you will see the following error when browsing the web interface:

Unable to generate a temporary class (result=1)

Fix

To grant permission to the IIS_IUSRS group:

  1. In Windows Explorer, browse to C:\Windows.
  2. Right-click on the Temp folder, and then click Properties.

    The Temp Properties dialog box is displayed.

  3. On the Security tab, click Advanced:

    The Advanced Security Settings for Temp dialog box is displayed.

  4. On the Permissions tab, click Continue:

  5. Under the Permission entries list, click Add:

    The Select User, Computer, Service Account, or Group dialog box is displayed.

  6. Click Locations:

  7. Select the local machine, and then click OK.
  8. In the Enter the object name to select box, type IIS_IUSRS, and then click Check Names:

    The IIS_IUSRS object name is expanded and underlined.

  9. Click OK.

    The Permission Entry for Temp dialog box is displayed.

  10. Under Permissions, select the check box to allow List folder / read data:

  11. Click OK.
  12. On the Advanced Security Settings for Temp dialog box, click OK, and then on the confirmation dialog box that is displayed, click Yes:

'Could not load type 'System.Management.Automation.PowerShell'...' error

If the computer you have installed Deployment Manager on does not have Windows PowerShell 2 (or later) installed, you will see the following error when you launch the server administration application:

Fix

You need to install Windows PowerShell 2:

'SocketException: No connection could be made...' error

You may receive this error when Deployment Manager server or the web interface are starting up:

SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:10930

The causes for this may be:

  • The Deployment Manager service is not running

    To start the service manually:

  1. In the Start menu, type services.msc, and then click services.
  2. In the Services dialog box, right-click the Red Gate Deployment Manager service, and then click Start:

  • Some kind of anti-virus or other security software is preventing the connection
  • You have multiple IP addresses, and HTTP.SYS is only bound to one of them

    This is a common configuration when you are using, for example, a Tomcat-based service (like TeamCity) and Deployment Manager on the same machine. You can check this via:

    netsh http show iplisten

    To solve it, either add 127.0.0.1 to the list of IP addresses HTTP.SYS can listen on using:

    netsh http add iplisten 127.0.0.1

    Or, in the registry under HKLM\Software\Deployment Manager, you can add the following string value:

    Deployment Manager.Raven.HostName = <host name or IP address to use>

'A required anti-forgery token was not supplied...' error

You may receive this error when trying to log in to the Deployment Manager web interface:

A required anti-forgery token was not supplied or was invalid

The causes for this error may be:

'There was a problem processing your request...' error

You may see the following error when adding a package step, or testing a package feed:

This error occurs when Deployment Manager has a problem connecting to a package (NuGet) feed.

Fix

To avoid this error, make sure that:

  • You have specified the correct URL for your feed in the Deployment Manager web interface
  • Your feed is running
  • Your Deployment Manager server can see the machine your feed is running on
  • Your feed and network are not overloaded

You can check that your feed is running, and that Deployment Manager can see the machine the feed is running on, by navigating to the feed URL in a web browser.

DeploymentManager.exe - Microsoft.CompilerServices.AsyncTargetingPack.Net4 error

You may see the following error when using the DeploymentManager.exe command line:

System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.CompilerServices.AsyncTargetingPack.Net4, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

This error can occur if if you have moved DeploymentManager.exe to a different location on your computer.

DeploymentManager.exe requires the Microsoft.CompilerServices.AsyncTargetingPack.Net4.dll file to be in the same location.

Fix

If you want to move DeploymentManager.exe to a different location on your computer, you must also move Microsoft.CompilerServices.AsyncTargetingPack.Net4.dll to the same location. You can find Microsoft.CompilerServices.AsyncTargetingPack.Net4.dll in your Deployment Manager installation location, in the Tools folder.

Deployment Manager server/machine communication

You can test whether Deployment Manager is able to reach a target machine (traversing firewall rules, etc.) by remoting to the Deployment Manager server, and pointing your web browser at http://your-machine-host-name:10933 (or whichever port you chose for machine to listen on).

If you see this error:

System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: An error occurred when verifying security for the message.

It can sometimes happen because the clock on one of the two machines is out-of-sync.

Was this article helpful?

Search support
Forums
Visit the Deployment Manager forum.
Learning Deployment Manager
Knowledge base

all SQL products

all products

Notes & articles

all SQL products

all products