Error encountered UNC path error during remote installation

Good day good people of the forum while carrying out a remote installation i encountered an UNC path error can anyone be of help giving me a comprehensive answer to the problem. am stuck i cant move ahead from that part of the installation

Hi Yudee, can you send us the error message? Are you getting it in a log? If so, which log?

Thanks,
Samuel Lester (MSFT)

sql

Error Deleteing Remote File

I am trying to delete a remote file as part of an SSIS package. The FTP Task I have to retrieve the file works fine. I use the same remote path variable and connection manager for both tasks. However, when the delete step executes I receive the error:

Error: 0xC002918E at FTP Task, FTP Task: Unable to delete remote files using "FTP Connection Manager 1".

Sounds like a permission issue.|||This is a known problem with the FTP task in SSIS trying to delete a file on a non-Windows FTP servers.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1074276&SiteID=1

I do not know if SP2 fixes this problem or not.
|||I can delete the files from the FTP command line. I have a DTS package that uses a .bat file to do this, I just want to put it into SSIS. Thanks for the info.|||Is there a way to tell if the server is not Windows?|||HAs this issue been aknowledge by Microsoft? [Microsoft follow-up]|||

I don't understand your question. Your the closest thing to Microsoft that I have seen involved in any discussion in this area, anywhere I've looked.

Tim

|||Yes, it is still an active bug report, reported over 1 year ago.

See: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=126207
|||No, you would have to know ahead of time what kind of server you are talking too.

However, there is a workaround on the thread I gave in the previous message. Basically, don't use the FTP task, use a script task and code it by hand.

|||We are aware of this bug and it will be fixed in the coming major release. Please contact CSS if you need a hotifx. Thanks

Error copying data to a remote sql server 2005 database.

When copying data to a remote SQL2K5 destination from a SQL2K5 source database, both using mixed sql server security mode, my job generates the following error:

[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".

This occurs after the destination database tables have been truncated and replacement data from the source would begin to copy.

The same process can be successfully completed from the Management studio with a simple data export process. However, when I run the saved package again from the BI interface, I get this error.

My search engine searches have yielded numerous hits of others having the same problem with one microsoft rep indicating it was a bug and would be resolved in sp1. I am working with sp1. Oddly, there is only mention of this in the forums. No KB article from MS addresses the problem and I do not see it addressed elsewhere at sqlservercentral.

It appears that others have switched to Integrated Security and resolved the problem. However, I do not have that option with a remotely hosted database.

Does anyone have any information concerning this problem?

bug reports may be submitted here: SQL Server Feedback.

i suggest that you first check for the status of any existing bug report to avoid duplication.

Error connecting to SQL Server 2005 - ... does not allow remote connections?

I have an ASP.NET 2.0 Website that in the connection string does not connect
to the local SQL Server but tries to connect to another SQL Server 2005
Server in another State. When I run the application from Visual Studio 2005
it connects just fine. When I published the website to the Live Server I
receive the below error:
An error has occurred while establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by the fact that
under the default settings SQL Server does not allow remote connections.
Any ideas?
Peace in Christ
Marco Napoli
http://www.ourlovingmother.orgCheck this url for troubleshooting:
http://blogs.msdn.com/sql_protocols.../22/506607.aspx
Jack Vamvas
___________________________________
Receive free SQL tips - www.ciquery.com/sqlserver.htm
___________________________________
"Marco Napoli" <marco@.avantitecnospam.com> wrote in message
news:#14p4JoaGHA.5004@.TK2MSFTNGP02.phx.gbl...
> I have an ASP.NET 2.0 Website that in the connection string does not
connect
> to the local SQL Server but tries to connect to another SQL Server 2005
> Server in another State. When I run the application from Visual Studio
2005
> it connects just fine. When I published the website to the Live Server I
> receive the below error:
> An error has occurred while establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by the fact that
> under the default settings SQL Server does not allow remote connections.
> Any ideas?
> --
> Peace in Christ
> Marco Napoli
> http://www.ourlovingmother.org
>
>|||Thank you.
Marco
"Jack Vamvas" <delete_this_bit_jack@.ciquery.com_delete> wrote in message
news:euqdnWInVNe2O8zZRVnyjg@.bt.com...
> Check this url for troubleshooting:
> http://blogs.msdn.com/sql_protocols.../22/506607.aspx
> --
> Jack Vamvas
> ___________________________________
> Receive free SQL tips - www.ciquery.com/sqlserver.htm
> ___________________________________
>
> "Marco Napoli" <marco@.avantitecnospam.com> wrote in message
> news:#14p4JoaGHA.5004@.TK2MSFTNGP02.phx.gbl...
> connect
> 2005
>

Error connecting to SQL 2000 db "The entry MCLConnectionString has already been added"

When I try to run my application using VWD from the file system I can connect and run the application and it connects to the remote SQL 2000 server with no problem.

However, when I publish to my web server I get the folloiwng error message:

Anyone got any ideas??

Configuration Error

Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message:The entry 'MCLConnectionString' has already been added.

Source Error:

Line 11: <appSettings/>Line 12: <connectionStrings>Line 13: <add name="MCLConnectionString" connectionString="Data Source=GEACO1INTR1;Initial Catalog=MCL;Persist Security Info=True;User ID=ASPNET;Password=PAUL0001" providerName="System.Data.SqlClient"/>Line 14: </connectionStrings>Line 15: <system.web>

Source File:c:\inetpub\wwwroot\mcltest\web.config Line:13

I also notice that it works if I put the connection string in each form, but as soon as I try to add it to the web.config file I get the above error.

Thanks

Paul

|||

My guess is that you have a ConnectionString with the same name on a Parent Web Application, my advise would be either to change the name of the ConnectionString, or do this:

<connectionString>
<clear/>
<add name="MCLConnectionString" connectionString="..." />
</connectionStrings
Hope this Helps,

Roberto Hernandez-Pou
http://www.rhpconsulting.net

IMPORTANT: If you use the <clear/> to clean all connectionString keys, you would also be removing the ones for the SqlAuthenticationProvider and SqlRoleProvider.

|||

To add onto Roberto's reply...

If the MCLConnectionString does already exist higher in the configuration hierarchy, you don't have to add it again to use at this level. Remove it at this level's web.config and read the connection string as normal, and the configuration API will pick it up.

Don

|||

Thanks, that sorted it. I had a copy of the web.config file left in the root directory of the web server.

Thanks again for your help

Paul

Error connecting to Report Manager

System.Net.WebException: Unable to connect to the remote server -->
System.Net.Sockets.SocketException: No connection could be made because the
target machine actively refused it 127.0.0.1:443
Can someone help me with that error?
ThanksThats a bit unusual. Try this post
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=552017&SiteID=1
Cheers
Shai
On Nov 19, 11:46 pm, "Mark Goldin" <mgol...@.ufandd.com> wrote:
> System.Net.WebException: Unable to connect to the remote server -->
> System.Net.Sockets.SocketException: No connection could be made because the
> target machine actively refused it 127.0.0.1:443
> Can someone help me with that error?
> Thanks

Error connecting to remote SQL Server Analysis Services

Hi All,

I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.

I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-

"Cannot connect to <IP Address>

A Connection cannot be made. Ensure that the server is running.

(Microsoft.AnalysisServices.AdomdClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"

Things I have tried:-

- Ensured that the remote connection is enabled.

- Have SQL Server 2005 SP1 installed on the remote server.

- Tried installined SQL Server 2005 SP2 on my local machine, but same error.

I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.

Any kind of help will be appreciated on this.

Regards,

Sumeet:-)

We had similar problems when deploying cubes (although running Vanilla - not SP1)

We could replicate this problem by doing the following

1) Ensure all of the SQL Server Services (inc Analysis Services) are running

2) Browse a cube on your local machine

3) Rebuild this cube on your local machine

4) Check back on the remote server to see if AS is still running

If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following

"

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..

"

We found upgrading to SP2 stopped this issue

|||

Hi,

Nice to see your reply.

The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.

Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...

Regards,

Sumeet

|||

hi

did you check the security settings of the analysis server? (right click -> properties-> security)

add 'everyone' to it and try again for testing. i believe you should put your active directory user in it

for http connectivity, the default port number of analysis services is 2383

hope this helps

|||

Hi Christina,

I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.

Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.

Regards,

Sumeet

|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:

i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work

good luck
|||

Hi Vali,

I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.

Later on I installed SP2 on my local machine and still I am getting the same error.

Regards,

Sumeet.

|||

In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.

Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?

|||

Hi John,

I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,

Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.

Regards,

Sumeet

|||

Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.

Thanks in advance.

Sarah Cameron - Incycle Software

|||

The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:

<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>

|||

Hi Sarah,

We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.

So still waiting for help..

Regards,

Sumeet

|||

Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.

__

Sarah Cameron - Incycle Software

Error connecting to remote SQL Server Analysis Services

Hi All,

I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.

I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-

"Cannot connect to <IP Address>

A Connection cannot be made. Ensure that the server is running.

(Microsoft.AnalysisServices.AdomdClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"

Things I have tried:-

- Ensured that the remote connection is enabled.

- Have SQL Server 2005 SP1 installed on the remote server.

- Tried installined SQL Server 2005 SP2 on my local machine, but same error.

I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.

Any kind of help will be appreciated on this.

Regards,

Sumeet:-)

We had similar problems when deploying cubes (although running Vanilla - not SP1)

We could replicate this problem by doing the following

1) Ensure all of the SQL Server Services (inc Analysis Services) are running

2) Browse a cube on your local machine

3) Rebuild this cube on your local machine

4) Check back on the remote server to see if AS is still running

If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following

"

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..

"

We found upgrading to SP2 stopped this issue

|||

Hi,

Nice to see your reply.

The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.

Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...

Regards,

Sumeet

|||

hi

did you check the security settings of the analysis server? (right click -> properties-> security)

add 'everyone' to it and try again for testing. i believe you should put your active directory user in it

for http connectivity, the default port number of analysis services is 2383

hope this helps

|||

Hi Christina,

I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.

Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.

Regards,

Sumeet

|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:

i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work

good luck
|||

Hi Vali,

I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.

Later on I installed SP2 on my local machine and still I am getting the same error.

Regards,

Sumeet.

|||

In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.

Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?

|||

Hi John,

I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,

Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.

Regards,

Sumeet

|||

Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.

Thanks in advance.

Sarah Cameron - Incycle Software

|||

The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:

<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>

|||

Hi Sarah,

We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.

So still waiting for help..

Regards,

Sumeet

|||

Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.

__

Sarah Cameron - Incycle Software

Error connecting to remote SQL Server Analysis Services

Hi All,

I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.

I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-

"Cannot connect to <IP Address>

A Connection cannot be made. Ensure that the server is running.

(Microsoft.AnalysisServices.AdomdClient)

A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"

Things I have tried:-

- Ensured that the remote connection is enabled.

- Have SQL Server 2005 SP1 installed on the remote server.

- Tried installined SQL Server 2005 SP2 on my local machine, but same error.

I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.

Any kind of help will be appreciated on this.

Regards,

Sumeet:-)

We had similar problems when deploying cubes (although running Vanilla - not SP1)

We could replicate this problem by doing the following

1) Ensure all of the SQL Server Services (inc Analysis Services) are running

2) Browse a cube on your local machine

3) Rebuild this cube on your local machine

4) Check back on the remote server to see if AS is still running

If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following

"

The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..

"

We found upgrading to SP2 stopped this issue

|||

Hi,

Nice to see your reply.

The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.

Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...

Regards,

Sumeet

|||

hi

did you check the security settings of the analysis server? (right click -> properties-> security)

add 'everyone' to it and try again for testing. i believe you should put your active directory user in it

for http connectivity, the default port number of analysis services is 2383

hope this helps

|||

Hi Christina,

I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.

Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.

Regards,

Sumeet

|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:

i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work

good luck
|||

Hi Vali,

I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.

Later on I installed SP2 on my local machine and still I am getting the same error.

Regards,

Sumeet.

|||

In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.

Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?

|||

Hi John,

I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,

Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.

Regards,

Sumeet

|||

Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.

Thanks in advance.

Sarah Cameron - Incycle Software

|||

The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:

<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>

|||

Hi Sarah,

We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.

So still waiting for help..

Regards,

Sumeet

|||

Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.

__

Sarah Cameron - Incycle Software

Error connecting to remote SQL 2000 Server

I'm experiencing a problem connecting to a SQL 2000 server through my ASP code. My connection string is as follows:

<addname="TheConnectionString"connectionString="driver={Sql Server};provider=MSDASQL;server=10.0.1.42;database=dbname;uid=*********;pwd=*********"providerName="System.Data.Odbc" />

The problem doesn't occur when I run my ASP code from my workstation using VS.NET's builtin webserver. It makes the connections and executes the CRUD commands successfully. However, when I publish my site to the webserver (which resides on 10.0.1.16) it fails out with the following error:

System.Data.Odbc.OdbcException: ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
ERROR [01000] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

I've verified that the webserver can talk to the DB server by connecting to the remote DB server through SQL Enterprise Manager running locally on the webserver. If I try to do this with a DSN I get the same results. I get the same error from any other webserver on the internal network. The difference between my workstation and the internal network is that I'm using a VPN to connect to our internal network while the webservers are physically connected to it. Firewalling isn't the issue in this case because the webservers and DB server are on a trusted network. I've seen other ways of connecting to the DB server including using Named Pipes (which I would rather not do because I don't want to setup a named pipe on the production db server).

I'm relatively new to ASP.NET 2.0, so the above connection string is an adaptation of some old ASP code. If anybody has any suggestions on a better way to construct this connection string, please let me know. I've been racking my brains trying to get this to work outside of the devel env.

Try with this:

<add name="TheConnectionString" connectionString="Server=10.0.1.42;Database=dbname;User ID=*********;Password=*********;"/>

|||

johnladda:

System.Data.Odbc.OdbcException: ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
ERROR [01000] [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).

First, this error is a generic one so your actual problem may range from incorrect credentials to a network problem.

Second, I'm not too sure why you've used ODBC library to connect to SQL while you've the SQL library.

johnladda:

I'm relatively new to ASP.NET 2.0, so the above connection string is an adaptation of some old ASP code. If anybody has any suggestions on a better way to construct this connection string, please let me know.

Third, you can use "Data Source=xxx;Initial Catalog=xxx;User ID=xxx;Password=xxx" to connect to SQL Server. You can referwww.connectionstrings.com . This site provides a number of connection string examples for almost every database.

Hope this will help.

|||

This site is fantastic. It's exactly what I needed. I was wondering if the "Data Source" property of the connection string works similar to the "Server" property in that you can specify the port number too? If not, how would I go about specifying the port number in the connection string. I only just recently found out that the person who implimented the database server put it on an alternate port.

|||

johnladda:

I was wondering if the "Data Source" property of the connection string works similar to the "Server" property in that you can specify the port number too? If not, how would I go about specifying the port number in the connection string. I only just recently found out that the person who implimented the database server put it on an alternate port.

No, you've mistaken the Data Source property of the connection string. It is no way similar to any server control. In fact, you can user Data Source or Server property in your connection string. Below are some of the alternatives you can use in your connection string.

Data Source = Server
Initial Catalog = Database
User Id = uId
Password = pwd

The default port is 1433 for SQL Server TCP/IP connection. You can specify any other port in your connection string as below:

"Data Source=xxx,portNumber;Initial Catalog=xxx;User ID=xxx;Password=xxx". That is, after either the IP or the name of the server put a comma and then provide the port number.

Error connecting to remote server using sql server 2005 management studio

I have a sql server 2000 database on my server with following setting

Server name KamiServer and IP range: 201.134.180.180 - 201.134.180.190
The SQL login (read-only access) is: Kamran and the password is: Shahid

When I try to caonnect it through Sql server management studio I got Following error
Testing the registered server failed. Verify the server name, login credentials, and database, and then click Test again.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) (Microsoft SQL Server, Error: 11001)

I can connect to other local server on my lanThere are some pieces missing in your explanation. is that a firewalled server ? As the host is not reachable, Is the IP reachable from the connecting client ?

HTH, Jens Suessmeyer.

-
http://www.sqlserver2005.de
-|||

Refer the below blog for more information

http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx

Error Connecting to Remote Server Using Microsoft SQL Server Management Studio Express

Dear All,

I am trying to connect to a remote sql server 2005. So I have install the Microsoft SQL Server Management Studio Express. When I try to connect I get the error below.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53). Can some one please help. I have even port no 1533 on my pc. Thanks.

This support article might give you some more info..

http://support.microsoft.com/kb/914277

By default, SQL 2005 servers are configured to not allow remote connections through TCP/IP. This is a security measure. You will want to ensure that the remote SQL Server you are trying to connect to is configured to allow remote connections.

Hopefully this helps, if not, please post back with more info.

-Steve

|||

Also, here is a similar thread that you might want to skim through to see if there are any other ideas there

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=847152&SiteID=1

|||

Dear Steve,

I have manage to connect the problem is on my side because of the port I never opened. I realy wish you thanks for all the references you gave and help. Thanks.

|||

I am facing same problem.

I want to connect to Remote Server (windows 2003 server). Iam using Deveoper ed. connecting to express ed.

I have allowed TCP-IP and enabled browser service. and restarted server also. windows firewall disabled.

I want to know where port involes in sql server and where to configure port for both sql server server.

Does SP1 creates probelm if it is not installed.

Error Connecting to Remote Server Using Microsoft SQL Server Management Studio Developer

Dear All,

I am trying to connect to a remote sql server 2005. So I have install the Microsoft SQL Server Management Studio Express. When I try to connect I get the error below.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53). Can some one please help. I have even port no 1533 on my pc. Thanks.

This support article might give you some more info..

http://support.microsoft.com/kb/914277

By default, SQL 2005 servers are configured to not allow remote connections through TCP/IP. This is a security measure. You will want to ensure that the remote SQL Server you are trying to connect to is configured to allow remote connections.

Hopefully this helps, if not, please post back with more info.

-Steve

|||

Also, here is a similar thread that you might want to skim through to see if there are any other ideas there

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=847152&SiteID=1

|||

Dear Steve,

I have manage to connect the problem is on my side because of the port I never opened. I realy wish you thanks for all the references you gave and help. Thanks.

|||

I am facing same problem.

I want to connect to Remote Server (windows 2003 server). Iam using Deveoper ed. connecting to express ed.

I have allowed TCP-IP and enabled browser service. and restarted server also. windows firewall disabled.

I want to know where port involes in sql server and where to configure port for both sql server server.

Does SP1 creates probelm if it is not installed.

Error connecting to remote server

Hi
I am trying to cerate a System DSN (in ODBC Data Source Administrator) for a
remote SQL Server. I am getting the below error message;
Connection failed:
SQL State: '01000'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
Instance())
Connection failed:
SQL State: '08001'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
What is the problem and how can I fix it?
Thanks
RegardsOn Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
> Hi
> I am trying to cerate a System DSN (in ODBC Data Source Administrator) for a
> remote SQL Server. I am getting the below error message;
> Connection failed:
> SQL State: '01000'
> SQL Server Error: 14
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
> Instance())
> Connection failed:
> SQL State: '08001'
> SQL Server Error: 14
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
> What is the problem and how can I fix it?
> Thanks
> Regards
the remote server isn't running sql as a named instance is it?|||Not sure. It is our web hosts which is an outside company. What should I ask
them to do?
Many Thanks
Regards
"densial" <densial@.gmail.com> wrote in message
news:1189754261.882976.147900@.r34g2000hsd.googlegroups.com...
> On Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
>> Hi
>> I am trying to cerate a System DSN (in ODBC Data Source Administrator)
>> for a
>> remote SQL Server. I am getting the below error message;
>> Connection failed:
>> SQL State: '01000'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
>> Instance())
>> Connection failed:
>> SQL State: '08001'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
>> What is the problem and how can I fix it?
>> Thanks
>> Regards
> the remote server isn't running sql as a named instance is it?
>|||We are trying to access the SQL Server from behind an ISA 2004 firewall.
Even though I have created a rule for port 1433 on ISA 2004, I wonder if
there is something still missing at the ISA 2004 that I need to do.
Many Thanks
Regards
"densial" <densial@.gmail.com> wrote in message
news:1189754261.882976.147900@.r34g2000hsd.googlegroups.com...
> On Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
>> Hi
>> I am trying to cerate a System DSN (in ODBC Data Source Administrator)
>> for a
>> remote SQL Server. I am getting the below error message;
>> Connection failed:
>> SQL State: '01000'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
>> Instance())
>> Connection failed:
>> SQL State: '08001'
>> SQL Server Error: 14
>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
>> What is the problem and how can I fix it?
>> Thanks
>> Regards
> the remote server isn't running sql as a named instance is it?
>|||On Sep 14, 8:49 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
> We are trying to access the SQL Server from behind an ISA 2004 firewall.
> Even though I have created a rule for port 1433 on ISA 2004, I wonder if
> there is something still missing at the ISA 2004 that I need to do.
> Many Thanks
> Regards
> "densial" <dens...@.gmail.com> wrote in message
> news:1189754261.882976.147900@.r34g2000hsd.googlegroups.com...
> > On Sep 14, 4:57 pm, "John" <J...@.nospam.infovis.co.uk> wrote:
> >> Hi
> >> I am trying to cerate a System DSN (in ODBC Data Source Administrator)
> >> for a
> >> remote SQL Server. I am getting the below error message;
> >> Connection failed:
> >> SQL State: '01000'
> >> SQL Server Error: 14
> >> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Invalid
> >> Instance())
> >> Connection failed:
> >> SQL State: '08001'
> >> SQL Server Error: 14
> >> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid Connection
> >> What is the problem and how can I fix it?
> >> Thanks
> >> Regards
> > the remote server isn't running sql as a named instance is it?
that error msg <snip>Invalid Instance()</snip> makes me think your
providor is using a named instance, just ask them if they are, then
reference your server as "servername\instancename" (check the slash
direction, can't remember off hand if it's forward or backward).
Another issue could be the port number, try either "servername,1433"
or "servername\instancename,1433" as your server address. this is
often a problem if your using load balanced sql server. also there's
somestuff about the server knowing which port to reply on (for
sql2005), but this is a bit more complex and sometimes requires some
server side config in awkward situations, anyways if it's 2k5 your
connecting to read up about sqlbrowser replying to the client on port
1434 instead of 1433.

Error connecting to remote connections...

That's what appears at my client site. I have virtually the exact same
configuration on a handful of servers using the SQL Reporting Services and
the RDLC which is working great. Except this one server has:
"An error has occurred when establishing a connection to the server. When
connecting to SQL Server 2005, this failure may be caused by teh fact that
under the default settings SQL Server does not allow remote connections.
Named Pipes provider, error: 40 - Could not open a connection to the SQL
Server).
I think the IT admin used SQL permissions when he installed. Could that be
the problem?
Thanks in Advance.
ChrisThis link might help,
http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
daw
"Chris Marsh" wrote:
> That's what appears at my client site. I have virtually the exact same
> configuration on a handful of servers using the SQL Reporting Services and
> the RDLC which is working great. Except this one server has:
> "An error has occurred when establishing a connection to the server. When
> connecting to SQL Server 2005, this failure may be caused by teh fact that
> under the default settings SQL Server does not allow remote connections.
> Named Pipes provider, error: 40 - Could not open a connection to the SQL
> Server).
> I think the IT admin used SQL permissions when he installed. Could that be
> the problem?
> Thanks in Advance.
> Chris
>
>|||Sorry, I should have specified this earlier but the SQL DB is SQL 2000 not
2005 which is what is strange. Again, works on multiple other configurations
but not this one.
"daw" <daw@.discussions.microsoft.com> wrote in message
news:D05FF90C-2A0D-43B9-83B4-D348859995E9@.microsoft.com...
> This link might help,
> http://vadivel.blogspot.com/2007/01/error-has-occurred-while-establishing.html.
> daw
> "Chris Marsh" wrote:
>> That's what appears at my client site. I have virtually the exact same
>> configuration on a handful of servers using the SQL Reporting Services
>> and
>> the RDLC which is working great. Except this one server has:
>> "An error has occurred when establishing a connection to the server. When
>> connecting to SQL Server 2005, this failure may be caused by teh fact
>> that
>> under the default settings SQL Server does not allow remote connections.
>> Named Pipes provider, error: 40 - Could not open a connection to the SQL
>> Server).
>> I think the IT admin used SQL permissions when he installed. Could that
>> be
>> the problem?
>> Thanks in Advance.
>> Chris
>>

Error Connecting to Database (SQL Server 2005)!

Hello all,
I'm encountering an issue with regards to the default REMOTE LOGIN
settings to my database instance on SQL Server 2005.
The message I am recieving is as follows:
"An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact
that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server
Please check your database settings and credentials and confirm that
the server is reachable."
To my knowledge, I am able to see my database running, and that I have
already set up the DAC Surface Area Configuration, and ensured that
both "Named Pipes and TCP/IP protocols" have been enabled.
Whats wrong here guys...am I missing something?
Mohd Al Junaibi wrote:
> Hello all,
> I'm encountering an issue with regards to the default REMOTE LOGIN
> settings to my database instance on SQL Server 2005.
> The message I am recieving is as follows:
> "An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact
> that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server
> Please check your database settings and credentials and confirm that
> the server is reachable."
>
> To my knowledge, I am able to see my database running, and that I have
> already set up the DAC Surface Area Configuration, and ensured that
> both "Named Pipes and TCP/IP protocols" have been enabled.
> Whats wrong here guys...am I missing something?
>
Did you enable Remote Connections in the Surface Area Configuration tool?
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Error Connecting to Database (SQL Server 2005)!

Hello all,
I'm encountering an issue with regards to the default REMOTE LOGIN
settings to my database instance on SQL Server 2005.
The message I am recieving is as follows:
"An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact
that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server
Please check your database settings and credentials and confirm that
the server is reachable."
To my knowledge, I am able to see my database running, and that I have
already set up the DAC Surface Area Configuration, and ensured that
both "Named Pipes and TCP/IP protocols" have been enabled.
Whats wrong here guys...am I missing something?Mohd Al Junaibi wrote:
> Hello all,
> I'm encountering an issue with regards to the default REMOTE LOGIN
> settings to my database instance on SQL Server 2005.
> The message I am recieving is as follows:
> "An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact
> that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server
> Please check your database settings and credentials and confirm that
> the server is reachable."
>
> To my knowledge, I am able to see my database running, and that I have
> already set up the DAC Surface Area Configuration, and ensured that
> both "Named Pipes and TCP/IP protocols" have been enabled.
> Whats wrong here guys...am I missing something?
>
Did you enable Remote Connections in the Surface Area Configuration tool?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yep...used the Surface Area Configuration and enabled remote logins
with Named Pipes and Support.
But just so that I didn't do anything wrong..what would be the
essential steps here (if you were in my shoes)..?|||Mohd Al Junaibi wrote:
> Yep...used the Surface Area Configuration and enabled remote logins
> with Named Pipes and Support.
> But just so that I didn't do anything wrong..what would be the
> essential steps here (if you were in my shoes)..?
>
Is SQL running on your local workstation, or on a remote server? Can
you ping that remote server, via hostname and via IP address? Is there
a firewall involved?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, both MSSQL Service is running, and the agent is on as well. I
don't recall having the firewall running.
I'm beginning to think it has to do with credentials.
I'm running a command to create my WEBFORMS on a virtual directory,
it's experimental and called "Blinq" from Microsoft.
Anyways...I'll try to check things here..
thanks a million

Error Connecting to Database (SQL Server 2005)!

Hello all,
I'm encountering an issue with regards to the default REMOTE LOGIN
settings to my database instance on SQL Server 2005.
The message I am recieving is as follows:
"An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact
that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server
Please check your database settings and credentials and confirm that
the server is reachable."
To my knowledge, I am able to see my database running, and that I have
already set up the DAC Surface Area Configuration, and ensured that
both "Named Pipes and TCP/IP protocols" have been enabled.
Whats wrong here guys...am I missing something?Mohd Al Junaibi wrote:
> Hello all,
> I'm encountering an issue with regards to the default REMOTE LOGIN
> settings to my database instance on SQL Server 2005.
> The message I am recieving is as follows:
> "An error has occurred while establishing a connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact
> that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server
> Please check your database settings and credentials and confirm that
> the server is reachable."
>
> To my knowledge, I am able to see my database running, and that I have
> already set up the DAC Surface Area Configuration, and ensured that
> both "Named Pipes and TCP/IP protocols" have been enabled.
> Whats wrong here guys...am I missing something?
>
Did you enable Remote Connections in the Surface Area Configuration tool?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yep...used the Surface Area Configuration and enabled remote logins
with Named Pipes and Support.
But just so that I didn't do anything wrong..what would be the
essential steps here (if you were in my shoes)..?|||Mohd Al Junaibi wrote:
> Yep...used the Surface Area Configuration and enabled remote logins
> with Named Pipes and Support.
> But just so that I didn't do anything wrong..what would be the
> essential steps here (if you were in my shoes)..?
>
Is SQL running on your local workstation, or on a remote server? Can
you ping that remote server, via hostname and via IP address? Is there
a firewall involved?
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||Yes, both MSSQL Service is running, and the agent is on as well. I
don't recall having the firewall running.
I'm beginning to think it has to do with credentials.
I'm running a command to create my WEBFORMS on a virtual directory,
it's experimental and called "Blinq" from Microsoft.
Anyways...I'll try to check things here..
thanks a million

Error after install with Remote SQL Server Instance

Hi,
I've been having a lot of problems with installing Reporting Services on our
webserver. We want the Report Server to be available externally so I've
installed the Report Server and Report Manager on our webserver and the
ReportServer database is located on a separate database server. The install
goes OK and a first test of http://xxx/ReportServer looked fine but when I
try to open Report Manager I get the below error. I've tried various
configurations with the install, so with NT AUTHORITY\SYSTEM as the user that
starts the Report Server service and then with various domain users and sql
logins that all should have access to the database server. Also, if the
service is stopped (it starts OK directly after it is installed) then it
cannot be restarted. In the log is says that it cannot connect to the
database, but there are no errors during the install or in any of the log
files the first time the service starts. If I try to restart the service then
it hangs and usually the server has to be rebooted to stop it.
This is a clean install of Reporting Services, we've never had a previous
version of it on the server. Both the webserver and database server are
Win2000 (sp4) with IIS 5.0 on the webserver. And it is the Standard Edition
of Reporting Services.
So far I have tried the following measures to fix this:
Reinstall ASP .NET 1.1 (v1.1.4322) and have registered it with IIS and
registered aspnet_isapi.dll.
Set file permissions on the winnt\temp directory and the Temporary ASP .NET
Files directory and the C:\Documents and Settings\xxx\ASPNET\Local
Settings\Temp directory. (ASPNET account, SYSTEM acount and even tried giving
Everyone full control)
Checked that all file associations in IIS are correct (aspx files are
associated with the correct version of the .NET framework)
Installing and uninstalling numerous times.
Installing service pack 1 (this fails everytime)
I have not been able to find any post on google with exactly the same error
and symptoms so any help would be much appreciated.
Regards,
Daniel Lee
aspnet_wp!ui!fb4!10/11/2004-16:53:32:: e ERROR: Server was unable to process
request. --> File or assembly name noogu73a.dll, or one of its dependencies,
was not found.
aspnet_wp!ui!fb4!10/11/2004-16:53:32:: e ERROR: HTTP status code --> 500
--Details--
System.Web.Services.Protocols.SoapException: Server was unable to process
request. --> File or assembly name noogu73a.dll, or one of its dependencies,
was not found.
at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at
Microsoft.SqlServer.ReportingServices.ReportingService.ListSecureMethods()
at Microsoft.SqlServer.ReportingServices.RSConnection.GetSecureMethods()
at Microsoft.ReportingServices.UI.RSWebServiceWrapper.GetSecureMethods()
at
Microsoft.SqlServer.ReportingServices.RSConnection.IsSecureMethod(String
methodname)
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at
Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel(HttpsLevel
level)
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object
sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain()
aspnet_wp!ui!fb4!10/11/2004-16:53:42:: e ERROR: Exception in ShowErrorPage:
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg) at at System.Threading.Thread.AbortInternal()
at System.Threading.Thread.Abort(Object stateInfo)
at System.Web.HttpResponse.End()
at System.Web.HttpServerUtility.Transfer(String path, Boolean preserveForm)
at Microsoft.ReportingServices.UI.ReportingPage.ShowErrorPage(String
errMsg)In case anyone else ever gets a simliar error, this seems to have been
something to do with corruption of a windows dll due to a hard disk failure.
However, my bad experience with Reporting Services continues on a new server.
Would find it hard to recommend this product (at least just now) to anyone
who wants to use this in a normal production environment (i.e. separate web
server and database servers), especially if trying to connect to an OLAP cube
and using MDX. I have wasted an unbelieveable amount of time just trying to
get reporting services installed properly. All this is a real pity as I
really like what it can (should) do. Maybe next year with SQL 2005?