Session could not be opened, occurs when logging into Web Deployment in Sage 300

Summary

The following error may appear when logging into Web Deployment: “Session could not be opened”

Resolution

The error may be resolved as follows:

  • Verify that you can logon to the desktop version of Sage 300 ERP successfully
  • Stop the .Net Remoting Service on the server and try to start it
    1. Go to Windows Control Panel, Administrative Tools, Component Services
    2. Click Services
    3. Locate the Sage 300 ERP .Net Remoting Service
    4. Right-click Stop, to stop the service
    5. Right-click Restart to restart the service
  • If the service could not start, reboot the server and try again
  • In some cases, the Windows Event logs needs to be emptied before the .Net Remoting service can restart
  • .Net Remoting service will not restart if it is using a Windows Local System account instead of a Windows user with both Windows Domain and Local Administrator rights
    1. Right-click on Sage 300 ERP .NET Remoting Service
    2. Click Properties
    3. Click on the Log On tab 
    4. Verify that you use a designated Windows user account with both domain and local administrator rights instead of the Local System account

Verify the Accpac ASP is running

  1. Go to Windows Control Panel, Administrative Tools, Component Services
  2. Click Component Services, Computers, My Computer, COM + Application
  3. Locate the Accpac ASP service
  4. Right-click the Accpac ASP service
  5. Click Properties
  6. Click on the Identity tab
  7. Verify that you use a designated Windows user account with both domain and local administrator rights instead of the Local System account

Rerun Web Deployment Wizard if the above steps do not work