PDA

View Full Version : Security Assist Log In Page Error


te_araroa319945
05-22-2009, 09:02 AM
Hi there,
Have just run the Security Assist wizard to generate log in pages and such. When I test the log in to access the Admin side of my site I receive this error -

Provider (0x80004005)
Unspecified error
/WA_SecurityAssist/Helper_JS.asp, line 15

line 15 of Helper_JS.asp is this -

WA_Auth_login_cmd.ActiveConnection = WA_Auth_Parameter.connection;

I get the same error when i try the Email Forgot Password page except this time the error is on line 81

line 81 of Helper_JS.asp is this -

WA_Auth_Forgot_Recordset_cmd.ActiveConnection = WA_Auth_Parameter.connection;

so this suggests its something to do with a database connection??But basically I'm stuck!!Have used this wizard before and had no problems so this is strange!!Can anyone shed any light of this problem for me?
Thanks in advance.
Colin

Ray Borduin
05-22-2009, 09:23 AM
This is a permissions error on the access database you are using. It basically means the IUSR_Machinename doesn't have privilages to create a lock file properly. This is a pretty common problem in the classic ASP with Access database world, so you should be able to find more detailed instructions on solving it on an Adobe tech note or other online resource.

te_araroa319945
05-22-2009, 10:15 AM
Hi Ray,
I've had permissions problems before so I checked that first and have added the Internet Guest Account Permission to all files in the site. I logged in fine a moment ago but now its gone back to the same error,I don't think its a permissions thing any other ideas?
thanks
Colin

Ray Borduin
05-22-2009, 11:01 AM
I'm sure this is permissions related ;)

try: http://support.microsoft.com/kb/307874/en-us

The reason why you logged in fine the first time is because it was the first time accessing the database... but then since it didn't create the access lock file properly because of permissions, it wouldn't allow you to access the database the next time.

I think in this case you would be better off researching how I could be right and doubting your own conclusion rather than doubting my conclusion. I can tell you that since it worked once, it isn't your code... so if it isn't permissions then I'm going with witchery or voodoo as the cause.