August 8, 2003 at 7:57 pm
An application with SQL Server 2000 runs fine when connected to a network but when the application is run locally,it errors complaining about object variable not set. Normally an object permission problem but the permissions are fine. When run logging on to the network domain with LAN disconnected,its runs fine, logoff and logon to the local machine and run it, the error reoccurs. Totally stumped,been through the permissions and systems tables everything is okay, are there any known problems with windows 2000 o/s and sql server integration that could be causing this?
August 11, 2003 at 7:24 am
That's normally Visual Basic error indicating an unitialized object variable, not a permission issue.
dim o as object
set o = GetUser()
if o.Name <> "" then
...etc...
In the above, if the line
set o = GetUser()
failed, the next line would produce that error (the function GetUser is just an example). If the code checks the network user name or domain group membership prior to allowing access, this might occur, depending upon how it was getting this information.
-------
at us, very deafly, a most stares
collosal hoax of clocks and calendars
eecummings
August 12, 2003 at 6:06 pm
Thanks for that.
I agree that the error is normally associated with an unitialised object. its due to However, this is not the case here. The application uses a localised sql login to connect to the db. If it was an application error due to incorrect domain or login I would expect it to occur across any local machine the app was loaded to particularly when we use the same user as a test case. The user connects to the server via windows authentication and then connections to the app db via sql authentication. The first connection works fine the second is where the problem lies.
On local machines running MSDE which have not been connected to the network,its fine. Put it on a machine that has been connected to our LAN domain in the past week and is now running locally, it crashes. This is only a recent development. Its not a virus.
We think the problem started last Thursday about the same time we downloaded a hotfix for our Windows server, something to do with OLE32 but we just don't know for sure.
I think its just one of those peculiar things we will have to investigate internally
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply