If it was permissions then it would happen all the time. I would look at a timing issue. Windows is known to hold on to resources, maybe a sleep command in the right place could avoid it?
Thanks, David A. Green www.dagconsulting.com (480) 813-1725 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kevin King Sent: Thursday, September 17, 2009 3:26 PM To: U2 Users List Subject: [U2] Z_xxxxxxx not created The UDT.OPTIONS manual explains that when a program does a EXECUTE... CAPTURING... there is a temporary item created in _PH_ called Z_ followed by the PID. I have tested this and found it to be true, and the item is immediately removed after the CAPTURING has read its value. I have a client on a Windows UD server where from time to time they get a message that says: Can't open D:\...path...\Z_xxxxxxx for writing/capturing job. It's enough to blow SB+ GUI out of the water unfortunately. Permissions issues aside, what might cause this to happen? The client is literally thousands of miles and an ocean away so I can only diagnose remotely, have no access to view or verify the Windows permissions settings (though they assure me that's not the issue) and this doesn't happen with enough regularity to be able to watch for it, but it's irritating them. Help? -Kevin http://www.PrecisOnline.com _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
