Mornin all,
First may I say thank you to everyone, for without this site, and a few others, my initial foray into IIS7 and Vista would have been cut short by a wail of despair and a reformat! So ....
Thank you!
Now on to the fun stuff:
Bill S, in his "loadUserProfile and IIS7 - understanding temporary directory failures" post gives us different ways to handle the dreaded "Operation must use an updateable query." error if and when we are confronted by it; alas, I've run smack into it! Twice!
Here's what happened:
I loaded a current project onto the new laptop as the groundbreaking piece to see what IIS7/Vista could do! This project is for a local charity and uses a simple Classic ASP driven CMS and Access to reduce overhead. After scouring the net and coming to terms with the differences in directory locations and virtual paths and application pools (so I thought) I load the Administration section into the browser and low and behold I can't update the database due to permissions. So back to the net I go and I stumble across a post which explains about using either the icals commands to change the permissions or simply edit the applicationHost.cofig file and add the following:
<applicationPoolDefaults>
<processModel identityType="NetworkService" loadUserProfile="false" />
</applicationPoolDefaults>
So, taking the easy way out, and thereby learning all about running programs in elevated status and the wonderful nightmare that entails [note heavy sarcasm here], I duly c&p these three line to the file, save, return to the browser and hit ctrl & f5....
Cha-Ching!
Everything works!
I'm able to update to my hearts desire, the site is reading everything fine and development can finally complete! The clients happy, I'm happy, we're all happy! :-)
So I move onto a new project,
This one is a bit more complicated, I decide that I need to start updating a personal site I first developed in 2002 which was my first attempt at Classic ASP and therefore was in dire need for an overhaul. So I download a copy of the currently live site, which runs on 2k3 server/IIS6 fine with never a problem, create the new site following all the loverly lessons learned previously, switch to the browser load the flash intro [I know, no comments please!] get into the front page to log in and ...
BAM!
I seem to have hit a brick wall!
Again.
The same brick wall I thought I knocked down with the first site ...
Microsoft JET Database Engine error '80004005'
Operation must use an updateable query.
/index.asp, line 36
So back to the net I go, and this is when I come across Bill's posting which talks about the right, and somewhat lesser right, way to handle this issue; and the right way being to use the icals statements in an elevated status command prompt instead of changing the applicationHost.config file.
So I do.
But nothing is different!
So here's the rub, I've checked the code in the applicationHost.config file, nothings changed;
I've checked the actual security settings of the
%system%\ServiceProfiles\NetworkService\AppData\Local\Temp directory:
NETWORK SERVICE has full rights,
IIS_IUSR permissions are set to Modify, Read, Write.
I've checked the permissions on the database folder within the site, as well as the permissions of the actual .mdb files
Nothing!
I keep getting the '80004005' error and cannot figure out what I can do to be able to sort it out!
Not only that, the original site, the charity one, now is throwing out the same errors as well?
So I duly apologise for the long post but..
HELP!
Please!
Jon