Database read only - error 2147467259

Database read only - error 2147467259 (Full Version)

All Forums >> [Web Development] >> ASP and Database

Message

rubyaim -> Database read only - error 2147467259 (7/13/2005 20:03:51)
Hello, am hoping someone can point me in the right direction here. Have a small members only site for our Athletics club (far more important than work [;)] ). Site is remotely hosted on IIS 5 and it's an Access 2000 db. Has been chugging away very nicely for several months with no problems at all. A user emailed me last night saying they kept getting errors when trying to update. Just tried it and am seeing: Database Results Error Description: [Microsoft][ODBC Microsoft Access Driver] Operation must use an updateable query. Number: -2147467259 (0x80004005) Source: Microsoft OLE DB Provider for ODBC Drivers I downloaded the database and it looks fine. Have tried several times to overwrite the db on the server (FTP - Filezilla) and am getting a 'Critical Transfer Error'. Have checked the FPDB folder and global.asa and all looks okay. There is another database on that server that is working. In desperation tried to recalculate the hyperlinks on the site (probably nothing to do with anything though), and am getting this error: "An error occurred accessing your Windows SharePoint Services site files. Authors - if authoring against a web server, please contact the webmaster for this server's web site. Webmasters - please see the server's application event log for more details." Problem is we don't have SharePoint and in FrontPage I've always had SharePoint Services unticked. I guess I'll need to contact our host, but am wondering if this is a FP Extensions issue, or a permissions issue? I like to have as much info as possible before I call as otherwise I tend to get confused by tech speak [:o] The site settings on FP show - FrontPage Server Extension version: 4.0.2.7802 I've not tried importing the database through FrontPage as in the past using FTP has been fine. Many thanks in advance for any advice. Sally

Spooky -> RE: Database read only - error 2147467259 (7/13/2005 21:43:17)
Generally it means that the permissions have changed. Youll need to ask your host to change the permissions for the database file so that the anonymous account has read / write access to the file

rubyaim -> RE: Database read only - error 2147467259 (7/13/2005 21:47:23)
Spooky, thank you - will phone them now. Sally

Spooky -> RE: Database read only - error 2147467259 (7/13/2005 21:48:52)
note - I meant permissions for the folder, not file

rubyaim -> RE: Database read only - error 2147467259 (7/13/2005 23:13:51)
Spooky, thanks again. Just had a fairly unsatisfactory conversation with tech support, and sent a detailed email (including a link to the 4GuysFromRolla info on the error)... Apparently the IUSER does have read write access. Was told it is a proxy error on my end? I don't actually use a proxy for this site (but do for work). If it is a proxy thing, I wonder why the db is the only file jammed? Could the last user somehow locked the db up via their connection? I hate it when things like this suddenly happen when I know for sure I've made no changes. Am also concerned about the SharePoint thing. Thanks for listening - hopefully overnight things will suddenly start working again - have had that happen before [8\|] Sally

Spooky -> RE: Database read only - error 2147467259 (7/13/2005 23:51:28)
Heres some more information, however the fix is typically the same : http://www.aspfaq.com/show.asp?id=2062

rubyaim -> RE: Database read only - error 2147467259 (7/14/2005 0:10:52)
Excellent - thanks once again! Emailed tech support with that link and am crossing fingers. Sally

rubyaim -> RE: Database read only - error 2147467259 (7/14/2005 2:01:28)
Just as well I had an RDO today - so much for working in the garden... Still not joy, and I think I'll have to believe the host that the permissions are correct (but not about the proxy). The other database on this site that is working is the Spooky Login. Pulled in a testing db, set up a few pages and that works. I tried importing the 'real' db and am getting 'Server Error - file is in use'. Can't delete it, rename it, can't really do anything at all. Have tried in FrontPage and via FTP. Have emailed the user from last night to see if there is the possibility that they are still connected (very, very long shot). Edit: The user was in using Table Editor at time of failure - 3 of us use this from time to time. Am really not sure if that would make a differece. Have been using it for about 12 months with no previous issues at all. I know that no-one here can really help with this, but was wondering if anyone had experienced a similar problem at all? Sally

Spooky -> RE: Database read only - error 2147467259 (7/14/2005 2:43:02)
Is the working database in the same folder as the not working one? What sort of code is creating this error? the DRW or is it custom asp?

rubyaim -> RE: Database read only - error 2147467259 (7/14/2005 19:18:18)
Hi Spooky, thanks for bearing with me on this, it's greatly appreciated. The DRW's (updates, inserts, delete's) are returning the error as well as the Table Editor (editing records, can view all data). All DB's on this site are located in the FPDB folder - including the Spooky DB and the couple of test ones I pulled in yesterday. I've about 20 or so pages that are just returning DB results and they are all functioning normally, as are the few pages for export to Excel. It appears as if it's just that one .mdb file that is locked. I was able to transfer it back here via FTP and have no problems with it locally at all - it's not corrupt, all relationships are as they should be, it was compacted etc. I recalculated hyperlinks this morning again out of curiosity and that worked - no SharePoint error this time at least. I'm wondering if my only option may be to import the database with a new name and then re-do all the DRW pages (or even re-do them in pure ASP as I've finally managed to get my head around the connections) .... am not really sure what to do about the jammed .mdb file though - probably just try to delete it every time I'm in that web. Thanks again. Sally

Spooky -> RE: Database read only - error 2147467259 (7/15/2005 3:25:49)
Are you sure that the file itself isnt read only?

rubyaim -> RE: Database read only - error 2147467259 (7/15/2005 18:18:27)
Well, the file is working as 'read only' as it's locked... It's acting like a typical Access database when it thinks there is still a connection to it. The .mdb itself is not read only. Spent hours on this yesterday and tried the following (just posting in case someone else has the same issues): Opening the DB from the web with the 'shift' key down (okay, useless really, but worth a go). Breaking the connection to all the pages that connect to the db, then writing a query that points to an existing table but non-existing column, then jumping in quickly to try to delete the database. Tried this 16 times and gave it away. Several hosting info pages recommend this, eg: http://www.enterhost.com/supportcenter/faq/search_answer.cfm?fqid=100113 Writing some code to unlock (but I don't know enough to do this properly). Found some code for dot net, but was unable to write in ASP... maybe this time next year I can manage that. In the end, after a lot of conversations with the host, they disabled asp on the server and then renamed that database with a .mdb.bak extension. That allowed me to import the database. Am still waiting for asp to be enabled...... Things like this are a good learning curve - I've learned more about databases locking than I ever wanted to know [&:] Sally

rubyaim -> RE: Database read only - error 2147467259 (7/16/2005 0:44:58)
A phone call to the host later to remind them that the asp pages were not working and everything is fine and back to normal. If I have this problem again will take these steps: 1/ Get copy of the database from the server (using FTP). Check database in case it's corrupt. If okay .... 2/ Ask host to look at the permissions first, send them link to http://www.aspfaq.com/show.asp?id=2062 If permissions okay then... 3/ Request host delete that file from the server. Stay on phone while this is done. If unable to stay on phone, call them back periodically (say, every 2 minutes), and nag until it's done. Paying a fair bit for hosting - figure this is to cover irritating clients, so in future plan to be irritating. 4/ Import the database back in. 5/ Cross fingers that it works when back in. I'd love to know how it locked in the first place [8\|] Spooky, thanks for replying here - finally work up the courage to post to the forums and seem to spend most of the time talking to myself - will never need a blog [sm=icon_redface.gif] Sally

Page: [1]

Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.046875