[SV_Trinity]

Every time I load Desktop Manager 4.2, I get the message:

"Desktop Manager: DesktopMgr.exe - Ordinal Not Found
The ordinal 45 could not be located in the dynamic link library MAPI32.dll."

I have no idea what this means. I click "OK" and the message goes away. Now I'm uncertain if the Desktop Manager is working properly or not.

I tried updating the handheld OS from 4.2.0.51 to 4.2.0.67 but the Desktop Manager didn't find it.

Does anyone know what the ORDINAL thing is? I'm Windows XP Pro SP2.

[moleman2k]

Originally Posted by SV_Trinity

Every time I load Desktop Manager 4.2, I get the message:

"Desktop Manager: DesktopMgr.exe - Ordinal Not Found
The ordinal 45 could not be located in the dynamic link library MAPI32.dll."

I have no idea what this means. I click "OK" and the message goes away. Now I'm uncertain if the Desktop Manager is working properly or not.

I tried updating the handheld OS from 4.2.0.51 to 4.2.0.67 but the Desktop Manager didn't find it.

Does anyone know what the ORDINAL thing is? I'm Windows XP Pro SP2.

It sounds like a issue with the mapi32.dll file. What version of outlook are you running? Maybe you could try a Detect and Repair on outlook if you have the CD for it.

Google reports this happening for many other applications, so it would lead me to believe the issue is not with Desktop Manager itself but the mapi32.dll file.

[SV_Trinity]

Originally Posted by moleman2k

It sounds like a issue with the mapi32.dll file. What version of outlook are you running? Maybe you could try a Detect and Repair on outlook if you have the CD for it.

Google reports this happening for many other applications, so it would lead me to believe the issue is not with Desktop Manager itself but the mapi32.dll file.

Thanks for your reply. I'm not even using Outlook. I'm using an older version of EUDORA. That is probably my issue.... a MAPI problem and not RIM.

[jbeek]

Originally Posted by SV_Trinity

Every time I load Desktop Manager 4.2, I get the message:

"Desktop Manager: DesktopMgr.exe - Ordinal Not Found
The ordinal 45 could not be located in the dynamic link library MAPI32.dll."

I have no idea what this means. I click "OK" and the message goes away. Now I'm uncertain if the Desktop Manager is working properly or not.

I tried updating the handheld OS from 4.2.0.51 to 4.2.0.67 but the Desktop Manager didn't find it.

Does anyone know what the ORDINAL thing is? I'm Windows XP Pro SP2.

I've started getting this too. I'm using XP Home SP2, Desktop Mgr 4.2.1.17b (or 4.2.1.8, depending on which version number in the About screen or installation program you want to believe...) and Eudora 7.1. I can click OK too to make the message go away, but then the Media Mgr part of DM doesn't work (MM window just closes when I try to transfer a file) or other times DM crashes. All of this worked fine until I upgraded DM to 4.2.1.17b...I'm going to dig up the disk that came with the Pearl and re-install the older version to see if that helps.

Edit: for what it's worth, the two version numbers might be the same...RIM refers to it as "4.2.1.8" and "4.2.1 Bundle 17", and I think I remember reading that T-Mobile got dyslexic and called it 4.2.1.17b.

[jbeek]

Originally Posted by jbeek

I've started getting this too. I'm using XP Home SP2, Desktop Mgr 4.2.1.17b (or 4.2.1.8, depending on which version number in the About screen or installation program you want to believe...) and Eudora 7.1. I can click OK too to make the message go away, but then the Media Mgr part of DM doesn't work (MM window just closes when I try to transfer a file) or other times DM crashes. All of this worked fine until I upgraded DM to 4.2.1.17b...I'm going to dig up the disk that came with the Pearl and re-install the older version to see if that helps.

Edit: for what it's worth, the two version numbers might be the same...RIM refers to it as "4.2.1.8" and "4.2.1 Bundle 17", and I think I remember reading that T-Mobile got dyslexic and called it 4.2.1.17b.

Well, I couldn't find the original disk so instead I installed the latest version (recently released 4.2 SP2) and the problem went away.