Could not login to calendar server
Dec 07, 2005 04:15 PM
I received a "Could not login to calendar server" error accessing Calendar in WebMail
The error can occur in these cases:
- GroupWare service is not running
- Port for GroupWare service is not open
- GroupWare service is not enabled for appropriate account
- The ODBC Connection for GroupWare is not set properly or the DB is not accessible
- GroupWare engine is not enabled at all
- The DSN (Data Source Name) for GroupWare wasn't installed properly
To check these issues follow the directions:
GroupWare service is not running
Go to System / Services menu node in the VisNetic MailServer Admin Console and check if the GroupWare service is running.
Try to restart the service.
Port for GroupWare service is not open on your FireWall/Router
By default, the GroupWare service runs on port 5229. You can see that in System / Services / Edit the GroupWare service. Verify this port is opened on your FireWall or Router.
GroupWare service is not enabled for appropriate account
This depends on the Processing Mode for GroupWare. To see that click the Processing Mode button in GroupWare menu node / General tab in the VisNetic MailServer Admin Console.
The following dialog shows you which mode you have set. By default it is set to Process All.
The ODBC Connection for GroupWare is not set properly or the DB is not accessible
Go to GroupWare menu node and click the ODBC Settings button. The default connection is set to VisNeticGroupWare DSN which is pointed to the calendar.mdb file in VisNetic MailServer\Calendar folder.
Click the Test Connection button to see if everything is ok.
If test is not successful you need to check if the DSN was installed or set properly - see last point in this FAQ.
GroupWare engine is not enabled at all
Go to GroupWare menu node and check if the Active checkbox is enabled.
The DSN (Data Source Name) for GroupWare wasn't installed properly
It could be caused by the installation process or VisNetic MailServer wasn't setup with full rights on the server. Be sure you have installed VMS with an account with full permissions. You can fix that by creating the DSN on your own or by reinstalling VMS again with an account with full permissions on the server. It is recommended that you reinstall VMS because it could cause additional problems if VMS was installed without full permissions.