Hi!
I have installed MSDE 2000 in "Mixed Windows and SQL mode authentication with network access" .following is the command:
setup.exe DISABLENETWORKPROTOCOLS=0 SAPWD="password" INSTANCENAME="TempInstance" SECURITYMODE=SQL
Then I created the database TempDB in it.
When I try to connect this database from my program running on my machine , it works fine. But when i try to connect to it from the same program running on a different machine on the same domain.It gives error:
"SQL Server does not exist or access denied ."
Even when i run the same program in my machine to access the same TempDB database on a remote machine that is not in my domain, it works fine.
this is my connection string:
Data Source={Database server's IP Address}\TempInstance;Initial Catalog=TempDB;User ID=sa;PWD=password;
Please help.
KT.What's the operating system for the client from which you are unsuccessfully attempting to connect? What version of MDAC is running on it?
Also, be aware that a named instance install of MSDE will set up to run on a non-default port (ie, not 1433). You can verify your connectivity by determining what port the SQL listener is running on and then using telnet {ip address} {port} from your client machine. You may need to account for the alternate port on your client machine. You can set up an alias for it by running cliconfg at a command prompt on your client machine.
Regards,
hmscott|||Thanks hmscott!
Actually my problem was caused by windows firewall.
regards.
Kuldeep.
Showing posts with label network. Show all posts
Showing posts with label network. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Problem in accessing reporting services web service, unable to set credentials I guess....
I am trying to access the Reporting Services Web Service, but i m not able to make it work. i tried with default credentials and network credentials
Tried to solve this and found that its the problem with the datasource I created for the report, tried to use 'sa' user in
ReportingService
service =newReportingService();service.Credentials =new System.Net.NetworkCredential("dbo","coreobject5","");
service.CreateSubscription(report, extSettings, description, eventType, matchData, parameters);
This is the exception i get
The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. --> The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database.Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:System.Web.Services.Protocols.SoapException: The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. --> The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database.
Source Error:
Line 3382: [return: System.Xml.Serialization.XmlElementAttribute("SubscriptionID")]Line 3383: public string CreateSubscription(string Report, ExtensionSettings ExtensionSettings, string Description, string EventType, string MatchData, ParameterValue[] Parameters) {Line 3384: object[] results = this.Invoke("CreateSubscription", new object[] {Line 3385: Report,Line 3386: ExtensionSettings,Tried to solve this and found that its the problem with the datasource I created for the report, tried to use 'sa' user in
data source->credentials->Use a specified user name and password, but did'nt worked.
One more thing i am able to accessGetExtensionSettings("Report Server Fileshare");API with
service.Credentials = System.Net.CredentialCache.DefaultCredentials;
Not able to find out what users to create in Report Server database or the database i am connecting to?
Will appreciate any kind of help.
Problem in accessing reporting services web service, unable to set credentials I guess....
I am trying to access the Reporting Services Web Service, but i m not able to make it work. i tried with default credentials and network credentials
ReportingService service = new ReportingService();
service.Credentials = new System.Net.NetworkCredential("username", "password", "domain");
service.CreateSubscription(report, extSettings, description, eventType, matchData, parameters);
This is the exception i get
The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. > The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Services.Protocols.SoapException: The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. > The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database.
Source Error:
Line 3382: [return: System.Xml.Serialization.XmlElementAttribute("SubscriptionID")] |
Tried to solve this and found that its the problem with the datasource I created for the report, tried to use 'sa' user in
data source->credentials->Use a specified user name and password, but did'nt worked.
Onemore thing i am able to access GetExtensionSettings("Report Server Fileshare"); API with
service.Credentials = System.Net.CredentialCache.DefaultCredentials;
Not able to find out what users to create in Report Server database or the database i am connecting to?
Will appreciate any kind of help.
|||
I believe your problem does not lie with a user in a database; I have used RS WS to Create / Fire Subscriptions and to UpdateSnapshots. Whatever user you pass to the Web Service must have Generate Events permission under Site Settings. Give the user those permissions and I think you will find that it will resolve your problem
Please let me know
Thanks
|||Report's data source must use stored credentials.sqlProblem in accessing reporting services web service, unable to set credentials I guess....
I am trying to access the Reporting Services Web Service, but i m not able to make it work. i tried with default credentials and network credentials
ReportingService service = new ReportingService();
service.Credentials = new System.Net.NetworkCredential("username", "password", "domain");
service.CreateSubscription(report, extSettings, description, eventType, matchData, parameters);
This is the exception i get
The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. > The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database.Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Web.Services.Protocols.SoapException: The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database. > The current action cannot be completed because the user data source credentials that are required to execute this report are not stored in the report server database.
Source Error:
Line 3382: [return: System.Xml.Serialization.XmlElementAttribute("SubscriptionID")] |
Tried to solve this and found that its the problem with the datasource I created for the report, tried to use 'sa' user in
data source->credentials->Use a specified user name and password, but did'nt worked.
Onemore thing i am able to access GetExtensionSettings("Report Server Fileshare"); API with
service.Credentials = System.Net.CredentialCache.DefaultCredentials;
Not able to find out what users to create in Report Server database or the database i am connecting to?
Will appreciate any kind of help.
|||
I believe your problem does not lie with a user in a database; I have used RS WS to Create / Fire Subscriptions and to UpdateSnapshots. Whatever user you pass to the Web Service must have Generate Events permission under Site Settings. Give the user those permissions and I think you will find that it will resolve your problem
Please let me know
Thanks
|||Report's data source must use stored credentials.Problem in " NT AUTHORITY\NETWORK SERVICE "
I just install a sql2k and csk
After all installation , This message occurs when I start the csk
What is 'NT AUTHORITY\NETWORK SERVICE' ?
How can I solve this problem please?
After all installation , This message occurs when I start the csk
What is 'NT AUTHORITY\NETWORK SERVICE' ?
How can I solve this problem please?
'/CommunityStarterKit' ?????
------------------------
? 'NT AUTHORITY\NETWORK SERVICE' ??
??: ??? Web ????????????,?????
??: System.Data.SqlClient.SqlException: ? 'NT AUTHORITY\NETWORK SERVICE' ??
??:
??? Web ??,??????????,??????
??:
[SqlException: ? 'NT AUTHORITY\NETWORK SERVICE' ??]
System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +472
System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372
System.Data.SqlClient.SqlConnection.Open() +384
System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44
System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +38
ASPNET.StarterKit.Communities.CommunityUtility.GetAllCommunitiesFromDB() +92
ASPNET.StarterKit.Communities.CommunityUtility.GetAllCommunities() +56
ASPNET.StarterKit.Communities.CommunityUtility.GetCommunityInfo() +332
ASPNET.StarterKit.Communities.CommunitiesModule.Application_BeginRequest(Object source, EventArgs e) +204
System.Web.SyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +60
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +87
------------------------
??: Microsoft .NET Framework ??:1.1.4322.573; ASP.NET ??:1.1.4322.573see thread "Connecting to MSDE using SSPI". Looks like you have hit the same problem as I did.
John B
Friday, March 9, 2012
problem creating view on table from linked server DB using IP
>>create a simply-named alias using Client Network Utility
This sounds like a great idea. May I ask where I locate the Client Network
Utility and how to create the simply-named alias?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Another thing to reduce the complexity here, of having IP addresses
> hard-coded into your query, is to create a simply-named alias using Client
> Network Utility, and then refer to the alias instead of the IP address. N
ot
> that this makes it okay to use the view designer, but I think it is a bett
er
> approach overall. In addition to alleviating problems with 4-dot naming,
it
> also makes it much easier to update the system should that IP address
> change - you just change the alias definition instead of all the places yo
u
> manually referred to it in code.
>
>> This sounds like a great idea. May I ask where I locate the Client
> Network
> Utility
Start > Programs > Microsoft SQL Server >|||Thank you. So I went to the utility. I clicked on the Alias tab. Then I
clicked Add. In the Server alias box I entered the alias name which was
simultaneously showing up in the Connection Parameters Server Name. I
changed that to the IP address of the remote server. Then I selected TCP/IP
in the Network Libaries and clicked OK.
In the Linked Server (from Enterprise Manager), I added the Aliased remote
server using the same context as the link using the IP address. I was not
able to link to the Alias server. Do I need to remove the linked server tha
t
is using the IP address first? I am a little afraid of doing that because
I
already have my client app (VB.Net) working and can retrieve data from the
views (which use the IP address of the remote server).
Well, if anything, it is an interesting exercise.
Thanks for the help.
Rich
"Aaron Bertrand [SQL Server MVP]" wrote:
> Start > Programs > Microsoft SQL Server >
>
>|||Server alias: should be "myserver"
Server name: should "a.b.c.d"
When you add the linked server, use the name "myserver"
What does "not able to" mean? Did you get an error message? If so, what
was it?
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:B2E4C610-E3DB-4229-93BD-D0B277868000@.microsoft.com...
> Thank you. So I went to the utility. I clicked on the Alias tab. Then I
> clicked Add. In the Server alias box I entered the alias name which was
> simultaneously showing up in the Connection Parameters Server Name. I
> changed that to the IP address of the remote server. Then I selected
> TCP/IP
> in the Network Libaries and clicked OK.
> In the Linked Server (from Enterprise Manager), I added the Aliased remote
> server using the same context as the link using the IP address. I was not
> able to link to the Alias server. Do I need to remove the linked server
> that
> is using the IP address first? I am a little afraid of doing that
> because I
> already have my client app (VB.Net) working and can retrieve data from the
> views (which use the IP address of the remote server).
> Well, if anything, it is an interesting exercise.
> Thanks for the help.
> Rich
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>|||When I add the Aliased server I use the Alias name "myServer"
I use the same security context as the original linked server - the UID,
impersonate, and the password, then apply. The new linked server shows up i
n
Enterprise manager, but when I click on tables - about 30 seconds later I ge
t
the error message that either the server "myServer" does not exist or Access
denied. In Query analyzer I try select * from myserver.remotedb.dbo.table1
I get the error message the same error message
"Server does not exist or Access denied"
when I look in sysservers, however
Use Master
select * from sysservers
I can see "myServer" in the list of servers. My question now is if the
Alias is correct - correctly referring to my remote server, and am I using
the correct security context.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Server alias: should be "myserver"
> Server name: should "a.b.c.d"
> When you add the linked server, use the name "myserver"
> What does "not able to" mean? Did you get an error message? If so, what
> was it?
>
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:B2E4C610-E3DB-4229-93BD-D0B277868000@.microsoft.com...
>
>|||Not sure, but you may have to restart the SQL Server service for the alias
to be picked up and routable? Also, have you tried any other authentication
methods (e.g. not defining a local login and checking "be made using this
security context" and putting the remote uid/password in that dialog)?
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:CC0FF896-33EF-4F9E-B881-1867D785255C@.microsoft.com...
> When I add the Aliased server I use the Alias name "myServer"
> I use the same security context as the original linked server - the UID,
> impersonate, and the password, then apply. The new linked server shows up
> in
> Enterprise manager, but when I click on tables - about 30 seconds later I
> get
> the error message that either the server "myServer" does not exist or
> Access
> denied. In Query analyzer I try select * from
> myserver.remotedb.dbo.table1
> I get the error message the same error message
> "Server does not exist or Access denied"
> when I look in sysservers, however
> Use Master
> select * from sysservers
> I can see "myServer" in the list of servers. My question now is if the
> Alias is correct - correctly referring to my remote server, and am I using
> the correct security context.
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
This sounds like a great idea. May I ask where I locate the Client Network
Utility and how to create the simply-named alias?
"Aaron Bertrand [SQL Server MVP]" wrote:
> Another thing to reduce the complexity here, of having IP addresses
> hard-coded into your query, is to create a simply-named alias using Client
> Network Utility, and then refer to the alias instead of the IP address. N
ot
> that this makes it okay to use the view designer, but I think it is a bett
er
> approach overall. In addition to alleviating problems with 4-dot naming,
it
> also makes it much easier to update the system should that IP address
> change - you just change the alias definition instead of all the places yo
u
> manually referred to it in code.
>
>> This sounds like a great idea. May I ask where I locate the Client
> Network
> Utility
Start > Programs > Microsoft SQL Server >|||Thank you. So I went to the utility. I clicked on the Alias tab. Then I
clicked Add. In the Server alias box I entered the alias name which was
simultaneously showing up in the Connection Parameters Server Name. I
changed that to the IP address of the remote server. Then I selected TCP/IP
in the Network Libaries and clicked OK.
In the Linked Server (from Enterprise Manager), I added the Aliased remote
server using the same context as the link using the IP address. I was not
able to link to the Alias server. Do I need to remove the linked server tha
t
is using the IP address first? I am a little afraid of doing that because
I
already have my client app (VB.Net) working and can retrieve data from the
views (which use the IP address of the remote server).
Well, if anything, it is an interesting exercise.
Thanks for the help.
Rich
"Aaron Bertrand [SQL Server MVP]" wrote:
> Start > Programs > Microsoft SQL Server >
>
>|||Server alias: should be "myserver"
Server name: should "a.b.c.d"
When you add the linked server, use the name "myserver"
What does "not able to" mean? Did you get an error message? If so, what
was it?
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:B2E4C610-E3DB-4229-93BD-D0B277868000@.microsoft.com...
> Thank you. So I went to the utility. I clicked on the Alias tab. Then I
> clicked Add. In the Server alias box I entered the alias name which was
> simultaneously showing up in the Connection Parameters Server Name. I
> changed that to the IP address of the remote server. Then I selected
> TCP/IP
> in the Network Libaries and clicked OK.
> In the Linked Server (from Enterprise Manager), I added the Aliased remote
> server using the same context as the link using the IP address. I was not
> able to link to the Alias server. Do I need to remove the linked server
> that
> is using the IP address first? I am a little afraid of doing that
> because I
> already have my client app (VB.Net) working and can retrieve data from the
> views (which use the IP address of the remote server).
> Well, if anything, it is an interesting exercise.
> Thanks for the help.
> Rich
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>|||When I add the Aliased server I use the Alias name "myServer"
I use the same security context as the original linked server - the UID,
impersonate, and the password, then apply. The new linked server shows up i
n
Enterprise manager, but when I click on tables - about 30 seconds later I ge
t
the error message that either the server "myServer" does not exist or Access
denied. In Query analyzer I try select * from myserver.remotedb.dbo.table1
I get the error message the same error message
"Server does not exist or Access denied"
when I look in sysservers, however
Use Master
select * from sysservers
I can see "myServer" in the list of servers. My question now is if the
Alias is correct - correctly referring to my remote server, and am I using
the correct security context.
"Aaron Bertrand [SQL Server MVP]" wrote:
> Server alias: should be "myserver"
> Server name: should "a.b.c.d"
> When you add the linked server, use the name "myserver"
> What does "not able to" mean? Did you get an error message? If so, what
> was it?
>
>
> "Rich" <Rich@.discussions.microsoft.com> wrote in message
> news:B2E4C610-E3DB-4229-93BD-D0B277868000@.microsoft.com...
>
>|||Not sure, but you may have to restart the SQL Server service for the alias
to be picked up and routable? Also, have you tried any other authentication
methods (e.g. not defining a local login and checking "be made using this
security context" and putting the remote uid/password in that dialog)?
"Rich" <Rich@.discussions.microsoft.com> wrote in message
news:CC0FF896-33EF-4F9E-B881-1867D785255C@.microsoft.com...
> When I add the Aliased server I use the Alias name "myServer"
> I use the same security context as the original linked server - the UID,
> impersonate, and the password, then apply. The new linked server shows up
> in
> Enterprise manager, but when I click on tables - about 30 seconds later I
> get
> the error message that either the server "myServer" does not exist or
> Access
> denied. In Query analyzer I try select * from
> myserver.remotedb.dbo.table1
> I get the error message the same error message
> "Server does not exist or Access denied"
> when I look in sysservers, however
> Use Master
> select * from sysservers
> I can see "myServer" in the list of servers. My question now is if the
> Alias is correct - correctly referring to my remote server, and am I using
> the correct security context.
>
> "Aaron Bertrand [SQL Server MVP]" wrote:
>
Monday, February 20, 2012
Problem connection to SQL Server with ODBC
What protocols are being used by the client and what is the
server listening on?
Are the client network utilities on the clients having the
connectivity problems?
Are you using an alias for the connection?
What version of MDAC on the clients?
From your description, it sounds like the app tries to
connect twice (which is fine) but that it's just not hitting
the right protocols. You can find information on how a
client runs through the protocols trying to connect in this
article:
INF: SQL Server Clients May Change Protocols When They Try
to Connect
http://support.microsoft.com/?id=328383
You can also find some general troubleshooting for the error
at:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On Tue, 6 Apr 2004 10:12:37 +0100, "Ian Spanswick"
<ian.spanswick@.eps-hq.co.uk> wrote:
>Hi,
>Getting very frustrated by the following problem, using SQL Server 2000 (inc
>SP3a), using an application that connects to a DB via ODBC and the following
>error message comes up:
>Connection failed:
>SQLSTATE: '01000'
>SQL Server Error: 1703
>[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error:17
>[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist
>or access denied
>When setting up the DSN the test works fine as does query analyzer, pretty
>sure it's not the application I'm using as the SQL server connection window
>that comes up after the initial error (above) gives the same error message.
>Any ideas? Help is definitely needed before I tear my hair out!
>Thanks
>Ian
>
Thanks for the links, studying them now but have moved my database to
another server and things are going better! Still want to get to the bottom
of the problem.
Ian
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:i3i670lutthh68l5mqlgn479ng66ornom3@.4ax.com...
> What protocols are being used by the client and what is the
> server listening on?
> Are the client network utilities on the clients having the
> connectivity problems?
> Are you using an alias for the connection?
> What version of MDAC on the clients?
> From your description, it sounds like the app tries to
> connect twice (which is fine) but that it's just not hitting
> the right protocols. You can find information on how a
> client runs through the protocols trying to connect in this
> article:
> INF: SQL Server Clients May Change Protocols When They Try
> to Connect
> http://support.microsoft.com/?id=328383
> You can also find some general troubleshooting for the error
> at:
> INF: Potential Causes of the "SQL Server Does Not Exist or
> Access Denied" Error Message
> http://support.microsoft.com/?id=328306
> -Sue
> On Tue, 6 Apr 2004 10:12:37 +0100, "Ian Spanswick"
> <ian.spanswick@.eps-hq.co.uk> wrote:
(inc
following
exist
pretty
window
message.
>
server listening on?
Are the client network utilities on the clients having the
connectivity problems?
Are you using an alias for the connection?
What version of MDAC on the clients?
From your description, it sounds like the app tries to
connect twice (which is fine) but that it's just not hitting
the right protocols. You can find information on how a
client runs through the protocols trying to connect in this
article:
INF: SQL Server Clients May Change Protocols When They Try
to Connect
http://support.microsoft.com/?id=328383
You can also find some general troubleshooting for the error
at:
INF: Potential Causes of the "SQL Server Does Not Exist or
Access Denied" Error Message
http://support.microsoft.com/?id=328306
-Sue
On Tue, 6 Apr 2004 10:12:37 +0100, "Ian Spanswick"
<ian.spanswick@.eps-hq.co.uk> wrote:
>Hi,
>Getting very frustrated by the following problem, using SQL Server 2000 (inc
>SP3a), using an application that connects to a DB via ODBC and the following
>error message comes up:
>Connection failed:
>SQLSTATE: '01000'
>SQL Server Error: 1703
>[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen
>(Connect()).
>Connection failed:
>SQLState: '08001'
>SQL Server Error:17
>[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist
>or access denied
>When setting up the DSN the test works fine as does query analyzer, pretty
>sure it's not the application I'm using as the SQL server connection window
>that comes up after the initial error (above) gives the same error message.
>Any ideas? Help is definitely needed before I tear my hair out!
>Thanks
>Ian
>
Thanks for the links, studying them now but have moved my database to
another server and things are going better! Still want to get to the bottom
of the problem.
Ian
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:i3i670lutthh68l5mqlgn479ng66ornom3@.4ax.com...
> What protocols are being used by the client and what is the
> server listening on?
> Are the client network utilities on the clients having the
> connectivity problems?
> Are you using an alias for the connection?
> What version of MDAC on the clients?
> From your description, it sounds like the app tries to
> connect twice (which is fine) but that it's just not hitting
> the right protocols. You can find information on how a
> client runs through the protocols trying to connect in this
> article:
> INF: SQL Server Clients May Change Protocols When They Try
> to Connect
> http://support.microsoft.com/?id=328383
> You can also find some general troubleshooting for the error
> at:
> INF: Potential Causes of the "SQL Server Does Not Exist or
> Access Denied" Error Message
> http://support.microsoft.com/?id=328306
> -Sue
> On Tue, 6 Apr 2004 10:12:37 +0100, "Ian Spanswick"
> <ian.spanswick@.eps-hq.co.uk> wrote:
(inc
following
exist
pretty
window
message.
>
Problem connecting to SQL Server over the internet
I have opened ports 1433 and 1434 on a SQL Server on our network to allow
our customers to receive a monthly subscription "key" for the software they
lease from us. Within an encrypted Stored Procedure I am using the
OPENDATASOURCE method with a connect string containing our IP address. It is
working on 90% of the sites. However some of the sites are receiving an
error:
Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
Line 37
SQL Server does not exist or access denied.
On most of the servers where the procedure is WORKING, a peek at the
firewall configuration using Shields-Up service from Gibson Research shows
that ports 1433 and 1434 are in Stealth mode. But, as I said, the connection
is still operating just fine. All sites, including the ones that don't work,
have the TCP/IP protocol enabled in the Client Network Utility on Port 1433.
So I am at a loss to figure out why the Internet connection is not working
at some sites. Any ideas?
Also, is there another way that I can distribute the "key" without user
intervention using "back-end" programs or procedures? Is there a way to
connect and retieve data via port 80 which is usually left open for outbound
requests? Thanks in advance...
I would make network traces at the problem site and either review the
firewall logs or
make simulataneous traces on the server. This sounds like a tcp issue not
a SQL issue.
Verify that the 3 way tcp handshake is completing. The login packet isn't
sent until this completes.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thank you both for your replies. I will make sure that the TCP issues are
resolved at the client sites before looking any further.
"John Kotuby" <jkotuby@.snet.net> wrote in message
news:undiWF%23TEHA.2028@.TK2MSFTNGP11.phx.gbl...
> I have opened ports 1433 and 1434 on a SQL Server on our network to allow
> our customers to receive a monthly subscription "key" for the software
they
> lease from us. Within an encrypted Stored Procedure I am using the
> OPENDATASOURCE method with a connect string containing our IP address. It
is
> working on 90% of the sites. However some of the sites are receiving an
> error:
> Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
> Line 37
> SQL Server does not exist or access denied.
> On most of the servers where the procedure is WORKING, a peek at the
> firewall configuration using Shields-Up service from Gibson Research shows
> that ports 1433 and 1434 are in Stealth mode. But, as I said, the
connection
> is still operating just fine. All sites, including the ones that don't
work,
> have the TCP/IP protocol enabled in the Client Network Utility on Port
1433.
> So I am at a loss to figure out why the Internet connection is not working
> at some sites. Any ideas?
> Also, is there another way that I can distribute the "key" without user
> intervention using "back-end" programs or procedures? Is there a way to
> connect and retieve data via port 80 which is usually left open for
outbound
> requests? Thanks in advance...
>
our customers to receive a monthly subscription "key" for the software they
lease from us. Within an encrypted Stored Procedure I am using the
OPENDATASOURCE method with a connect string containing our IP address. It is
working on 90% of the sites. However some of the sites are receiving an
error:
Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
Line 37
SQL Server does not exist or access denied.
On most of the servers where the procedure is WORKING, a peek at the
firewall configuration using Shields-Up service from Gibson Research shows
that ports 1433 and 1434 are in Stealth mode. But, as I said, the connection
is still operating just fine. All sites, including the ones that don't work,
have the TCP/IP protocol enabled in the Client Network Utility on Port 1433.
So I am at a loss to figure out why the Internet connection is not working
at some sites. Any ideas?
Also, is there another way that I can distribute the "key" without user
intervention using "back-end" programs or procedures? Is there a way to
connect and retieve data via port 80 which is usually left open for outbound
requests? Thanks in advance...
I would make network traces at the problem site and either review the
firewall logs or
make simulataneous traces on the server. This sounds like a tcp issue not
a SQL issue.
Verify that the 3 way tcp handshake is completing. The login packet isn't
sent until this completes.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Thank you both for your replies. I will make sure that the TCP issues are
resolved at the client sites before looking any further.
"John Kotuby" <jkotuby@.snet.net> wrote in message
news:undiWF%23TEHA.2028@.TK2MSFTNGP11.phx.gbl...
> I have opened ports 1433 and 1434 on a SQL Server on our network to allow
> our customers to receive a monthly subscription "key" for the software
they
> lease from us. Within an encrypted Stored Procedure I am using the
> OPENDATASOURCE method with a connect string containing our IP address. It
is
> working on 90% of the sites. However some of the sites are receiving an
> error:
> Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
> Line 37
> SQL Server does not exist or access denied.
> On most of the servers where the procedure is WORKING, a peek at the
> firewall configuration using Shields-Up service from Gibson Research shows
> that ports 1433 and 1434 are in Stealth mode. But, as I said, the
connection
> is still operating just fine. All sites, including the ones that don't
work,
> have the TCP/IP protocol enabled in the Client Network Utility on Port
1433.
> So I am at a loss to figure out why the Internet connection is not working
> at some sites. Any ideas?
> Also, is there another way that I can distribute the "key" without user
> intervention using "back-end" programs or procedures? Is there a way to
> connect and retieve data via port 80 which is usually left open for
outbound
> requests? Thanks in advance...
>
Problem connecting to SQL Server over the internet
I have opened ports 1433 and 1434 on a SQL Server on our network to allow
our customers to receive a monthly subscription "key" for the software they
lease from us. Within an encrypted Stored Procedure I am using the
OPENDATASOURCE method with a connect string containing our IP address. It is
working on 90% of the sites. However some of the sites are receiving an
error:
Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
Line 37
SQL Server does not exist or access denied.
On most of the servers where the procedure is WORKING, a peek at the
firewall configuration using Shields-Up service from Gibson Research shows
that ports 1433 and 1434 are in Stealth mode. But, as I said, the connection
is still operating just fine. All sites, including the ones that don't work,
have the TCP/IP protocol enabled in the Client Network Utility on Port 1433.
So I am at a loss to figure out why the Internet connection is not working
at some sites. Any ideas?
Also, is there another way that I can distribute the "key" without user
intervention using "back-end" programs or procedures? Is there a way to
connect and retieve data via port 80 which is usually left open for outbound
requests? Thanks in advance...I would make network traces at the problem site and either review the
firewall logs or
make simulataneous traces on the server. This sounds like a tcp issue not
a SQL issue.
Verify that the 3 way tcp handshake is completing. The login packet isn't
sent until this completes.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thank you both for your replies. I will make sure that the TCP issues are
resolved at the client sites before looking any further.
"John Kotuby" <jkotuby@.snet.net> wrote in message
news:undiWF%23TEHA.2028@.TK2MSFTNGP11.phx.gbl...
> I have opened ports 1433 and 1434 on a SQL Server on our network to allow
> our customers to receive a monthly subscription "key" for the software
they
> lease from us. Within an encrypted Stored Procedure I am using the
> OPENDATASOURCE method with a connect string containing our IP address. It
is
> working on 90% of the sites. However some of the sites are receiving an
> error:
> Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
> Line 37
> SQL Server does not exist or access denied.
> On most of the servers where the procedure is WORKING, a peek at the
> firewall configuration using Shields-Up service from Gibson Research shows
> that ports 1433 and 1434 are in Stealth mode. But, as I said, the
connection
> is still operating just fine. All sites, including the ones that don't
work,
> have the TCP/IP protocol enabled in the Client Network Utility on Port
1433.
> So I am at a loss to figure out why the Internet connection is not working
> at some sites. Any ideas?
> Also, is there another way that I can distribute the "key" without user
> intervention using "back-end" programs or procedures? Is there a way to
> connect and retieve data via port 80 which is usually left open for
outbound
> requests? Thanks in advance...
>
our customers to receive a monthly subscription "key" for the software they
lease from us. Within an encrypted Stored Procedure I am using the
OPENDATASOURCE method with a connect string containing our IP address. It is
working on 90% of the sites. However some of the sites are receiving an
error:
Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
Line 37
SQL Server does not exist or access denied.
On most of the servers where the procedure is WORKING, a peek at the
firewall configuration using Shields-Up service from Gibson Research shows
that ports 1433 and 1434 are in Stealth mode. But, as I said, the connection
is still operating just fine. All sites, including the ones that don't work,
have the TCP/IP protocol enabled in the Client Network Utility on Port 1433.
So I am at a loss to figure out why the Internet connection is not working
at some sites. Any ideas?
Also, is there another way that I can distribute the "key" without user
intervention using "back-end" programs or procedures? Is there a way to
connect and retieve data via port 80 which is usually left open for outbound
requests? Thanks in advance...I would make network traces at the problem site and either review the
firewall logs or
make simulataneous traces on the server. This sounds like a tcp issue not
a SQL issue.
Verify that the 3 way tcp handshake is completing. The login packet isn't
sent until this completes.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thank you both for your replies. I will make sure that the TCP issues are
resolved at the client sites before looking any further.
"John Kotuby" <jkotuby@.snet.net> wrote in message
news:undiWF%23TEHA.2028@.TK2MSFTNGP11.phx.gbl...
> I have opened ports 1433 and 1434 on a SQL Server on our network to allow
> our customers to receive a monthly subscription "key" for the software
they
> lease from us. Within an encrypted Stored Procedure I am using the
> OPENDATASOURCE method with a connect string containing our IP address. It
is
> working on 90% of the sites. However some of the sites are receiving an
> error:
> Server: Msg 17, Level 16, State 1, Procedure PLSPSYS_ALTER_KEYSP_REMOTE,
> Line 37
> SQL Server does not exist or access denied.
> On most of the servers where the procedure is WORKING, a peek at the
> firewall configuration using Shields-Up service from Gibson Research shows
> that ports 1433 and 1434 are in Stealth mode. But, as I said, the
connection
> is still operating just fine. All sites, including the ones that don't
work,
> have the TCP/IP protocol enabled in the Client Network Utility on Port
1433.
> So I am at a loss to figure out why the Internet connection is not working
> at some sites. Any ideas?
> Also, is there another way that I can distribute the "key" without user
> intervention using "back-end" programs or procedures? Is there a way to
> connect and retieve data via port 80 which is usually left open for
outbound
> requests? Thanks in advance...
>
Subscribe to:
Posts (Atom)