Helps more than not knowing what the Jet error was. Do any of the root causes referenced in KB Article 253111 apply?
Another process has "stolen" the file. A virus checker may mistakenly quarantine a file, or a backup process may temporarily deny access. A disk or controller failure has occurred, and access to the entire drive has been lost, sometimes temporarily. Check the System Log for I/O or drive errors near the time of the 158 Event. Permissions have been removed from the folder where the file resides. The file has been marked read-only. This is most likely to happen to a checkpoint file. The folder containing the file has been renamed or deleted. This is also mostly likely to happen to a checkpoint file. On 3/31/03 17:53, "Ted Mosher" <[EMAIL PROTECTED]> wrote: > The error is Jett_errFileAccessDenied when I run ISINTEG -PATCH > > Does that help? > > -----Original Message----- > From: Chris Scharff [mailto:[EMAIL PROTECTED] > Sent: Monday, March 31, 2003 9:58 AM > To: Exchange Discussions > Subject: Re: Strange Exchange 5.5 Windows 2000 Question > > > Which Jet Errors? There are a number of them. > > On 3/29/03 18:55, "Ted Mosher" <[EMAIL PROTECTED]> wrote: > >> Strange question for anyone who may have tried this... >> >> Can you restore an Exchange 5.5 server that was backed up with Backup >> Exec with the Exchange Option from an NT4.0 server to a copy of >> Exchange 5.5 (same site/org) but running on a Windows 2000 server with > >> the same domain - Here is the catch - but the domain has been upgraded > >> to AD. >> >> I tried it and get Jet Errors when I try Isinteg -Patch.. >> >> Has anyone every done this? Seems like it should still work. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
