error '80004005' in ASP Page

P

PHTech

Senior Member
Joined
Aug 21, 2006
Messages
588
Reaction score
0
Location
Witbank
Hi there...

I am struggling with this annoying damn error almost the whole day now... "error '80004005'". I Get this error on one ASP Page that I have created, and only gives me that error AFTER I have added a Binding into the page... Upon testing the data in Dreamweaver CS4, it displays correctly from withing the SQL menu, but afterwards it gives me this hateful error...!!! :mad:

I am using Windows Vista & IIS7.0. I have given every thing and folder imaginable FULL permissions, and even changed the temp file location in the Environmental Variables... I also use an Access DB for this webpage...

This is what is displayed on screen.

error '80004005'
/xcsa_intranet/pages/sites/goedgevonden/ggvtel.asp, line 9

ANY HELP PLEASE PLEASE PLEASE...!!!
 
Any luck with this? I remember getting this error - just can't remember what it meant.
 
I have managed to get this working...! This stupid error is only to do with the permissions... I have elevated the user account permissions BUT still no luck. Then when I added the IUSR account, everything worked like a dream...! Weird hey...

Thanx to Windows Vista, you must add permissions to every little thing you want to do... I bet in WinXP this type of error won't easily appear...

Thanx for your assistance...
 
Don't bother upgrading to .NET. ASP classic isn't dead yet and can still do a lot ;)

FYI, I'd stay away from MS Access DB's. You'll find when you move your application to the server you will most likely have the same issues. And if your client hosts on a shared environment you won't be able to get the admins to change things around for you.

Shared hosting packages comes free with a slew of databases you can use that's 104985749 better/faster and more reliable than "omg I looked at the database and it got corrupted" MS Access.

Even SQL Server 2005 Express is free so you really don't have an argument ;)

Next time post your code. Line 9 means absolutely nothing to us and ODBC errors (and CDO) are usually the ones that's less descriptive of anything ever found in windows.

Be sure to check out the Event Viewer, sometimes it'll give you a better idea of what is going wrong. A lot of people forget the Event Viewer. It usually logs more detailed descriptions.
 
AcidRaZor said:
Don't bother upgrading to .NET. ASP classic isn't dead yet and can still do a lot ;)

FYI, I'd stay away from MS Access DB's. You'll find when you move your application to the server you will most likely have the same issues. And if your client hosts on a shared environment you won't be able to get the admins to change things around for you.

Shared hosting packages comes free with a slew of databases you can use that's 104985749 better/faster and more reliable than "omg I looked at the database and it got corrupted" MS Access.

Even SQL Server 2005 Express is free so you really don't have an argument ;)

Next time post your code. Line 9 means absolutely nothing to us and ODBC errors (and CDO) are usually the ones that's less descriptive of anything ever found in windows.

Be sure to check out the Event Viewer, sometimes it'll give you a better idea of what is going wrong. A lot of people forget the Event Viewer. It usually logs more detailed descriptions.
Click to expand...
+1. This is how to answer, people! Listen up and take note. ;)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X