i tried to migrate a outlook pst to Groupwise 7 build 1294 with formativ express 2.01 and the personal outlook migration applet 2.0.3.
Unfortunately i get followin error: Access violation at address 7c92103c in module ntdll.dll Write of address 0208cacd.
I tried the import twice and i suppose the error appears at the same time (after about 1600 emails). I tried to repair the .pst with the outlook tool but the error is still there.
Now i try to import the emails only - no appointment, no other stuff...
Any further hints? =D Thanks in advance. Cheers PiTPosts:
2 | Registered: March 05, 2009
posted
Thanks for your post. Unfortunately, we haven't any report about the ntdll.dll error on the Personal Outlook Migration solution.
We have received few reports about the ntdll.dll error when user view or applet access shared folders, address books, etc. The cause of the error still unknown and appear to be GroupWise client related.
A quick Google search on "ntdll.dll" turns up several threads, it appears to faulty printer drivers, terminal server, etc.
We would suggest you to re-install the GroupWise client to latest point release. It also could be environmental, can you re-produce the behaviour to another machine or user?
Regards, Advansys SupportPosts:
821 | Registered: February 19, 2006
i tried the migration with another workstation (same GW version, runtime and applet). The migration freezed after about 200 mails -no error, just freeze. I put the directory in which the applet freezed into the outlook archive and started again. And this time everything went fine until the migration of the appointments. There i got the same error (access violation). But that doesn´t matter for me...After that I migrated the archive.pst with the directory in which i assumed the origin of the first access violation error...but the migration went fine. So thank you for this great piece of software :0) - with some workarround the migration was doable. During the next weeks i will migrate some other pst files to Groupwise...maybe I ll get the error again and I will keep reporting =D.
Next
