The search keyword is (same as before)
Microsoft JET Database Engine unspecified error
The error message is
Microsoft JET Database Engine (0x80004005) Unspecified error
Yesterday I switched from win2003 to winxp pro version, but when debugging the photo album program, I found the above error. This error has been bothering me for a day today, and I haven't been able to find a solution, nor can I reinstall the system. But the program runs normally on the win2003 server. After searching on the Internet, I found that there are many reasons for this, the most common ones are the following two.
reason
The access permissions of the system temp file are not enough. In the past, I always focused on IIS, the permissions of the file itself, etc.
Most people don't seem to think that there is a problem here. Before today, I had never thought about it...
Solution
Modify the security options of the temp folder under windows or winnt
Plus everyone has full control
At least give the IIS guest user write permissions
But I followed these two methods to set it up, but it still didn't solve the problem, so I reinstalled the system, but it still didn't work. Haha, I'm depressed.
I know that the reason for this must be a permissions issue. But I just don't know what went wrong. There is no solution found on Microsoft's official MSDN. So I thought, why not try setting the directory permissions of IIS, so I set the website in iis to not allow anonymous access, and it worked. I feel very puzzled, because as a website, anonymous access must be allowed, so I think this is not a normal solution. Just leave it to be solved later...
There is another way: set the /windows/system32/config/systemprofile/Local Settings/TEMP directory permissions to readable by everyone. The problem is finally solved.
Three additional situations were found:
The first solution: Use "Tools->Database Utilities->Compress and Repair Database" in Ms Access to repair db/global.asa. If the error still occurs after repairing, please check whether there is a global.dbl file in the db directory. If there is, please delete it. If it cannot be deleted, please end the server w3wp.exe process (win2003) or Aspnet_wp.exe process (win2000) and then delete it.
Second solution:
Set the application pool in Internet Information Services (IIS) Manager and change the application pool properties of the website as shown in the figure below:
The problem can be solved after adjustment.
Third solution:
In fact, it only takes a few simple steps:
start. . . run. . . regsvr32 jscript.dll starts. . .
run. . . regsvr32 vbscript.dll starts. . .
run. . . iisreset