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
- Go to Windows Control Panel, Administrative Tools, Component Services
- Click Services
- Locate the Sage 300 ERP .Net Remoting Service
- Right-click Stop, to stop the service
- 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
- Right-click on Sage 300 ERP .NET Remoting Service
- Click Properties
- Click on the Log On tab
- 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
- Go to Windows Control Panel, Administrative Tools, Component Services
- Click Component Services, Computers, My Computer, COM + Application
- Locate the Accpac ASP service
- Right-click the Accpac ASP service
- Click Properties
- Click on the Identity tab
- 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