Hi,

I am having problems when using your product to update an Exchange Contacts Public Folder from an SQL Server database. The folder contains approx. 2000 contacts of custom form type and I managed to use your product to populate the folder in the first instance. On trying to run the 'Load All' functionality the program initialises and starts updating the contact items fine then stops after a few seconds giving an 'Unspecified Error' as its reason for failure. The code associated with this error is inconsistent and I have seen 0xDAA04005, 0xEB404005 and 0x8A904005. It seems to be that the error occurs after the same amount of time (and a similar number of records) each attempt and the load process stops rather than just moving past the error. I hope this problem is solvable as it throws a spanner into the works of my whoe project if not...

Cheers,
Dan Allason

Hi,

what is your Outlook and Exchange version? Do you have admin permission on the folder?

I am running Outlook 2003 and Exchange 2003 and the Genius Connect is running on the Administrator profile (which has owner permissions on the folder in question). Definitely a strange problem this.

I mean real version, latest Outlook 2003 version is:
11.8118.8107 (SP2), (sometimes these problems can be Outlook version related.)

Sorry - the real version number is Outlook 2003 11.6568.6568 SP2.

Can you update to latest version?

is your custom form read only (does not allow new custom fields)? Can you test the same config without custom form?

Are in using Outlook in "Cached Exchange Mode"?
http://support.geniusconnect.com/Posts/t238- 

The same config works fine without the custom form and I have updated to the latest version. I disabled the Cached Exchange and still the program won't update. Interestingly the update seems to always stop at record 246 - could this be a memory issue? I thought that may be solved by diabling the cache but it wasn't...

Ok,

so it is custom-form related, do you have custom-scripts?

Please see topic:
http://support.geniusconnect.com/Posts/t62- 

Thanks very much! I obviously must have been an issue with the script behind the form - setting a new registry key worked wonders!

Dan