Desiree
|
| Posted: 02/17/2002, 5:18 PM |
|
I am experiencing a difficulty in going live with any of my pages. I get an error about the microsoft jet database ... the workgroup is missing a file or it is open exclusively by someone else. Then under the sys ad section of the error it says to check the common.asp file line 25. It states to open the database. I have compared my common to the other example commons and they are exactly the same but the database file names are different. PLEASE help me. I am desperate for screenshots for a customer presentation!!
|
|
|
 |
Andrew B
|
| Posted: 02/17/2002, 6:07 PM |
|
1. Try re-starting IIS. Sometimes it will lock the db (cc opens in lock exclusive move) and then not let it go.
2. Upgrade to the newest version of MDAC (on microsoft.com or msdn.microsoft.com)
3. Is the database using 'security'?
4. Check for a <dbname>.ldb file. If it is there, remove it. If you can't and a restart of iis doesn't let you, try rebooting.
Could you copy the error message up, along with the line of code that is failing?
|
|
|
|
Desiree
|
| Posted: 02/17/2002, 7:37 PM |
|
The page cannot be displayed
There is a problem with the page you are trying to reach and it cannot be displayed.
--------------------------------------------------------------------------------
Please try the following:
Click the Refresh button, or try again later.
Open the localhost home page, and then look for links to the information you want.
HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services
--------------------------------------------------------------------------------
Technical Information (for support personnel)
Error Type:
Microsoft OLE DB Provider for ODBC Drivers (0x80004005)
[Microsoft][ODBC Microsoft Access Driver] The Microsoft Jet database engine cannot open the file '(unknown)'. It is already opened exclusively by another user, or you need permission to view its data.
/RIMS/Common.asp, line 25
Browser Type:
Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Page:
GET /RIMS/default.asp
Time:
Sunday, February 17, 2002, 10:45:34 PM
More information:
Microsoft Support
|
|
|
|
AudiTT @ MCI
|
| Posted: 02/17/2002, 9:50 PM |
|
Are you using MS Access?? This would happen if you have MSAccess editing the MDB, and trying to getr IIS to load the same DB.. If not, disreguard..
Bryan
|
|
|
|
Nicole
|
| Posted: 02/18/2002, 5:37 AM |
|
Desiree,
refer to following article on this error:
http://support.codecharge.com/files/CodeChargeFAQ.html#_Toc517263838
|
|
|
|
redSnake98
|
| Posted: 05/03/2002, 2:56 AM |
|
I am getting the same error. I have tried all the other advice posted on this site--including setting up a System DSN. Same error everytime. I'm also able to connect to the Access Database from every other DB application on the same machine--CodeCharge only product that consistently dies.
It's getting very late, I've wasted way too much time, and I think it's time to return to my own ASP code (which checks ALL return codes AND runtime errors--logging them to a flat file in great detail as they occur). Nothing more frustrating than flying blind.
CodeCharge really needs to add some 'commercial-grade' exception handling to their generated code. It's currently implemented as though all code will work all the time without error (classic programming 101 mistake). If they ever expect it to adopted by professionals, it will need to generate true professional grade code.
|
|
|
|
redSnake98
|
| Posted: 05/03/2002, 3:15 AM |
|
Peace. I found the answer in the following thread:
"I can't stand it anymore..."
However, my statement regarding the need for 'commercial-grade' exception handling still stands. Because CodeCharge is a code-generator, it should not be that difficult to retrofit. The resultant increase in programmer productivity would be vastly enhanced (I've seen incredible improvment on all the projects I've ever been directly involved in where that attention to detail has been introduced into the coding practices). For every minute a programmer isn't chasing down mysterious behavior, that's another minute (usually more like hours) they can devote to creating a product.
All-in-all you guys are on the right track. Keep up the good work. But, do add commercial-grade error checking, reporting, and recovery to your to-do list. It will transform your product from a 'very cool curiosity' to a mandatory 'killer-app'.
I wish you great success.
|
|
|
|
|
