HTTP 401.3

mat41 · August 2nd, 2009, 11:16 PM

This permissions issue has poped it head out of blue. I have had it before but not for a long long time. The site its happening on was working one and then this error the next, all I have done is a DB restore (SQL Server 2000). It my dev environment XP IIS 5.1

I have looked at everything. I am using the default anon access under the IUSR_mahineName user. In fact I have got so frustrated at this I have given full control to everyone. I did research this for a while before posting here.

Any ideas?

TYIA

aspless · August 3rd, 2009, 05:35 AM

Mat,

Ever considered using VMware?

Instead of developing on XP i have a virtual 2003 server as my development platform.

Also allows you to have multiple versions of XP for browser versions, domain policy checks ect ect..

I did try and use XP as my primary dev O/S and it just gave me head aches!!

Just a thought ..

Cheers

Aspless

mat41 · August 3rd, 2009, 06:47 PM

Yes few guys in the office do run VMWare. I have a seperate 2003 machine to work with however....

I am mistified at this issue. its the only site which is doing this. Its been running fine for a couple of years, so annoying!

Any ideas what I can check?

aspless · August 4th, 2009, 04:41 AM

Ok .. My clutching at some logical straws we can discount any of your existing web site file permissions as they have not changed.

Can you connect using a test page to your restored SQL DB? If you can then my next 'try this' will have no affect .. If you can't then my try this is to remove the SQL user associated with the restored DB and re associate the account.

I have had issues in the past with matching restored user accounts with existing accounts in SQL ..

I am sure the actual file permissions of the MDB and log files are of little importance when restoring to SQL but as a secondary clutch you could check them too.

Hope my ramblings may point you in the right direction ..

Aspless

mat41 · August 4th, 2009, 07:19 PM

mmmm I dont think this 403.1 error even gets to the DB connection string therefore what ever use I am using to connect wont alter things. This is proven when I place the sa user details in the string.....

Its got to be application folder permission related I think. So annoying, I will try to re-create the site ina new application folder with a different name.....