<rfarley@spyderinternet.com> wrote:

>By the way, when I try to follow the step in the walkthrough to create a
>connection, I get the following error:
>
>[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
>denied.
>
>But it does exist. Why would access be denied? For what it is worth, access
>is denied even if I try to login using specific name and password.
>
>As I found the directions somewhat confusing, there is a real possibility I
>may have installed MSDE wrong. Can someone step me through *exactly* how it
>should be installed to work with Visual Studio 2003?
>
>PLEEEASE someone help the stupid newbie!
>
> / R
>

"Self" <wolfdeveloper@nospam.yahoo.com> wrote in message
news:r6g23092jooer0vtor9s20qlh1gdhbrvr5@4ax.com...
> On Mon, 16 Feb 2004 08:57:44 -0600, "Richard D. Farley"
> <rfarley@spyderinternet.com> wrote:
>
> >By the way, when I try to follow the step in the walkthrough to create a
> >connection, I get the following error:
> >
> >[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or
access
> >denied.
> >
> >But it does exist. Why would access be denied? For what it is worth,
access
> >is denied even if I try to login using specific name and password.
> >
> >As I found the directions somewhat confusing, there is a real possibility
I
> >may have installed MSDE wrong. Can someone step me through *exactly* how
it
> >should be installed to work with Visual Studio 2003?
> >
> >PLEEEASE someone help the stupid newbie!
> >
> > / R
> >
>
> For a quick test :
>
> Try making a UDL file on the desktop you can test connectivity of
> specfic providers installed.
>
> I usually do this for client issues to make it easy to test for
> connectivity.
>
> Make a txt file on the desktop then change the extension to UDL,
> when it prompts are you sure say yes. Note if it doesn't prompt or
> you see an extension you will have to change the Explorer Options ,
> de-check the 'Hide extensions for known types'.
>
> Next switch to the provider tab
> Then select 'Microsoft OLEDB Provider for SQL Server
> Press Next
> On the Connection Tab Enter
> 1) Server name - For this I start with IP (takes DNS out of the
> picture)
> 2) Try 'Use Windows NT Integrated Security'
> 3) Type the DB name
>
> Press "Test Connection"
>
> Now if this much works the server is up and running and MDAC is
> operational and VS.NET should work. Sometimes just doing this test
> has made it 'spontaneously' work at client sites of mine. I am
> looking for a 'why' to this but haven't found one so far.
>
> Next for #2 try the username and password.
>
> If it does not work this may provide a different error.
>
> Make sure the service is started (may seem obvious but it might start
> and then stop if it's configured wrong) after you have booted and the
> disk has stopped whirring.
>
> HTH,
>
> -E.
>
>

<rfarley@spyderinternet.com> wrote:

>I'm still lost. Something works if I enter NAMEOFMYWORKSTATION\VSDOTNET for
>the Server Name, but I am then limited to databases master, model, msdb and
>tempdb and cannot in any way specify the pubs database as suggested in the
>walkthrough.

>And I haven't had any luck with the UDL file, but that may be because you
>did not explain things to the nth degree so a dimmer-than-average 2-year-old
>could understand it.

>Based on Microsofts' specs, I think it is probably right that it should have
>been included, but being such a newbie, I am always at risk of
>misunderstanding nearly everything. Do you know whether a developer license
>copy of SQL Server 2000 should have been included or not?

>And how much would having it likely help me over MSDE?

>Thanks again for your patience.

<wolfdeveloper@nospam.yahoo.com> wrote:

>this assumes you know how to run a query using osql. Are you familiar
>with it at all or have you been able to

"Self" <wolfdeveloper@nospam.yahoo.com> wrote in message
news:43n530paogc0c86b3riudiuu4uq19cl512@4ax.com...
> On Tue, 17 Feb 2004 00:10:22 -0600, "Richard D. Farley"
> <rfarley@spyderinternet.com> wrote:
>
> >I'm still lost. Something works if I enter NAMEOFMYWORKSTATION\VSDOTNET
for
> >the Server Name, but I am then limited to databases master, model, msdb
and
> >tempdb and cannot in any way specify the pubs database as suggested in
the
> >walkthrough.
>
> This would be a named instance.
>
> My guess about the pubs DB most likely also a permissions issue. You
> may not have been granted access to the pubs DB.
>
> To possibly cure this you might try rnning the following SQL:
>
> EXEC sp_grantdbaccess '<machine name or domain>\<your windows user
> name>' , '<login name>'
>
> Example:
>
> EXEC sp_grantdbaccess 'MACHINEA\Mylogin', 'MyLogin'
> GO
>
> this assumes you know how to run a query using osql. Are you faniliar
> with it at all or have you been able to
>
>
>
> On Named Instances see here for more:
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_runsetup_2xmb.asp
>
> ===
>
>
> If your going to install MSSQL Dev edition you can upgrade it or
> remove it.
>
>
> For removal see this tech doc :
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;320873
>
> ===
>
> For upgrade see here this site which has a helpful walkthrough with
> pictures.
>
> http://www.axon.com/mr_Axon_KB_Article.cfm?ArticleID=101
>
> replace the instance name with the VSDOTNET. If you need to run
> sample apps from the net you may also need a 'default instance'
>
> (Hopefully these fine people don't mind me posting the link.)
>
> ===
>
> For more on getting MSDE to work see the following but my advice would
> be to setup MSSQL server Dev edition.
>
> ==
> INFO: MSDE Security and Authentication
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325022
> ==
>
> PRB: Cannot Connect to MSDE 2000 by Using ADO.NET with SQL
> Authentication
>
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;321698
> ==
>
> HOW TO: Connect to Microsoft Desktop Engine :
>
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;319930
> ==
>
> And last but not least SP# can be had here:
>
> http://www.microsoft.com/sql/downloads/2000/sp3.asp
>
> ===
>
> >And I haven't had any luck with the UDL file, but that may be because you
> >did not explain things to the nth degree so a dimmer-than-average
2-year-old
> >could understand it.
>
>
> For the steps I sent in a little more detail see this article:
>
> http://support.microsoft.com/default.aspx?scid=kb;[LN];264691
>
> In step #2 of the article substitute :
>
> Microsoft OLE DB Provider for SQL Server
>
> for :
>
> Microsoft Jet 4.0 OLE DB Provider
>
> For Server since you have a named instance you would need to enter
>
> MACHINENAME\VSDOTNET
>
> For the database name use PUBS (since you want to connect to it)
>
> Also make sure the Tab 1 (Provider) of the UDL wizard is set or you
> will not see the correct screen on Tab Page 2 of the UDL wizard.
>
> It defaults to ODBC and not the MS SQL provider which is what I
> explained.
>
>
> >Based on Microsofts' specs, I think it is probably right that it should
have
> >been included, but being such a newbie, I am always at risk of
> >misunderstanding nearly everything. Do you know whether a developer
license
> >copy of SQL Server 2000 should have been included or not?
>
> Yes it is includeed and would be in the orange box (.NET Servers Disk
> if you did not get CD's which is what I have).
>
> >And how much would having it likely help me over MSDE?
>
> A lot. The SQL Server will include the client tools and the
> enterprise manager which make the management of the DB much easier
> than on MSDE with osql command line(IMHO anyway).
>
>
> >Thanks again for your patience.
>
> Your welcome.
>
> If your still having issues after this post back and let me know any
> errors you have gotten.
>
> Think this should cover most of the issues I have run into with
> MSDE/MSSQL setup/upgrade in the past.
>
>
> Again hop the helps you et up and running.
>
> HTH,
>
> - E
>

"Richard D. Farley" <rfarley@spyderinternet.com> wrote in message
news:u7rwwpA9DHA.2316@TK2MSFTNGP09.phx.gbl...
> Am using Visual Studio 2003 and Windows XP Pro. In the 'Walkthroughs'
book,
> on page 22, when making a Data Connection, it states in step 4 to 'Use
> Windows NT Integrated security' and says in a note below to see your
network
> administrator if you do not have integrated security set up on your
system.
>
> What is this about? I have so far been unable to make sense of it. I found
> the following link:
>
>
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskaccessingsqlserverusingwindowsintegratedsecurity.asp
>
> But I can't follow the 'Configuring SQL Server' instructions, as there is
no
> entry anywhere for 'Microsoft SQL Server' when I click on Start. Maybe it
is
> because I am not using the full version, but the limited 'MSDE for Visual
> Studio Net' desktop version?
>
> Of course that's just a guess and probably a bad one. I'm such a newbie, I
> haven't really got a clue.
>
> Please help. Thanks.
>
> / r
>
>
> --
> "Do you have blacks too?"
> --George W. Bush to Brazil's President Fernando Henrique Cardoso, March
2001
> (As reported in an April 28, 2002, Estado Sao Pauloan column by Fernando
> Pedreira, a close friend of President Cardoso)
>
>
>
>