Frustrating: Can't get to Provider Options in SQL 2005 Express?

Hi,
I'm trying to get to the provider options screen in SQL2K5 Management
Studio, however I am unable to find it anywhere. This is really
frustrating... Here is what I am trying to do:
1.. In SQL Mgmt Studio, connect to the SQL Server Database Engine and go
to Server Objects->Linked Server->Providers in the Object Explorer.
2.. Right-click on a provider and select Properties.
However, all I can see when I right-click is "Refresh" ... How can I access
the provider options? Is this a limitation of the Express database? Is there
a stored proc I can use?
Thanks,
MichaelWhat are you trying to achieve?
Look at the sp_addlinkedserver system procedure.
"Thou shall lear to type. Clicking is the work of the Devil."
-- undisclosed apostle
;)
ML
http://milambda.blogspot.com/|||Thanks, but I have already used sp_addlinkedserver.
I am trying to set the "allow inprocess" provider options... according to
research in the NG's and BOL (see "Linked Server Properties (Provider
Options Page)"), this is set from a dialog that I am unable to access. I
can't see it when adding a new linked server, editing an existing one, or
right-clicking on the provider in Management Studio.
Any ideas?
Thanks,
Mike
"ML" <ML@.discussions.microsoft.com> wrote in message
news:99625079-C5D6-430C-89AB-8AD8421A2731@.microsoft.com...
> What are you trying to achieve?
> Look at the sp_addlinkedserver system procedure.
> "Thou shall lear to type. Clicking is the work of the Devil."
> -- undisclosed apostle
> ;)
>
> ML
> --
> http://milambda.blogspot.com/sql

Frustrating: Can't get to Provider Options in SQL 2005 Express?

Hi,
I'm trying to get to the provider options screen in SQL2K5 Management
Studio, however I am unable to find it anywhere. This is really
frustrating... Here is what I am trying to do:
1.. In SQL Mgmt Studio, connect to the SQL Server Database Engine and go
to Server Objects->Linked Server->Providers in the Object Explorer.
2.. Right-click on a provider and select Properties.
However, all I can see when I right-click is "Refresh" ... How can I access
the provider options? Is this a limitation of the Express database? Is there
a stored proc I can use?
Thanks,
MichaelWhat are you trying to achieve?
Look at the sp_addlinkedserver system procedure.
"Thou shall lear to type. Clicking is the work of the Devil."
-- undisclosed apostle
;)
ML
--
http://milambda.blogspot.com/|||Thanks, but I have already used sp_addlinkedserver.
I am trying to set the "allow inprocess" provider options... according to
research in the NG's and BOL (see "Linked Server Properties (Provider
Options Page)"), this is set from a dialog that I am unable to access. I
can't see it when adding a new linked server, editing an existing one, or
right-clicking on the provider in Management Studio.
Any ideas?
Thanks,
Mike
"ML" <ML@.discussions.microsoft.com> wrote in message
news:99625079-C5D6-430C-89AB-8AD8421A2731@.microsoft.com...
> What are you trying to achieve?
> Look at the sp_addlinkedserver system procedure.
> "Thou shall lear to type. Clicking is the work of the Devil."
> -- undisclosed apostle
> ;)
>
> ML
> --
> http://milambda.blogspot.com/|||Try setting the rest of provider settings through the @.provstr parameter of
the sp_addlinkedserver.
Some examples are available in Books Online.
ML
--
http://milambda.blogspot.com/|||Thanks. After doing some more research, I now know that this is a limitation
of SQL Server Express.
I was however able to use the following system stored procedure to change
the provider options:
EXEC master.dbo.sp_MSset_oledb_prop N'ProviderName', N'AllowInProcess', 1
I hope this can help someone else.
Thanks,
Mike
"ML" <ML@.discussions.microsoft.com> wrote in message
news:1CF1915F-6D1B-443F-B674-7C51B3139B79@.microsoft.com...
> Try setting the rest of provider settings through the @.provstr parameter
> of
> the sp_addlinkedserver.
> Some examples are available in Books Online.
>
> ML
> --
> http://milambda.blogspot.com/|||This is very helpful and good to know. Do you have a blog? Where have you
found the solution?
ML
--
http://milambda.blogspot.com/|||Hi,
Cindy Winegarden answered in microsoft.public.sqlserver.programming, when I
asked for the same problem (25/05/2006)
--
Michel Lévy
Communauté Francophone des Professionnels FoxPro
Pour un développement durable...
http://www.atoutfox.org
--
"ML" <ML@.discussions.microsoft.com> a écrit dans le message de news:
0BAB0C0C-0151-462E-94B0-9686347E430D@.microsoft.com...
> This is very helpful and good to know. Do you have a blog? Where have you
> found the solution?
>
> ML
> --
> http://milambda.blogspot.com/

Frustrating: Can't get to Provider Options in SQL 2005 Express?

What are you trying to achieve?
Look at the sp_addlinkedserver system procedure.
"Thou shall lear to type. Clicking is the work of the Devil."
-- undisclosed apostle
;)
ML
http://milambda.blogspot.com/Thanks, but I have already used sp_addlinkedserver.
I am trying to set the "allow inprocess" provider options... according to
research in the NG's and BOL (see "Linked Server Properties (Provider
Options Page)"), this is set from a dialog that I am unable to access. I
can't see it when adding a new linked server, editing an existing one, or
right-clicking on the provider in Management Studio.
Any ideas?
Thanks,
Mike
"ML" <ML@.discussions.microsoft.com> wrote in message
news:99625079-C5D6-430C-89AB-8AD8421A2731@.microsoft.com...
> What are you trying to achieve?
> Look at the sp_addlinkedserver system procedure.
> "Thou shall lear to type. Clicking is the work of the Devil."
> -- undisclosed apostle
> ;)
>
> ML
> --
> http://milambda.blogspot.com/|||Hi,
I'm trying to get to the provider options screen in SQL2K5 Management
Studio, however I am unable to find it anywhere. This is really
frustrating... Here is what I am trying to do:
1.. In SQL Mgmt Studio, connect to the SQL Server Database Engine and go
to Server Objects->Linked Server->Providers in the Object Explorer.
2.. Right-click on a provider and select Properties.
However, all I can see when I right-click is "Refresh" ... How can I access
the provider options? Is this a limitation of the Express database? Is there
a stored proc I can use?
Thanks,
Michael|||What are you trying to achieve?
Look at the sp_addlinkedserver system procedure.
"Thou shall lear to type. Clicking is the work of the Devil."
-- undisclosed apostle
;)
ML
http://milambda.blogspot.com/|||Thanks, but I have already used sp_addlinkedserver.
I am trying to set the "allow inprocess" provider options... according to
research in the NG's and BOL (see "Linked Server Properties (Provider
Options Page)"), this is set from a dialog that I am unable to access. I
can't see it when adding a new linked server, editing an existing one, or
right-clicking on the provider in Management Studio.
Any ideas?
Thanks,
Mike
"ML" <ML@.discussions.microsoft.com> wrote in message
news:99625079-C5D6-430C-89AB-8AD8421A2731@.microsoft.com...
> What are you trying to achieve?
> Look at the sp_addlinkedserver system procedure.
> "Thou shall lear to type. Clicking is the work of the Devil."
> -- undisclosed apostle
> ;)
>
> ML
> --
> http://milambda.blogspot.com/

Frustrating: Can't get to Provider Options in SQL 2005 Express

Try setting the rest of provider settings through the @.provstr parameter of
the sp_addlinkedserver.
Some examples are available in Books Online.
ML
http://milambda.blogspot.com/Thanks. After doing some more research, I now know that this is a limitation
of SQL Server Express.
I was however able to use the following system stored procedure to change
the provider options:
EXEC master.dbo.sp_MSset_oledb_prop N'ProviderName', N'AllowInProcess', 1
I hope this can help someone else.
Thanks,
Mike
"ML" <ML@.discussions.microsoft.com> wrote in message
news:1CF1915F-6D1B-443F-B674-7C51B3139B79@.microsoft.com...
> Try setting the rest of provider settings through the @.provstr parameter
> of
> the sp_addlinkedserver.
> Some examples are available in Books Online.
>
> ML
> --
> http://milambda.blogspot.com/|||This is very helpful and good to know. Do you have a blog? Where have you
found the solution?
ML
http://milambda.blogspot.com/|||Hi,
Cindy Winegarden answered in microsoft.public.sqlserver.programming, when I
asked for the same problem (25/05/2006)
Michel Lvy
Communaut Francophone des Professionnels FoxPro
Pour un dveloppement durable...
http://www.atoutfox.org
--
"ML" <ML@.discussions.microsoft.com> a crit dans le message de news:
0BAB0C0C-0151-462E-94B0-9686347E430D@.microsoft.com...
> This is very helpful and good to know. Do you have a blog? Where have you
> found the solution?
>
> ML
> --
> http://milambda.blogspot.com/

Frustrating Authentication Errors

I have a prospective client evaluating our software that uses a SQL backend
and we're struggling with some errors I can't recreate here in our lab.
When he logs into his laptop and tried to access the SQL db, he get's this
error:
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection"
However, when he or the SQL admin log into the SQL admin's PC both can
access the SQL db just fine.
This error only happens on the tester's PC. He even re-imaged the PC and it
still fails. He's running WinXP.
They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD and
SQL authentication. In this case they have created users for him in both AD
and SQL for this db.
Suggestions?
make named pipes the priority on the clients.
"smutny" <smutny@.discussions.microsoft.com> wrote in message
news:780B2EEF-7C85-4DCE-854B-25F4409DE61F@.microsoft.com...
>I have a prospective client evaluating our software that uses a SQL backend
> and we're struggling with some errors I can't recreate here in our lab.
> When he logs into his laptop and tried to access the SQL db, he get's this
> error:
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
> However, when he or the SQL admin log into the SQL admin's PC both can
> access the SQL db just fine.
> This error only happens on the tester's PC. He even re-imaged the PC and
> it
> still fails. He's running WinXP.
> They are running SQL 2000 on a Windows Server 2003 box. Use a mix of AD
> and
> SQL authentication. In this case they have created users for him in both
> AD
> and SQL for this db.
> Suggestions?

Frustrated with two clients that can't connect...

I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev
"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?

> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.

Frustrated with two clients that can't connect...

I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?

> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.

Frustrated with two clients that can't connect...

I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.