MainBossWeb Troubleshooting

This help file applies to an out-of-date version of MainBoss.
The most recent version of MainBoss is MainBoss 4.2.3.
This help file does not exist in MainBoss 4.2.3, but the index for that version can be found here.

< Previous section  |  Table of Contents  |  Index  |  Next section >

This section lists a number of error messages you might see when trying to use MainBossWeb, plus ways to correct the problems.

There was a problem validating access to the database XXX on server YYY. The database-principal 'dbo' does not exist or user is not a member. Failed SQL command is: declare @result int; exec @result = sp_getapplock 'MainBossSession', 'shared', 'session', 0, 'dbo'; select @result This indicates you did not give permissions to the login name for the identity of the application pool where MainBossWeb runs. Follow the instructions in Application Pools. An error occurred while processing your request. Database server 'ServerMainBossDatabaseIsOn' was not found or was not accessible. This indicates that you did not change the default dbserver application setting. See Application Settings of this guide.

Could not load file or assembly 'System.Web.Mvc' or one of its dependencies. Access is denied. This indicates that you did not give DOMAIN\IIS_MAINBOSS read/write file system privileges to the directory containing temporary ASP.NET files. See the previous section of this guide for more information.

Note: Whenever you encounter diagnostic messages, you can usually find useful information by typing them into Google and searching for information.

The Windows Firewall: In our experience, many of the difficulties that arise when configuring MainBossWeb are due to firewall problems. If the Windows firewall is not adjusted to allow various information to pass through, MainBossWeb will not work. Firewall problems are especially difficult to diagnose because they generate no error messages or log entries; you just don't see anything happening.

Requestor Rejection Errors: Requests may be rejected for a variety of reasons. For example, suppose you have reached the limit of authorized requestors allowed in the Requestors table according to your license keys. If a new requestor attempts to submit a request, the request will be rejected, even though the person would otherwise be accepted according to your MainBoss Service configuration options.

< Previous section  |  Table of Contents  |  Index  |  Next section >