Troubleshooting - MasterCal
- I can create an event in the public Calendar, and it sends the notification correctly. However when I run the server-side program I get an email saying unresolved mailboxes. I have tried a number of variants for adding the attendees including their SMTP addresses and their Exchange aliases, but none seem to be recognized.
Resolution:
The 'Run As' account specified in the program settings does not have access rights to users' mailboxes.
This account should never be Admin or Administrator - Administrator accounts are explicitly locked out of mailboxes on Exchange2000+.
This is a security feature implemeted by Microsoft and is very complex to change. It is recommended you configure a new network account to use with MasterCal
that has Read/Write/Delete permissions to the Private Mailbox Store on your Exchange Server.
- I received the following error message: 'Error: X; - Init_Master_Session()'
Resolution 1: Run As account must be a Local Admin.
The 'Run As' account must be part of the 'Local Admins' group for the PC that is running MasterCal.exe in order to create a MAPI Session for MasterCal to run.
Resolution 2: Run As account must have an Exchange Mailbox.
The 'Run As' account must have an Exchange Mailbox in order to create a MAPI Session for MasterCal to run.
NOTE: Some versions of Exchange require that you log into a mailbox at least once before it is actually created on the server.
Resolution 3: Run As account must have a MAPI profile on the local machine.
The 'Run As' account must have a default MAPI profile configured on the machine that is hosting the MasterCal.exe application. If more than one profile exists for this account one of the profiles must be set as the default MAPI profile. This profile must use the "Exchange Server" service to connect to an Exchange mailbox.
- I always receive an error in the MasterCalLog.log file: 'Failed to send Summary message to Admin.'
- OR -
After installed and run, MasterCal reports that it processed 0 mailboxes.
Resolution:
There may be a problem with the 'Run As' account specified in the program's settings.
The alias you provide for this field must be able to resolve uniquely for your organization.
For example, the alias 'Admin' never resolves uniquely. Neither will 'JimM' resolve uniquely if there is also a 'JimMiller' in your organization.
You can test if the alias resolves by typing it into the 'To:' field of an email. If it resolves it will be underlined, if not it will have a red squiggly line under it.
Whatever account you specify as the 'Run As' account, this user/account must be a member of the Local Administrative group for the machine that is running MasterCal.exe.
- I wonder why the application is looking for a file called MasterCal.log although the actual logfile name is MasterCalLog.log. Even renaming the file does not succeed. It is being renamed then in xxx.tmp and a corresponding entry in the logfile is made.
Resolution:
'MasterCal.log' and 'MasterCalLog.log' are two completely separate files.
The first file, MasterCal.log, is a transaction file that contains all of the additions/changes/deletions of Appointment items in the Exchange folder(s).
MasterCal.exe processes this file each time it runs in order to push any changes to users' mailboxes.
During processing this file is renamed to 'MasterCal.log.tmp' so that users cannot write to the file. It is possible for a new MasterCal.log file to be created at this time.
If any errors are encountered during processing, this temporary file will be renamed using the current Date/Time and have a file extension of '.bak' (ex. 20050125125136MasterCal.bak) This prevents transactions being lost.
'MasterCalLog.log' is a file generated by MasterCal.exe each time it runs to log any errors and/or details during program execution.
- When I make a change to an existing MasterCal Appointment in a Public Folder, the change is not replicated to all user's mailboxes.
Resolution:
This has been fixed in the newest version of the MasterCal Server (version 1.0.18, released September 21, 2005).
To download the newest version of MasterCal go here.
- All MasterCal Appointments that are pushed to users' folders have the Reminder Flag turned on.
Resolution:
The latest release of the MasterCal Server (version 1.0.19, released January 27, 2006) now provides an interface to toggle this option on or off.
To download the newest version of MasterCal go here.
- I am running/have upgraded to Outlook2002 SP3 or Outlook2003. The custom forms do not appear to work in Shared or Public Folders.
Resolution:
Outlook 2002 SP3 and Outlook 2003 include a setting -- turned off by default -- to allow forms in Public Folders or Shared Mailboxes to run script.
In Outlook 2003 (but not Outlook 2002 SP3), you can change the setting by choosing Tools | Options | Other | Advanced Options and checking the box for Allow script in shared folders.
You'll see that there is also an option for Allow script in public folders.
The corresponding registry values are in the HKCU\Software\Microsoft\Office\11.0\Outlook\Security key -- SharedFolderScript and PublicFolderScript, both DWORD values.
Outlook 2002 SP3 does support the registry values, but change the key from 11.0 to 10.0.
- The Messenger reports an unresolved mailbox with the following error: Could not log into mailbox for Attendee ''. (name is blank)
Resolution:
There is a problem resolving the Attendee's alias listed in the Calendar folder's Description field. Replace the alias with the Attendee's full SMTP address.
- The Messenger cannot resolve a Distribution List entered as an Attendee and reports an unresolved mailbox with the following error: Could not log into mailbox for Attendee '<DL Name>'.
Resolution:
This has been fixed in the newest version of the MasterCal Server (version 2.1.0.2, released November 27, 2007).
To download the newest version of MasterCal go here.
|