So the web app is done and it's time to test. I give the address to the clients, and let them go at it. Immediately, the phone rings. Turns out they can't even log into it. So I go back and check the permissions and such. No good. I go over to a client workstation and log in. I can access the app just fine. I go up to their workstation, and I can't access the app at all.
WTF?
So I go over permissions and settings and all kinds of crap... I have no idea what's going on. Until I notice one thing... it's not applying the stylesheet to the pages on their workstations, whereas it's working fine on mine. Curious... I check the link for the stylesheet and noticed that it points to a folder they don't have access to. That would explain why they keep getting asked to login every 2 seconds. And why they get different login dialog boxes. (The client folder uses basic authentication, the internal one uses integrated Windows authentication.)
So we get the stylesheet in the right place, and now they can log in, but are still getting permissions errors on the database. Weird. Now I tackle that by granting the group all permissions on the user tables and stored procedure. (Select, Insert, Update, and Delete on the tables, and Execute on the procedure.) Still erroring out. So, I add the users individually. Still errored. As a last ditch attempt, I just give the users DBO, or admin rights on the database. Sure enough, that works. I'll have to go through the dependencies individually and see what exactly the deal is. There's something in there that's a system resource that they require access to. I just have no idea what it is.
End result though, the client likes the product, and is enjoying it so far. Now all I have to do is make the history work for last year's data.
Always one more thing... That's development, I guess. :-)
No comments:
Post a Comment