Re: ADP Project Trusted Connection Issue?
From: MikeC (anonymous_at_microsoft.com)
Date: 11/22/04
- Next message: Arthur: "Re: Permissions problem"
- Previous message: Rick Brandt: "Re: Can not open other Access DBs if joining security workgroup file"
- In reply to: Sylvain Lafontaine: "Re: ADP Project Trusted Connection Issue?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 22 Nov 2004 22:32:59 GMT
Sylvain,
You are absolutely correct. The problem was related to my account!
After some further troubleshooting, I discovered that my account had been
*removed* from the Administrator group on my local machine!!!
After some special effort from my local desktop support people, they managed
to add my account back to the group. Now I can connect to the database
without any problems.
Now that I have admin permissions again, I can also start and stop SQL
Server, so this allowed me to change my authentication mode to Mixed in the
registry. I'll set up a SQL Server account for myself just in case this
problem happens again in the future. Thanks for your help.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:OXmkKbN0EHA.2624@TK2MSFTNGP11.phx.gbl...
> Sorry, for the provider, it's my error. After verification, I see that
the
> dialog box for ADP project only permits the SQL-Server OLEDB Provider.
It's
> hard to follow all these different dialog boxes these days. Forget about
> the DSN.
>
> For the registry setting, try to change the setting and reboot your
> computer. Go into safe mode if necessary to change the setting. Look
into
> the services window to see if they are nothing unusual about the
SQL-Server
> service.
>
> If I were you, I would stop the SQL-Server (by going into safe mode if
> necessary); make a copy of the database files and desinstalls/reinstalls
the
> whole thing.
>
> Also, I'm not sure but it's quite possible that loging as Administrator
and
> not with another account with administrator rights can change things.
Maybe
> there is something wrong with the account that you are using presently.
>
> S. L.
>
> "MikeC" <anonymous@discussions.microsoft.com> wrote in message
> news:M5sod.21136$zx1.9389@newssvr13.news.prodigy.com...
> >I am unable to find the provider in the "Data Link Properties" dialog
box.
> >This is the dialog box that displays when I select Connection... from the
> >File menu. Should I be looking somewhere else?
> >
> > I also tried to change the server to "(local)", but I'm continuing to
> > receive the same error.
> >
> > I'll try creating a DSN and see if that makes any difference.
> >
> > I also noticed that I can no longer stop SQL Server on my machine. I
get
> > the below:
> >
> > "An error 5 - (Access is denied.) occured while performing this service
> > operation on the MSSQLServer service."
> >
> > I am assuming this error is part of the same permissions-related
problem.
> > I discovered this problem because I had tried to change SQL Server from
> > Windows Authentication mode to Mixed mode in the system registry as
> > explained in a KB article I found. However, I do not believe I can
change
> > this setting in the registry until I can shut down SQL Server!!!
> >
> >
> > "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
> > wrote in message news:Ono7ZKqzEHA.2936@TK2MSFTNGP10.phx.gbl...
> >> (local), with the parenthesis, not Local. You can also try 127.0.0.1
or
> >> 127.0.0.1,1433.
> >>
> >> If you have ODBC installed (quite probably), you can try creating a DSN
> >> by
> >> using the Data Sources tool in the Administrative Tools section under
the
> >> control panel.
> >>
> >> Finally, what provider are you trying to use in the connection window?
> >>
> >> S. L.
> >>
> >> "MikeC" <anonymous@discussions.microsoft.com> wrote in message
> >> news:P9xnd.19938$zx1.12542@newssvr13.news.prodigy.com...
> >>> Enterprise Manager and VS.NET are not installed on my machine.
> >>>
> >>> The SQL Server name is set to the name of the machine. Should I
change
> >>> it to Local? I hadn't tried that, but in hind sight that makes sense.
> >>> I'll give it a try and post again if the problem persists. Thanks for
> >>> your help.
> >>>
> >>>
> >>> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam
please)>
> >>> wrote in message news:%23vhjrTpzEHA.2624@TK2MSFTNGP11.phx.gbl...
> >>>> Obviously, if you were able to connect to the MSDE engine and now you
> >>>> can't, something must have happened.
> >>>>
> >>>> Have you tried another kind of client, like Enterprise Manager ou
> >>>> VS.NET, to connect to the MSDE database and what is the name of the
> >>>> server that you are using? (for example: the name of the machine,
> >>>> (local), localhost, 127.0.0.1, etc.)
> >>>>
> >>>> S. L.
> >>>>
> >>>> "MikeC" <anonymous@discussions.microsoft.com> wrote in message
> >>>> news:58vnd.19918$zx1.7264@newssvr13.news.prodigy.com...
> >>>>>I must have a default installation.
> >>>>>
> >>>>> Yes, I successfully connected to the database the day that I created
> >>>>> it. I created the tables, relationships and was beginning to enforce
> >>>>> referential integrity. Now I'm trying to connect, and it won't
trust
> >>>>> my login even though that's what I told it to do when I originally
> >>>>> created the database.
> >>>>>
> >>>>> I do have administrator rights on my local machine, but these rights
> >>>>> are external to SQL Server. I don't know what specific rights I
have
> >>>>> within SQL Server. However, as I mentioned above, I did manage to
> >>>>> create the tables and begin enforcing referential integrity.
Usually,
> >>>>> only someone with administrator permissions can do these things. At
> >>>>> the time, I just assumed that I was automatically granted
> >>>>> administrator
> >>>>> rights when I created the database. If this is not the case, then
I'm
> >>>>> puzzled as to why I was allowed to create the database, tables, etc.
> >>>>> in
> >>>>> the first place. Maybe SQL Server was just teasing me. :-)
> >>>>>
> >>>>>
> >>>>> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam
> >>>>> please)>
> >>>>> wrote in message news:%238EZxlozEHA.2936@TK2MSFTNGP10.phx.gbl...
> >>>>>> The fact that you are able to successfully log on to your machine
is
> >>>>>> not necessarily sufficient to get access to the MSDE or SQL-Server.
> >>>>>>
> >>>>>> By default, you must have administrator rights to have access to
the
> >>>>>> server (with a default installation) and even these accounts can be
> >>>>>> kicked off the sql-server.
> >>>>>>
> >>>>>> Have you been able to log on successfully before?
> >>>>>>
> >>>>>> S. L.
> >>>>>>
> >>>>>> "MikeC" <anonymous@discussions.microsoft.com> wrote in message
> >>>>>> news:8Vtnd.23388$6q2.7167@newssvr14.news.prodigy.com...
> >>>>>>>I recently created an ADP project as a front end that connects to a
> >>>>>>>new MSDE 2000 backend. Both files are installed on the same
machine.
> >>>>>>>MSDE 2000 and Access XP are both installed. The project is using
NT
> >>>>>>>Authentication (Trusted Connection). My login authenticates to an
> >>>>>>>Active Directory domain. I don't know whether this detail is
> >>>>>>>relevant.
> >>>>>>>
> >>>>>>> Now I'm trying to connect to the back end from the project file
> >>>>>>> (both
> >>>>>>> on local machine), but I'm having the below problems:
> >>>>>>>
> >>>>>>> 1) The tables and database diagram no longer display in the
> >>>>>>> database
> >>>>>>> window.
> >>>>>>>
> >>>>>>> 2) The title bar at the top of the database window indicates that
> >>>>>>> the project is *disconnected* from the back end.
> >>>>>>>
> >>>>>>> 3) When I run the "Connection" option from the File menu and
click
> >>>>>>> on the "Test Connection" button at the bottom of the "Data Link
> >>>>>>> Properties" dialog box, I get the following error:
> >>>>>>>
> >>>>>>> "Test connection failed because of an error in initializing
> >>>>>>> provider.
> >>>>>>> Login failed for user '[myDomain\MyUserName]'"
> >>>>>>>
> >>>>>>> 4) If I just click on the OK button in the "Data Link Properties"
> >>>>>>> dialog box, I get the following error:
> >>>>>>>
> >>>>>>> "Microsoft Access could not log on to the server. Verify that the
> >>>>>>> log on information is correct."
> >>>>>>>
> >>>>>>> Normally, I would assume the fact that I was able to successfully
> >>>>>>> log
> >>>>>>> on to my machine is sufficient proof that my login info is
correct.
> >>>>>>> For some reason, my new database does not appear to be trusting(?)
> >>>>>>> my
> >>>>>>> Windows 2000 authentication. My password has *not* changed
> >>>>>>> recently.
> >>>>>>>
> >>>>>>> I have also verified that SQL Server is running on my machine and
> >>>>>>> that my machine name has been selected as the SQL Server Name in
the
> >>>>>>> "Data Link Properties" dialog box. "Use Windows NT Integrated
> >>>>>>> security" is also selected. The database is also selected.
> >>>>>>>
> >>>>>>> I have re-started my machine and logged in again, but I still
cannot
> >>>>>>> connect to the MSDE database from the project file.
> >>>>>>>
> >>>>>>> What am I missing?
> >>>>>>>
> >>>>>>>
> >>>>>>> P.S. I'm Xposting in Microsoft.Public.Access.Security and
> >>>>>>> Microsoft.Public.Access.ADP.SQLServer.
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
>
>
- Next message: Arthur: "Re: Permissions problem"
- Previous message: Rick Brandt: "Re: Can not open other Access DBs if joining security workgroup file"
- In reply to: Sylvain Lafontaine: "Re: ADP Project Trusted Connection Issue?"
- Messages sorted by: [ date ] [ thread ]