Is the Windows 7 SDK a 64 bit version of the software? If so I would think it would not be able to see the 32bit Unidk to use it. As 64bit versions of software can only interact with the 64bit versions of drivers even if the 32bit drivers are installed properly. Is there some way to make the Windows 7 sdk run as a 32bit environment? I would think that could solve your problem unless your trying to write something to run on windows 7 64bit.
Jeffrey Lettau ERP Systems Manager polkaudio -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jim.sto...@esc.edu Sent: Tuesday, June 14, 2011 5:47 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Installing UniObjects on Windows 2008 64 bit Hi, Thanks for the suggestions, folks. So far, I haven't made any progress. I did install the UniData client by right clicking on the installer and using Run As Administrator, while also logged in as an Administrator, with the same results. After David's email mentioned a missing dll and registering them manually, I tried to investigate that possibility. I'm not very familiar with that aspect of Windows systems administration, though, so I don't really know exactly what dlls are required. I looked in the "C:\IBM\UniDK\redist\i386\register" subdirectory, and made sure that all of those files were present in my C:\Windows\SysWOW64 directory (they were). And then I opened the command prompt (with Run as Administrator), and tried using the REGSVR32 command to register each of those 8 files, including uniobjects.dll. In each case, I got the message "DllRegisterServer in c:\windows\syswow64\uniobjects.dll succeeded." However, I still don't see the UnioaifCtrl class in the OLE/COM viewer that comes with the Windows 7 SDK, and I still get the error when I try to call the object in my Domino agent. The one new piece of info that I have is this: When I run (as administrator) the UniData client installer, and then choose the UniDeveloper Kit option, it installs without any visible error as I've mentioned. However, I also tried going into the installer's UNIDK subdirectory, and running (as administrator) the actual setup.exe application for the UniDeveloper Kit. When I do it this way, I do see an error message: * The following files did not self-register or unregister: * 1. C:\Windows\SysWOW64\oc30.dll Error: 0x80040200 * 2. C:\Windows\SysWOW64\oleaut32.dll Access is denied. I do not get that error message when I run the full UniData client installer, though, so I am not sure if that error is because some underlying element that is normally handled by the main installer isn't in available, or if that error is actually occurring all the time and the main installer just isn't reporting it. Since my install isn't working, I'm guessing the error happens all the time, and the main installer is interfering with the error alert. A google search on the error number hasn't helped much. If I try to set the UDK setup program to run in Windows 2003 compatibility mode, it no longer reports an error, but the object still doesn't work or show up in the object viewer. I'll keep looking, but if anyone has any more suggestions, I'd love to hear them! :-) Thanks for the help so far! Jim Stoner _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ________________________________ Disclaimer: This email may contain confidential and/or privileged information. It is intended only for the person or persons to whom it is addressed. Any unauthorized review, use, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email or telephone and destroy all copies of the original message. Please consider the environment before printing this email. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
