Re: [U2] Installing UniObjects on Windows 2008 64 bit
Hello, A few weeks ago I posted about the trouble we've been having getting UniObjects to work as a COM/OLE object inside 64-bit Lotus Domino. We've been looking at ways to use the .Net version of UniObjects inside Domino instead, and we found the following web page that talks about how to access a .Net class from LotusScript: https://www-304.ibm.com/support/docview.wss?rs=899uid=swg21230705 Following the directions on that page, we've run GACUTIL and REGASM to register the objects in the uodotnet.dll and make them accessible via the COM interface, with partial success. When we use the Object Viewer, under the Object Classes / Grouped by Component Category / .Net Category, we find the following two classes: IBMU2.UODOTNET.SupportClass and IBMU2.UODOTNET.UniRecord. There are also entries for a bunch of exceptions: IBMU2.UODOTNET.UniCommandException, UniDataSetException, UniDynArrayException, UniFileException, etc. There are 14 of those exception entries in total. The rest of the classes, like UniObjects, UniSession, etc. are not listed in the object viewer (though some like UniCommand, UniDynArray and UniFile do have their exceptions listed). In LotusScript, we can then use the following code to successfully access the two exposed UniObjects classes: set obj = CreateObject(IBMU2.UODOTNET.SupportClass) set obj2 = CreateObject(IBMU2.UODOTNET.UniRecord) Both of those statements work. However, by themselves, those classes aren't much use. We cannot create COM objects for the core UniObjects, UniSessions, UniFile, etc. classes. They just give the generic cannot create automation object error messages. Does anyone know why the remainder of the UniObjects classes would not be accessible via the COM interface after using GACUTIL and REGASM? Is there something about the remaining UniObject classes that make them somehow incompatible with this approach for exposing .Net dlls as COM objects, even though it worked for the UniRecord class? Or are we just missing a step somewhere? Any advice would be welcomed! Thanks, Jim Stoner ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Installing UniObjects on Windows 2008 64 bit
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
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Hi Jeff, You are right, the default version of the Windows 7 SDK object viewer that you access through the Start menu is 64 bit. The SDK does include a 32 bit object viewer, if you find and launch it manually. Thanks for clarifying that - I don't work in a Windows development shop, so I'm not really familiar with the issues of 32 vs 64 bit drivers/environments. I didn't even think to look for that. Using the 32 bit viewer, it does show the UnioaifCtrl class does show up. And of course, that implies the problem with my Domino agent is that we're running the 64 bit version of Domino on this server, which presumably cannot access the 32 bit UniObjects dll. Is there a 64 bit version of UniObjects? I've done a search for it, but haven't found one. Alternatively, would UniObjects for Java work with our Domino 64 bit version? Thanks for everyone's help, and sorry for having missed something so fundamental. Jim Stoner From: Lettau, Jeff jlet...@polkaudio.com To: U2 Users List u2-users@listserver.u2ug.org Date: 06/15/2011 08:29 AM Subject:Re: [U2] Installing UniObjects on Windows 2008 64 bit Sent by:u2-users-boun...@listserver.u2ug.org 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
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Can Domino use the .NET DLL directly? The .NET DLL should work in both x32 and x64. You have anyone who can write a wrapper for that DLL if not? -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jim.sto...@esc.edu Sent: Wednesday, June 15, 2011 4:28 PM To: U2 Users List Subject: Re: [U2] Installing UniObjects on Windows 2008 64 bit Hi Jeff, You are right, the default version of the Windows 7 SDK object viewer that you access through the Start menu is 64 bit. The SDK does include a 32 bit object viewer, if you find and launch it manually. Thanks for clarifying that - I don't work in a Windows development shop, so I'm not really familiar with the issues of 32 vs 64 bit drivers/environments. I didn't even think to look for that. Using the 32 bit viewer, it does show the UnioaifCtrl class does show up. And of course, that implies the problem with my Domino agent is that we're running the 64 bit version of Domino on this server, which presumably cannot access the 32 bit UniObjects dll. Is there a 64 bit version of UniObjects? I've done a search for it, but haven't found one. Alternatively, would UniObjects for Java work with our Domino 64 bit version? Thanks for everyone's help, and sorry for having missed something so fundamental. Jim Stoner From: Lettau, Jeff jlet...@polkaudio.com To: U2 Users List u2-users@listserver.u2ug.org Date: 06/15/2011 08:29 AM Subject:Re: [U2] Installing UniObjects on Windows 2008 64 bit Sent by:u2-users-boun...@listserver.u2ug.org 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
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Hi Marc, Can Domino use the .NET DLL directly? The .NET DLL should work in both x32 and x64. I'm not really sure. I'm not familiar with how .NET stuff works, and I've never seen anything talking about Domino working with native .NET libraries. Is the uodotnet.dll accessible as a COM object to other programs? I actually would prefer to use the .NET uniobjects instead of the original, just to have access to the UniDataSet class, but I haven't found any instructions for how to access it as a COM object. When I install the UniData client, it doesn't seem to put the uodotnet.dll file anywhere in the Windows directory tree; the only place it's put on the client computer is in the C:\IBM\UDK\uonet\bin directory. Could I just copy that to C:\windows\system32 and manually register it, then access it as a COM object? Or is the uodotnet.dll not a COM object? After some basic wikipedia reading on this topic, it looks like COM Interop might let me register a .NET component as a COM object, but I'm not sure what's involved with doing that. I also found some instructions on a related topic, that led me to try the following: C:\Windows\Microsoft.NET\Framework64\v4.0.30319regasm c:\ibm\unidk\uonet\bin\uodotnet.dll /tlb /c Microsoft (R) .NET Framework Assembly Registration Utility 4.0.30319.1 Copyright (C) Microsoft Corporation 1998-2004. All rights reserved. Types registered successfully Assembly exported to 'c:\ibm\unidk\uonet\bin\uodotnet.tlb', and the type library was registered successfully I don't know what to do from there, however. Uodotnet does not show up as an object in either the 32 or 64 bit object viewers, for example. So next I tried copying the .dll and .tlb files to the C:\windows\syswow64 directory, and then ran: C:\regsvr32 c:\windows\syswow64\uodotnet.dll That gave me an error of The module c:\windows\syswow64\uodotnet.dll was loaded but the entry point DllRegisterServer was not found. Make sure that uodotnet.dll is a valid DLL or OCX file and try again. So that's where I'm stuck at the moment. If I could get COM access to uodotnet.dll, that would be great. You have anyone who can write a wrapper for that DLL if not? I don't think we have anyone in-house who has the .NET skills (or even the software) to do so, although I'll check on that tomorrow. Thanks, Jim ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Keep in mind that 2008 has User Account Control like vista and 7. Its microsoft's crappy version of sudo in unix/linux. So I believe what some may be suggesting is that not only should you be logged in as Administrator, BUT, you should right click the executable and select Run as Administrator when installing. On 6/13/11, Bill Haskett wphask...@advantos.net wrote: Jim: I installed the U2 client from the udt_7.2acl.zip file onto Windows 2008 R2. It installed just fine. One thing I always do on Win 2008 R2 is run everything like this as administrator. There is so much that can go wrong, and very few people know how to resolve permissions issues. HTH, Bill - Original Message - *From:* jim.sto...@esc.edu *To:* u2-users@listserver.u2ug.org *Date:* 6/13/2011 2:07 PM *Subject:* [U2] Installing UniObjects on Windows 2008 64 bit Hello, We have a UniData server and are using UniObjects to access it from our web servers (using Lotus Notes/Domino). We have UniObjects working in Domino's Lotusscript scripting language on our production servers running Windows 2003. It also works on my desktop running Windows XP. I just tried to install the UniData client (udt_7.2acl, downloaded today from Rocket's website) on a development machine running Windows 2008 R2 64 bit, and the Domino agent that calls the Uniobjects.UnioaifCtrl object always fails with the error: ERROR 208 : Cannot create automation object. The UniObjects manual mentions that if you get an error saying it cannot create object that UniObjects didn't install property and instructing you to try re-installing. I've re-installed it three times with no luck. The UniData client installer runs fine, and seems to install the UniDevelopers Kit (the element that installs UniObjects) without any errors. There are no errors in the server's event log, and the file uniobjects.dll is placed into the C:\Windows\SysWOW64 directory on the server, which seems to be correct for a 32-bit dll on a Windows 2008 server. Next I downloaded and installed Microsoft's OLE/COM Object Viewer (a Windows 2008 compatible version is in the Windows 7 SDK installer), and installed that on both my desktop and the Windows 2008 server. On my desktop, the viewer shows that the UnioaifCtrl class is registered/installed. However, the UnioaifCtrl class does not appear in the viewer on the Windows 2008 server. Maybe the installation didn't register the object? Has anyone installed the UniData client, especially UniObjects, on Windows 2008 R2? Does anyone have any suggestions about why the client installer wouldn't be registering the automation object, or how to proceed? Thank you, Jim Stoner ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Sent from my mobile device John Thompson ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
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
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Sorry I don't have a 64-bit server for testing; however I was searching the kb yesterday (looking at how to install SBClient on 63-bit) and found a couple of articles that may help. One indicated that you should run the installer in Windows 2003 compatibility mode and the other was to change the CPU type (in Visual Studio) to x86 from AnyCpu. The first sounds like it would help and the second doesn't look like it will help until you actually compile/create something. Take a look at the Rocket Knowledge base (or ask your support provider) for more info. hth Colin Alfke Calgary, Canada From: Jim.Stoner 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
Re: [U2] Installing UniObjects on Windows 2008 64 bit
sounds like a UAC error. An installer can request elevated UAC permission - which is not the same as running as administrator. Turn off UAC in your control panel and try again... Brian Sent from my ASUS Eee Pad ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] Installing UniObjects on Windows 2008 64 bit
Hello, We have a UniData server and are using UniObjects to access it from our web servers (using Lotus Notes/Domino). We have UniObjects working in Domino's Lotusscript scripting language on our production servers running Windows 2003. It also works on my desktop running Windows XP. I just tried to install the UniData client (udt_7.2acl, downloaded today from Rocket's website) on a development machine running Windows 2008 R2 64 bit, and the Domino agent that calls the Uniobjects.UnioaifCtrl object always fails with the error: ERROR 208 : Cannot create automation object. The UniObjects manual mentions that if you get an error saying it cannot create object that UniObjects didn't install property and instructing you to try re-installing. I've re-installed it three times with no luck. The UniData client installer runs fine, and seems to install the UniDevelopers Kit (the element that installs UniObjects) without any errors. There are no errors in the server's event log, and the file uniobjects.dll is placed into the C:\Windows\SysWOW64 directory on the server, which seems to be correct for a 32-bit dll on a Windows 2008 server. Next I downloaded and installed Microsoft's OLE/COM Object Viewer (a Windows 2008 compatible version is in the Windows 7 SDK installer), and installed that on both my desktop and the Windows 2008 server. On my desktop, the viewer shows that the UnioaifCtrl class is registered/installed. However, the UnioaifCtrl class does not appear in the viewer on the Windows 2008 server. Maybe the installation didn't register the object? Has anyone installed the UniData client, especially UniObjects, on Windows 2008 R2? Does anyone have any suggestions about why the client installer wouldn't be registering the automation object, or how to proceed? Thank you, Jim Stoner ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Were you logged in as an administrator when you installed UO? We have UO installed on our Windows 2008 R2 64 server with no problem, and I don't recall that we had any problems when it was installed. I do not, however, recall what version of UO it was. -Kevin http://www.PrecisOnline.com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] Installing UniObjects on Windows 2008 64 bit
Jim: I installed the U2 client from the udt_7.2acl.zip file onto Windows 2008 R2. It installed just fine. One thing I always do on Win 2008 R2 is run everything like this as administrator. There is so much that can go wrong, and very few people know how to resolve permissions issues. HTH, Bill - Original Message - *From:* jim.sto...@esc.edu *To:* u2-users@listserver.u2ug.org *Date:* 6/13/2011 2:07 PM *Subject:* [U2] Installing UniObjects on Windows 2008 64 bit Hello, We have a UniData server and are using UniObjects to access it from our web servers (using Lotus Notes/Domino). We have UniObjects working in Domino's Lotusscript scripting language on our production servers running Windows 2003. It also works on my desktop running Windows XP. I just tried to install the UniData client (udt_7.2acl, downloaded today from Rocket's website) on a development machine running Windows 2008 R2 64 bit, and the Domino agent that calls the Uniobjects.UnioaifCtrl object always fails with the error: ERROR 208 : Cannot create automation object. The UniObjects manual mentions that if you get an error saying it cannot create object that UniObjects didn't install property and instructing you to try re-installing. I've re-installed it three times with no luck. The UniData client installer runs fine, and seems to install the UniDevelopers Kit (the element that installs UniObjects) without any errors. There are no errors in the server's event log, and the file uniobjects.dll is placed into the C:\Windows\SysWOW64 directory on the server, which seems to be correct for a 32-bit dll on a Windows 2008 server. Next I downloaded and installed Microsoft's OLE/COM Object Viewer (a Windows 2008 compatible version is in the Windows 7 SDK installer), and installed that on both my desktop and the Windows 2008 server. On my desktop, the viewer shows that the UnioaifCtrl class is registered/installed. However, the UnioaifCtrl class does not appear in the viewer on the Windows 2008 server. Maybe the installation didn't register the object? Has anyone installed the UniData client, especially UniObjects, on Windows 2008 R2? Does anyone have any suggestions about why the client installer wouldn't be registering the automation object, or how to proceed? Thank you, Jim Stoner ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
