Hi, David. I've been testing your suggestion for the past couple of days. Selecting "allow this service to interact with the desktop" does indeed somehow keep the service alive (and I suppose I can live with the DOS window that pops up whenever a connection is made...)
Thanks for the information! Regards, -- Bryan Shumsky Director of Engineering Via Systems, Inc. ----- Original Message ----- From: "David Jordan" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, December 06, 2004 6:48 PM Subject: RE: [U2] Problem with RPC calls to UniVerse on Windows 2003? > This seems to be common problem on windows 2003. One of the resolutions is > to go to services menu under administration tools. Select the properties > for universe RPC and under the login tab select to allow this service to > interact with the desktop. > > Under windows 2003 there are a number of security features and I suspect > that part of this is to close down unrecognised sockets that have not been > active for a while. I believe there is somewhere where you can keep this > active, but have not had time to explore. > > Hope this helps > > Regards > > David Jordan > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Bryan Shumsky > Sent: Tuesday, 7 December 2004 4:17 AM > To: [EMAIL PROTECTED] > Subject: [U2] Problem with RPC calls to UniVerse on Windows 2003? > > Hi, everyone. I've just been working on a project using the UniObjects for > Java stuff, and it all works fine...for a little while. That is, I can make > connections and do 'thinkgs' on the UniVerse system, connecting and > disconnecting with no problem. But after "a while" of inactivity (exact > duration unknown), I find I can no longer make the connection any more - the > call returns with "The RPC failed." Rebooting the Windows 2003 system makes > things work again. Note that I'm not trying to reuse the connection, or the > session, or anything; I've actually quit out of my program, and am trying to > go back into it again. > > At first, I suspected that there was something awry in my Java code, but > I've discovered that I can create the same problem just by using the > UniVerse Admin tool; again, I connect, and "do stuff" with no problem, but > after disconnecting and waiting a while, attempts to reconnect generate the > dialog box "Unable to open connection - Error 81002 - connection is broken". > As the Admin tool is on the same box as UniVerse, this eliminates any > questions (I think) of firewall issues, networking problems, etc. > > While this makes me feel better about my UOJ code :-) it means there's > something else going on here. I don't know if it's related to being on > Windows 2003 Server, or the fact that this is the Personal Edition of > UniVerse (just downloaded from the IBM site; version is 10.0.10), or...? If > it's just something unique to the PE, that's fine; I'm using this for > testing and development, and if it works correctly in the "real" world, then > that's OK, but it'd be nice to know what's going on. > > Thanks! > > -- Bryan Shumsky > Director of Engineering > Via Systems, Inc. > ------- > u2-users mailing list > [EMAIL PROTECTED] > To unsubscribe please visit http://listserver.u2ug.org/ > ------- > u2-users mailing list > [EMAIL PROTECTED] > To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
