We have resolved this by having the Administrator copy the privileges data file from another account that we know to be working to overlay the one we know is not working. That did the trick. The vendor, on the other hand, recommended we take the whole account and overlay the account that was experiencing the problem, then manually correct the hundreds of pointers that were in the source VOC. Frankly, such shotgun-blast idiocy should be punished.
The only difference between the old version of the file and the new version of the file was the missing information about the privileges file. Everything else was identical. Unfortunately, I don't know how the account was originally created; that was all done by the vendor. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Monday, November 14, 2005 1:17 PM To: [email protected] Subject: RE: [U2] Problem with privileges file Try checking the actual windows permissions (especially the owner) on the file. I've seen some strange things happen with them. How was this account created?hth Colin ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
