InfoBridge Knowledge Base

Version History DataDirector

Thomas Speekenbrink — Mon, 06 Feb 2012 15:05:52 GMT

INFO:

DataDirector 3.X

SUMMARY
Version History Information.

Version 3.0.6
* Added SuperOffice SIX.Web support for SuperOffice NetServer 3.0

Version 3.0.5
* Custom rule added for customer

Version 3.0.4
* Custom rule added for customer

Version 3.0.3
* Custom rule added for customer

Version 3.0.2
* Custom rule added for customer

Version 3.0.1
* Custom rule added for customer

Note
* No need to update when running version 3.0.0!

InfoBridge Version 3.0.0
* Release for SuperOffice CRM SIX/SIX.One

Version History Synchronizer Products

Thomas Speekenbrink — Mon, 06 Feb 2012 15:04:30 GMT

INFO:

APPLIES TO

Synchronizer Products

SUMMARY
Version History Information.

InfoBridge Version 3.0.6/SuperOffice Version 1.2.12
Resolved
* (2147217885) Row handle referred to a deleted row or a row marked for deletion.
* Illegal data like email addresses in the phone number field in SuperOffice are now accepted when synchronizing

InfoBridge Version 3.0.5/SuperOffice Version 1.2.11

Resolved
* UpdateToSuperOffice: 5 Invalid procedure call or argument.
* Duplication of the subject text within an Outlook appointment.

Note on building the subject and location field:
When the following options are set in the SynchronizerAdmin, in the panel ‘SuperOffice SIX Settings’
External Subject Line: <250 characters of App. Or Task Text>
You have the following behavior
Situation 1:
- When the appointment is originally created in SuperOffice, only the first 250 characters of the appointment text will be placed in the subject field in Outlook. The complete appointment text will be placed in the body field of the Outlook appointment.
- When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be overwritten by the Synchronizer with the first 250 characters of the appointment text.
Situation 2:
- When the appointment is originally created in Outlook, the Synchronizer will respect the subject and or location field of Outlook in the SuperOffice appointment text.
- When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be not overwritten by the Synchronizer with the first 250 characters of the appointment text.

When the following options are set in the SynchronizerAdmin, in the panel ‘SuperOffice SIX Settings’
External Subject Line: <Task Type><First line of App. or Task>
You have the following behavior
Situation 1:
* When the appointment is originally created in SuperOffice, only the first line of the appointment text will be placed in the subject field in Outlook. First line is recognized by the first carriage return found. The complete appointment text will be placed in the body field of the Outlook appointment.
* When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be overwritten by the Synchronizer with the first line of the appointment text.
Situation 2:
* When the appointment is originally created in Outlook, the Synchronizer will respect the subject and or location field of Outlook in the SuperOffice appointment text.
* When this appointment is changed in Outlook, meaning a new subject line and or location is filled in, this will be not overwritten by the Synchronizer with the first line of the appointment text.

Remark: You can easily determine where the appointment is created by looking at the SuperOffice appointment text, if the appointments text has the fields: Subject: Location: and -------------, this means the appointment was originally created in Outlook.

InfoBridge Version 3.0.4/SuperOffice Version 1.2.10

Resolved
* When the date separator character contained an invalid character creating of the user statistics file would fail.
* When the Outlook body of an appointment is larger then 2000 characters, the Synchronizer will not update the body text (in Outlook) from SuperOffice to Outlook.

Synchronizer
* Vista Compatible
* When the SuperOffice appointment has no related company, the Outlook subject will hold the SuperOffice task type.
* Colors which are set in Outlook 2007, will be maintained, even when the color scheme in SuperOffice is not used.
* Phone Numbers are also synchronized to the body of the Outlook appointment, which will give quick dial access from mobile phones

SynchronizerAdmin
* Option added to reset the users, so that the synchronization will perform a fresh start, missing appointments will be added if necessary. It will not create duplicates!
* Purify phone number option added, so that the phone which is been synchronized to the appointment/task text, does not contain any invalid characters
* New option added for building Outlook appointments, <task type>: <First line of the appointment text> First line is determined by the first carriage return found.
* Notifier option to get instantly notified by mail of changes in the diary
* Option added to NOT synchronizer the alarm set in SuperOffice to Outlook
* Option added to NOT synchronizer the alarm set in Outlook to SuperOffice
* From now on, the SynchronizerAdmin is always in English.
* Option added to select all activity types, instead of selecting the activities one by one

Note
* Time Zone support from SuperOffice is not supported in Outlook 2007, however the Time Zone support of Outlook 2007 is supported in SuperOffice, this is due the incompatibility between the Time Zone setup of SuperOffice and the Microsoft platform.

InfoBridge Version 3.0.3/SuperOffice Version 1.2.9
* Internal Changes

InfoBridge Version 3.0.2/SuperOffice Version 1.2.8
* Internal Changes

InfoBridge Version 3.0.1/SuperOffice Version 1.2.7
* Keycode handling for both versions added

InfoBridge Version 3.0.0/SuperOffice Version 1.2.6

Synchronizer
* In some cases Runtime Error 6 Overflow occured and the sync would not continue with adding appointments, this issue was caused when the group_idx of an appointment record would not fit in a integer variable.
* Synchronizer.exe now checks at startup of redemption.dll is available, when redemption.dll is missing, linking of users would work in SynchronizerAdmin,
but when the Synchronizer would access the folders, the message appeared Problem getting folder xx
* userid and password are not converted anymore to uppercase, this could cause problems on SQL server 2005
* Synchronizing resources will work now

SynchronizerAdmin
* When linking a resource as a syncuser, an error would occur.
* It is possible now to link resources as a syncusers
* The list of resources also contained deleted resources
* Linking of a mailbox name with a ' in the name would fail
* userid and password are not converted anymore to uppercase, this could cause problems on SQL server 2005
* Better description for US and Dutch language for the options Enable simple logand Enable debug
* The option DELETESYNCTABLES is now also removing the userpreference settings of the synchronizer
* The option DELETESYNCTABLES will continue deleting tables even when the first table is already deleted

InfoBridge Version 3.0.0/SuperOffice Version 1.2.5

Synchronizer
* Encryptedcheck field is now filled with a ' ' blanc character, this bug caused the following behaviour:
- Appointment would be added to SuperOffice
- Insert in the visiblefor table would fail because blanc character was not allowed
- Because of this error the record was not added in the Synchronizer History table
- In next run the same appointment is not found in the Synchronizer history table, so the record would be added again to SuperOffice

SynchronizerAdmin
* There is an issue with the SDKDictonary on Oracle, when there is not enough space (SYSTEM) or rights, the first table (syncuser) will be created in the Oracle database, however the
remaining tables will not be created.
Extra checked is build in, to see if also the last table exists (synctemp) in the SuperOffice database, if this is not the case the user will get the following errormessage:
"Not all Synchronizer tables are found, some tables are missing. Please start the SynchronizerAdmin with the parameter DELETESYNCTABLES and try to create the tables again. Make sure the user has sufficient rights in 'Oracle' to create tables!"

This would cause the following issue;
- It seams everything is working, the synchronizeradmin works completely, however the Synchronizer will not find the remaining tables and will display an error.

InfoBridge Version 3.0.0/SuperOffice Version 1.2.4

Synchronizer
* When linking a user in SynchronizerAdmin on Oracle 10g, the emailaddress which should be empty will containt one space, this would mean
the emailaddress is not empty, so the synchronizer will try to resolve the exchange user based on the blank emailaddress instead of the unique
exchange id. This would cause the following problem;
- Link the user in SynchronizerAdmin
- Start the synchronizer, message would appear: can not resolve user

SynchronizerAdmin
* No Change, just version number update to keep versions in sync

InfoBridge Version 3.0.0/SuperOffice Version 1.2.3

Synchronizer
* Bug fixed when the Outlook Subject or location would exceed 250 characters, this bug caused the following problem;
- Appointment would be added to SuperOffice
- Appointment could not be stored in the Synchronizer History table
- In next run the same appointment is not found in the Synchronizer history table, so the record would be added again to SuperOffice
- Again this new added appointment could not be added to the Synchronizer History table
- This would happen each time when the synchronizer would run.
- The end result is that many duplicate appointments would be created on the same day

* In the Outlook mode (personal edition) the settings made in the SynchronizerAdmin where not read on startup of the Synchronizer,
this bug caused the following behaviour:
- Setting made for example start minimized, and sync every minute
- The synchronizer would start, but the user had to press the start button, because there settings for the user where not read at startup

SynchronizerAdmin
-----------------
* No Change, just version number update to keep versions in sync

InfoBridge Version 3.0.0/SuperOffice Version 1.2.2

Synchronizer
* Added support for handling internal sybase travel, in case when a internal sybase travel database gets detected it uses the following
connectionstring:
dDatabase.ConnectionString = "Driver=SuperOfficeTravel;Start=" & SODB.Settings.ProgPath + "\Database\dbeng9.exe -q -c 8m;Integrated=No;DatabaseFile=" & SODB.Settings.LocalArchivePath + "\Data\SuperOfficeTravel.db;UID=" & sUserID & ";PWD=" & sPassWord

SynchronizerAdmin
* When running the SynchronizerAdmin in the Exchange mode (/E) the option Restart every # minute could not be checked,
a message would popup telling the watchowl should be enabled, even if the watchowl was enabled

InfoBridge Version 3.0.0/SuperOffice Version 1.2.1

Synchronizer
* Release

SynchronizerAdmin
* Release

Version History NewsDirector

Thomas Speekenbrink — Mon, 06 Feb 2012 15:03:41 GMT

INFO:

APPLIES TO

NewsDirector

SUMMARY
Version History Information.

NewsDirector Version 3.0.1_6
Resolved
* Fixed the issue that on some systems it is impossible to get a focus and start typing in the editor.
* Changed the editor to remove Doctype Definition from all loaded HTML because of the above issue and to improve stability of the editor.

NewsDirector Version 3.0.0_6
* Initial BETA release of NewsDirector.

Version History Exchange Synchronizer for Visma Business

Thomas Speekenbrink — Mon, 06 Feb 2012 15:03:01 GMT

INFO:

APPLIES TO

Visma Business Synchronizer

SUMMARY
VersionHistory Information.

Version 1.2.10

Resolved

* Fix for possible out of sync situation when moving an, in Visma,deleted appointment in Outlook

* Fixed an issue where updates of addresses for Visma Business contactswere not synced instantly to Outlook

Version History Exchange Synchronizer for Visma CRM

Thomas Speekenbrink — Mon, 06 Feb 2012 15:02:18 GMT

Version History Information Exchange Synchronizer for Visma CRM

Synchronizer Version 1.7.9
* Fixed a possible cancellation caused by specific Exchange environments

Synchronizer Version 1.7.8
* Internal Optimization

Synchronizer Version 1.7.7
* New and improved Configurator

Synchronizer Version 1.7.5 - 1.7.6
* Internal Optimization

Synchronizer Version 1.7.4.1
* Additional fix for synchronization of phones notes

Synchronizer Version 1.7.4

Resolved

* Updated MAPICDO version in prerequisites. This new version resolves issues with hanging appointments, caused by the Exchange MAPI

* Fixed an issue with large appointments from Visma CRM

* Fixed an issue with telephone notes that was introduced in version 1.5.9

* Solved a rare issue that could cause synchronization to stop due to an special appointment in Visma CRM

* Fixed a possible cause of cancellations when deleting the ICS folder and journal.db3

* Fixed several possible causes of cancellations

* Fixed an issue with Outlook appointments that contain a quote in the body text

* Fixed an issue that could cause events not to be picked up when rescheduling a meeting in Visma CRM

New

* Added support for 190+ simultaneous users

* Added option to disable housekeeping at startup

Synchronizer Version 1.6.0 - 1.7.2

* Internal Optimization

Synchronizer Version 1.5.9

Resolved

* Fixed anissue with invites from externals, where externals were not added as attendeesin Visma CRM

* Addedprerequisites folder in installation directory

* Addedadditional handling for large appointments coming from Outlook

* Enabledsynchronization of all types of Visma appointments. This solves various issuesrelated to types.

* A newsetup is used from 1.5.9. To upgrade, a deinstall is required first.

Version History Synchronizer V2 Products

Thomas Speekenbrink — Mon, 06 Feb 2012 15:01:30 GMT

INFO:

APPLIES TO

Synchronizer Products

SUMMARY
VersionHistory Information.

InfoBridge/SuperOffice Version 3.2.65
Resolved
* Using an Oracle database could give you a casting issue.

InfoBridge/SuperOffice Version 3.2.64
Resolved
* Using Oracle with older versions of the synchronizer could give errors when saving settings in the Synchronizer admin

* Moving a recurring Outlook appointment in the Outlook calendar could lead up to a missing appointment in SO

InfoBridge/SuperOffice Version 3.2.59 - 3.2.63
Resolved
* Internal Optimization
Note: This version was not released as downloadable version
InfoBridge/SuperOffice Version 3.2.58
Resolved
* The Gui starts but the Service does not. This can happen when you are using Exchange 2010 and Outlook 2003. It's a complex problem and it is due to Outlook 2003 MAPI and Legacy DN's to resolve Exchange servers and the Sync users there mailboxes.

We have solved the problem in this new 3.2.58 version. You do need to place an extra file in the Synchronizer folder; 'mapi.opt'. It's attached to this document.

NOTE: The Mapi.opt file only works from version 3.2.58 and only when you are using Exchange 2010 and Outlook 2003.

InfoBridge/SuperOffice Version 3.2.57

Resolved

* The Service failed during start. This was due to the object server for the COM-object not being correctly initialized.

InfoBridge/SuperOffice Version 3.2.56
Resolved
* Updating phonenumbers in some occasions went wrong. Due to a combination filter giving an early return when there was no phonenumber available for a contact.

InfoBridge/SuperOffice Version 3.2.49 - 3.2.55
Resolved
* Internal Optimization
Note: This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.50
Resolved
* Matching recurring instances between SuperOffice and Outlook with all-day events.

InfoBridge/SuperOffice Version 3.2.49
Resolved
* Internal Optimization
Note: This version was not released as downloadableversion

InfoBridge/SuperOffice Version 3.2.48
Resolved
* In this version persistent locking is activated.This means that files like journal.db3.jrnl cannot get locked if otherprocesses on the machine are in use.

InfoBridge/SuperOffice Version 3.2.47
Resolved
* Appointments with recurrency patterns which the Synchronizer cannotparse will be skipped.
Note: Extra information will be logged in the logfile

InfoBridge/SuperOffice Version 3.2.46
Resolved
* Extra parameter option to turn off Unicode support. Use the parameter/DISABLEUNICODE in the GUI start command line to turn off Unicodesupport. For the Service you have to add disableUnicode=1 just below [Server].
Note: Please consult InfoBridge support for advice before using this option

InfoBridge/SuperOffice Version 3.2.45
Resolved
* When changing ownership of a Superoffice appointment or task to anon-Synchronizer user the appointment or task was deleted from the SO database.This was due to delete notifications from Exchange which were not canceled andtherefore the appointment or task was deleted from SO

InfoBridge/SuperOffice Version 3.2.44
Resolved
* Selection synchronization in SO Six could give you the following error:'Invalid column name 'targetTableNumber'. This is now resolved.

InfoBridge/SuperOffice Version 3.2.43
Resolved
* The SO address lines 2 and 3 are now also synchronized to the addressline in the synchronized appointment and task body text in Outlook

InfoBridge/SuperOffice Version 3.2.42
Resolved
* Problems with the synchronization of the SuperOffice 7 location fieldtowards Outlook are now solved

InfoBridge/SuperOffice Version 3.2.41
*Internal Optimization
Note: This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.40
Resolved
*The Synchronizer is now compatible forSuperOffice Six and Seven

InfoBridge/SuperOffice Version 3.2.27 - 3.2.39
* Internal Optimization
Note: This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.26
Resolved
* Appointments created in SuperOffice were notsynchronized from Exchange 2010 into some mobile devices. This was due to anone required property.

InfoBridge/SuperOffice Version 3.2.25
*Internal Optimization
Note:This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.24
Resolved
* The Synchronizer could crash while processing themapping between SuperOffice and Exchange id's
* Some recurrent appointments from Outlook presented the Synchronizer with aunknown first day of the week value of -1

InfoBridge/SuperOffice Version 3.2.23
* Internal Optimization
Note: This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.22
Resolved
* ICS Synchronization would fail in some cases
* Company and contact addresses are now synchronized correct into Outlook
* Synchronization of tasks which were changed from the SO Checklist into the SODiary would sometimes fail
* Opening the 'User Synchronization Settings' in the Synchronizer Admin couldgive you an "Unhandled Exception" error when you use Windows 7
* In Windows server 2008 the creation of the Synchronizer tables could failwhen the Mutex was not correctly closed
* When there were empty fields in the Synchronizer tables the synchronizercould present you with MessageID errors (mainly on Oracle databases)

InfoBridge/SuperOffice Version 3.2.20 - 3.2.21
* Internal Optimization
Note:This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.19
Resolved
* Automatic Linking would fail in some cases
* Synchronization of middle name
* Postal address synchronization
* High CPU load
* Retired associates are no longer synchronized
* Outlook color indication would be overwritten by the synchronizer
* Problems with selecting a synchronized contactperson by using the To buttonin Outlook
* Completed all-day event is uncompleted after synchronization
* Executable file information in Windows explorer displays old version
* Filtering of activity types on Oracle fails in certain situations
New
* Participant information from a SuperOffice group appointment isSynchronized to Outlook
* Support of using template variables to build Outlook subject line
* Possibility to move time consuming tasks to a different time
* Complete redesign of Synchronizer admin (maximize, sorting, filtering)
* Speed improvement
* Option to disable/enable synchronization of private appointments
* Option to link blank appointment to fixed SuperOffice company
* New Key code handling inside Synchronizer Admin
* Full support for Microsoft SQL 2008
* Full support for Microsoft Exchange 2010

InfoBridge/SuperOffice Version 3.2.10 - 3.2.18
* Internal Optimization
Note:This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.9
Resolved
* Meeting reply/response requests where not alwayspossible in Outlook if the appointment originated from SuperOffice
* .NET Framework 64 bit is supported
New
* The logging is now configurable in the Synchronizer Admin or can be changedwhile the Synchronizer is running, see installation manual for more information

InfoBridge/SuperOffice Version 3.2.8
Resolved
* Some Russian UNICODE characters where not correctly synchronized
* In certain rare cases the edit of a private appointment in Outlook was notreflected towards SuperOffice
* In a hosted Exchange environment the message 'Invalid cast from'System.String' to 'InfoBridge.Connector.IMessageId); would sometimes appear
* Synchronizer Admin: The limit of 400 days in the future has been removed
* Synchronizer Admin: Loading the GAL will always display a loading dialog
* Multi-language support added for task types

InfoBridge/SuperOffice Version 3.2.7
* Internal Optimization
Note:This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.6
Resolved
* In rare cases a dead-lock on the SQL server occured when SuperOfficedatabase was stressed
Note:This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.5
* Internal Optimization
Note:This version was not released as downloadable version

InfoBridge/SuperOffice Version 3.2.4
Resolved
* Correct window name in Taskbar is displayed of the activation screen
* When Exchange/Outlook users have multiple calendars, the Synchronizer willonly handle the default calendar of the user and will not listen to events ofthe other calendar.

InfoBridge/SuperOffice Version 3.2.3
New
* SuperOffice License system implemented

InfoBridge/SuperOffice Version 3.2.2
Resolved
* Version number on EXE and DLL files

InfoBridge/SuperOffice Version 3.2.1
* Initial Release

Version History Mail Logger for Visma Business

Thomas Speekenbrink — Mon, 06 Feb 2012 15:01:08 GMT

SUMMARY
Version Information

Add-In version 1.4.0 / Service version 1.4.0

Resolved
* Add-In GUI will always represent correct 'Link'-items and Associates

New
* Support for Visma Business 5.31
* Service will recover from Visma Business Service Host restart
* New Configurator:
- License test option
- License release option
- License import option
- Add multiple firms to log to
- Test connection settings to Visma Business
- Option to set logging level
- Option to select 3 'Organizational Units' for Add-In
* New Add-In interface
* Add-In can log to multiple firms
* Outlook 2010 64-bit now supported

Add-In version 1.3.0 / Service version 1.3.0

Resolved

* Logging sent items will now always take the correct associate, if found.

New

* Added support for loading large lists.

* Associate and contact now always show the associates that will be send to Visma Business.

* Removed property panel from Outlook settings.

- For Outlook 2003 - 2007 a new menu item in 'Tools' is added.

- For Outlook 2010, a ribbon button is added

* Settings in Add-In are more user-friendly now. Only the server name is required to make a connection.

* New setup for the service. To upgrade, a deinstall of the old service is required first.

Version 1.2.12

* First public release

Hanging appointments

Thomas Speekenbrink — Mon, 06 Feb 2012 12:48:29 GMT

When you experience that appointment are not getting through, please check the local folder where you will find the logfiles.
When you see that the application has started to create dmp files in this local folder please perform the following steps:

- Check your Synchronizer version. Please make sure it's the latest version. You can find the latest version on http://www.vismaplaza.com/
- Update the MapiCDO files. http://www.microsoft.com/download/en/details.aspx?id=1004 (NOTE: please remove your current MapiCDO components (through add/remove programs))

How to Prepare the Exchange Server for RPC over HTTPS

Thomas Speekenbrink — Mon, 06 Feb 2012 12:24:26 GMT

This simple tutorial explains in general what needs to be done in order to prepare the Exchange server for use of RPC over HTTP.

This functionality enables clients to access the Exchange server through Outlook from anywhere in the world, as long as an internet connection exists.

RPC over HTTPS is also useful when implementing Infobridge Synchronizer for Exchange in a different domain than where the Exchange server exists, and this is the motivation for this tutorial.
This procedure is not required on SBS as SBS fully configures Exchange for RPC over HTTPS and also provides instructions to connect an Outlook client on the 'Configure Outlook over the internet' link on RWW https://sbs/remoteConsiderations

Please see the attached document "How To - Prepare the Exchange Server for RPC over HTTPS"

Installing the Synchronizer in a multiple domain environment

Thomas Speekenbrink — Mon, 06 Feb 2012 12:14:08 GMT

FAQ: Installing the Synchronizer in a multiple domain environment

APPLIES TO

Exchange synchronizer V2

Description: The Synchronizer Service needs to be installed in a multiple domain environment, for example; Domain_A holds the SuperOffice Database, Domain_B holds the Microsoft Exchange Server. For the best performance the Synchronizer will be installed at Domain_A.

Please see also the attached document How To - Prepare the Exchange server for RPC over HTTPS

When a MAPI profile is created on Domain_A towards the Exchange server on Domain_B a logon box is presented.

Cause: The user who is logging on from Domain_A is not known (trusted) in Domain_B, therefore a logon box will be always presented. Because a logon is forced by Microsoft the service of the Synchronizer will not run!

Solution: Create a trust between the two domains. This will prevent the logon box because the user of Domain_A is trusted at Domain_B.

Login to Domain_A using a Domain Administrator account.
Click Start - Administrative Tools - Active Directory Domains and Trusts.
Right-click on Domain_A, and select Properties. Go to the "Trusts" tab. Click the [New Trust...] - [Next].
Type "Domain_B" in the Name field to indicate the domain to trust, and click [Next].
Select "Two-way" for the Direction of the Trust. Click [Next].
In "Sides of the Trust", select the "This domain only" bullet. Click [Next].
Set the Authentication level to "Domain-wide Authentication". Click [Next].
Enter a Trust Password twice. Remember to make it complex enough to comply with any strong password criteria you may require in your domain security policy.
Click [Next] - [Next] - [Next].
Select the "No" bullet to the Outgoing Trust Confirmation - [Next].
Select the "No" bullet to the Incoming Trust Confirmation - [Next].
Click [Finish] - [OK].
Log off of Domain_A.
Login to Domain_B using a Domain Administrator account.
Click Start - Administrative Tools - Active Directory Domains and Trusts.
Right-click on Domain_A, and select Properties. Go to the "Trusts" tab. Click the [New Trust...] - [Next].
Type "Domain_A" in the Name field to indicate the domain to trust, and click [Next].
Select "Two-way" for the Direction of the Trust. Click [Next].
In "Sides of the Trust", select the "This domain only" bullet. Click [Next].
Set the Authentication level to "Domain-wide Authentication". Click [Next].
Enter a Trust Password twice. Remember to use the exact same Trust Password that you used previously in Step #8.
Click [Next] - [Next] - [Next].
Select the "Yes" bullet to the Outgoing Trust Confirmation - [Next].
Select the "Yes" bullet to the Incoming Trust confirmation - [Next].
Click [Finish] - [OK].
Log off of Domain_B.

InfoBridge Synchronizer is not registered

Thomas Speekenbrink — Mon, 06 Feb 2012 11:03:58 GMT

Ever started the Outlook Synchronizer and received the message "InfoBridge Synchronizer is not registered"? And the Synchronizer has been registered months before:

Most likely you started the Synchronizer from the Outlook Synchronizer folder.
When you start the Outlook synchronizer from the Start menu there should be no registration problem.

Another possible sollution is to check the properties of your shortcut
In the Start Command line you should see a /P parameter; if not please add this to your start command line
e.g. "C:\Program Files (x86)\InfoBridge\Outlook Synchronizer\InfoBridge Synchronizer.exe" /P

Synchronizer upgrade from CRM5 to SO 7

Thomas Speekenbrink — Mon, 06 Feb 2012 10:26:36 GMT

Synchronizer upgrade from CRM5 to SO 7

Step 1

The 1st step is to install SuperOffice SIX
Next you need to install the Synchronizer for SO SIX. This is version 3.0.6 is enclosed in this knowledge base article.
After the installation of the Synchronizer is completed, the Synchronizer admin needs to be started. This will create the new Synchronizer tables in the SO Six database.
Note: You can automatically generate a trial keycode during the start of the Synchronizer admin

We now need to transfer all data from the old Synchronizer tables (in the CRM5 database) into the new Synchronizer tables in the SO SIX database.
This can be done with the conversion tool “OutlookSync2Synchronizer.zip”, see attached.
Please follow the conversion procedure explained in the document “SO Outlook Sync 2 Synchronizer.pdf”

When the conversion is done you can start the Synchronizer admin. Make sure all settings are correct.
Next run the Synchronizer.
If it is Synchronizing like a charm that’s the end of the 1st step.

Step 2

You are now ready to upgrade the Synchronizer 3.0.6 (v1) to 3.2.xx (v2)
Please visit our website for the latest version http://www.crmplaza.com

On the website you will also find the installation manual in which all the upgrade steps are described in detail.
To give you a hint of what’s coming:
• Install the Cleaner tool in the exchange synchronizer folder
• Start the Cleaner tool and clean all Outlook Calendars (This will remove all calendar entries in the date range specified in the Synchronizer admin)
• Use the Cleaner tool to drop the old synchronizer tables
• Install the new version 3.2.xx
• Start the Synchronizer admin to create the new Synchronizer tables
• Use the settings.txt (created by the Cleaner tool) to replace all the settings in the Synchronizer admin
• Start the Synchronizer to synchronize all appointments back into Outlook and get the calendars back in sync.

NOTE: The latest version of the Synchronizer on our website is compatible with SuperOffice 7 but it is absolutely mandatory to perform this 2nd step on a SuperOffice SIX database. This is because the Cleaner tool can only run on SuperOffice SIX.

Step 3

Now you are ready to upgrade SuperOffice to SO 7.
When this is completed please follow these steps to get the Synchronizer ready for SO 7:
• Convert the license key by using the License Key Manager
• Reset the SyncUsers table with the “SyncToSeven.zip” tool, also attached
• Change the Synchronizer Admin - Service Options
All these steps are described in more detail in the attached “Upgrade Manual Synchronizer for superOffice 7.pdf”

Unable to initialize COM object server

Thomas Speekenbrink — Thu, 02 Feb 2012 16:26:42 GMT

When you see this message when starting the synchronizer you most likely have .NET Framework version 2.0

Solution: Install .NET Framework 3.5

unable to create synchronizer agents

Torben Henriksen — Mon, 23 Jan 2012 13:59:35 GMT

When starting the Synchronizer you can get the following error : Unable to create Synchronizer agents.

- The problem could be that the rights on the InfoBridge folder are not set correctly. Check to see if you can create a new file.
To sovle this, adjust the rights on the InfoBidge folder.

- It could also be that the UAC (User Account Control) is on (Vista). Please turn this UAC off and reboot your pc.

- Give the user full rights on the Infobridge folder

- It could also be that you are not logged in as the user which has been set up to be the synchronizer user

- If you are trying to open the GUI, please check if the service is running.

Unable to connect to Lotus Notes server!

Torben Henriksen — Thu, 19 Jan 2012 10:19:25 GMT

When performing a Test in the Domino Synchronizer administration under "Technical Settings", and you get the error message "Unable to connect to Lotus Notes Server"

It can be that the port specified in step 11 of "Domino Server configuration settings" in the installation manual for the Domino server, is being used by another application.

Please make sure that this is not the case.

If settings permit, also see if you can ping the server to ensure that there is a connection between the two.

Unable to edit the MAPI profile

Torben Henriksen — Tue, 17 Jan 2012 17:10:18 GMT

When logged in as the synch user and you still are not able to edit the MAPI profile, there is a good chance that the MAPI file has been corrupted.

Please do the steps below to fix the file.

Do these steps first

Close Synchronizer admin and Outlook.
Locate a utility program on your computer called FIXMAPI.EXE. The easiest way to find it is to search for it with Windows Find. When found, double-click it to run it. It will probably run quickly and may not produce any visible results.
Restart your computer.
Start Synchronizer admin to see if your problem is resolved.

Do these steps only if the above steps do not fix your problem

Close Outlook.
Rename each occurrence of MAPI32.DLL on your system to MAPI32.OLD. The easiest way to find it is to search for it with Windows Find.
Reinstall Microsoft Outlook using the repair and replace missing or corrupt files option. This will install the correct MAPI32.DLL.
Restart your computer.
Start Synchronizer admin

Strange Phone number or place in your Synchronized appointment

Thomas Speekenbrink — Fri, 13 Jan 2012 11:53:26 GMT

Ever seen a synchronized appointment in Outlook with a strange phone number or place just below your text?

This could happen when you have made an appointment in SuperOffice without a company and contact.
Why?
The synchronizer looks for a record where the owner_id = 0
In your SuperOffice database these records could be found in the Phone and/or Address table

How to solve it:
Open the Phone- and/or the Address table and look for records where the owner_id = 0
Remove these records

Updating Outlook Synchronizer in Terminal Server environment

Torben Henriksen — Wed, 04 Jan 2012 16:35:50 GMT

When updating each user's folder on the terminal server, it is important that the file "journal.db3" and all the files in the ICS folder are not been overwritten.

HTML Parsing and Rendering in Outlook 2007

Torben Henriksen — Mon, 02 Jan 2012 12:11:41 GMT

HTML Parsing and Rendering in Outlook 2007.

Microsoft Office Outlook 2007 uses the HTML parsing and rendering engine from Microsoft Office Word 2007 to display HTML message bodies. The same HTML and cascading style sheets (CSS) support available in Word 2007 is available in Outlook 2007.

This article provides reference documentation related to supported and unsupported HTML elements, attributes, and cascading style sheets properties.

http://msdn.microsoft.com/en-us/library/aa338201.aspx

SuperOffice SIX not responding with DataDirector rules

Torben Henriksen — Mon, 02 Jan 2012 11:53:16 GMT

SuperOffice SIX is not responding after making rules in DataDirector.

During installation the button 'Copy from DataDirector Admin' was not clicked during installation ( DataDirector Installation Manual )

Solution

Open the 'DataDirector Configurator' from the Start menu, and click the button 'Copy from DataDirector Admin'

The Service fails but the Gui runs fine, part2

Torben Henriksen — Thu, 15 Dec 2011 14:42:39 GMT

The Gui starts but the Service does not.

This can happen when you are using Exchange 2010 and Outlook 2003. It's a complex problem and it is due to Outlook 2003 MAPI and Legacy DN's to resolve Exchange servers and the Sync users there mailboxes.

We have solved the problem from version 3.2.58. You do need to place an extra file in the Synchronizer folder; 'mapi.opt'. It's attached to this document.

NOTE: The Mapi.opt file only works from version 3.2.58 and only when you are using Exchange 2010 and Outlook 2003.

Upgrading the Synchronizer for SuperOffice 7

Thomas Speekenbrink — Thu, 01 Dec 2011 17:49:15 GMT

Scenario 1

You use the v1 synchronizer. This can be version 1.2.xx or 3.0.xx

What to do:

Upgrade the Synchronizer before you upgrade Superoffice to 7, please use the installation manual provided with the setup for detailed instructions

Why is this? The 'old' Synchronizer does not run in a SuperOffice 7 environment. The cleaning tool which you need in the upgrade proces runs on the old Synchronizer software and therefore you need to perform the upgrade in the SuperOffice Six environment.

Scenario 2

You use the v2 Synchronizer. The version is 3.2.xx

What to do:

Make sure you have the latest version. Upgrades can be downloaded from our website http://www.crmplaza.com/

Please follow the upgrade manual attached when upgrading to Seven

Domino SSL issue

Thomas Speekenbrink — Tue, 29 Nov 2011 14:26:38 GMT

We officially do not support SSL, therefore it has to be disabled on the Domino server running the sync.

There are several options, depending on what is acceptable and possible:

1. Remove SSL entirely.

a. To do this, open up the server document;

b. Go to ports->Internet ports tab;

c. Make sure that SSL port status is set to disabled;

d. Save and close the Server document;

e. Restart the HTTP task at the server console.

2. Configure SSL so it’s bypassed when accessing the server with a specific DNS name:

a. If both the Domino server and the SuperOffice connector are running on the same server we can accomplish this by using ‘localhost’:

i. Create a new internet site documentin the domino directory for ‘localhost’ set to be available on the sync-Domino server.;

ii. Leave the option to redirect tcp traffic to ssl on this site document disabled. This way non ssl traffic can only be used if the hostname ‘localhost’ is used to connect to the server;

iii. Set the homepage to the default domino homepage so even if an external user manages to put an entry in their hosts file pointing to ‘localhost’ at the external IP address they will not be asked to login over a non encrypted connection;

iv. Restart the HTTP task at the server console.

b. Create a new non-existing DNS name, to be specifically used by this sync connector:

i. Add a CNAME entry in your DNS server for example server.exampledomain.local to point at the correct Windows server (running the sync-Domino server);

ii. Do the steps described in ‘point a’, replace localhost byexampleserver.exampledomain.local;

iii. Configure the exampleserver.exampledomain.local to be usedby the SuperOffice connector.

Exchange Cache Mode

Thomas Speekenbrink — Fri, 25 Nov 2011 12:14:51 GMT

The Synchronizer communicates between SuperOffice and Exchange through the Mapi Profile you set in the Technical settings.

Please make sure that the Exchange Cache Mode is off.

Stop/Start Batch for Synchronizer service

Thomas Speekenbrink — Thu, 24 Nov 2011 12:49:09 GMT

In some situations we've seen that the Synchronizer service looks to be started but in fact there is no synchronization.
Most of the time the server was rebooted during the night and the service was started but not running. Could be that it started before the sql server was fully up and running for instance.

There is an easy trick to make sure the synchronizer is started each morning.

Just create 2 batch files and schedulle these to run each morning.
Create a batch call 'StopSynchronizerService' and schedulle this to run at 05:00
Create a 2nd batch 'StartSynchronizerService' which you can schedulle at 05:30

The command you can use is a simple NET STOP/START

You can find the files attached. Make sure to rename to *.bat