Hi all, I'm running SQL Server 2008 on Windows 7, x64 on Intel i3 PC. SQLExpress is an instance. Its TCP and shared memory are enabled with port 65004 assigned. Windows has remot access enabled. SQL Server, SQL Browser, and all ports are allowed. Machine and router Repotec IP's are fixed. Router port forwarding is done (It does not ask for port protocol: whether TCP or UDP).  Antivirus stopped. Connecting to 'public IP/SQLExpress' from same machine failed with the error message 'Object not found. The requested URL/SQLExpress was not found in the RomPager server'. TCPviewer reports port 65004 is listening. Any idea where the error is? Best regards.                                                                                                                               Prof. Dr. Said El Noshokaty

 

Connecting to 'public IP/SQLExpress' from same machine failed with the error message 'Object not found. The requested URL/SQLExpress was not found in the RomPager server'. TCPviewer reports port 65004 is listening. Any idea where the error is? 

I know nothing about "RomPager server" but a cursory search shows it is an HTTP engine.  Whatever application you are using seems to be connecting to that engine instead of the SQL instance.  What application are you using to connect to the SQL Express instance?  If the network is open up, I would expect the IP and port number to work. 

The requested URL/SQLExpress was not found in the RomPager server'. 

Hello,

It should be a backslash, not a slash => URL\SQLExpress

You can also use the IP port instead of the instance Name => use "tcp:publicIP, 65004" as Server Name.

Hi Dan, thank you for your answer. I have used MS Internet Explorer to connect to SQL Server, which apparently I should have not. Now I'm trying SQL Management Studio instead, using the format 'url\sqlexpress'. I received the error 'A network-related or instance-specific error'. Best regards.  Prof. Dr. Said El Noshokaty

• Edited by Prof. Dr. Said El Noshokaty Tuesday, February 03, 2015 12:10 PM I have used wrong application

Hi Olaf, thank you for your answer. I have used MS Internet Explorer to connect to SQL Server, which apparently I should have not. Now I'm trying SQL Management Studio instead, using the format 'url\sqlexpress'. I rceived the error 'A network-related or instance-specific error'. Best regards. Prof. Dr. Said El Noshokaty

  

Have you tried using the IP address + port?

Hi Olaf, yes, I have tried  URL + port. I received same error with different detail. Detail says 'Err 0: No connection could be made because the target machine actively refused it'. With 'URL\SQLExpress', detail says: 'Err 26: Error locating server / instance specified'. Best regards.  Prof. Dr. Said El Noshokaty  

It may be either one of the following:

1. It may be the firewall blocking the connection. You are not using default Port "1433". But, You have used 65004 Port.
2. The hosting service is not listening on that port

• Edited by SQLServerBuddy Tuesday, February 03, 2015 6:50 PM
• Proposed as answer by Michelle LiMicrosoft contingent staff Wednesday, February 04, 2015 12:29 PM

By "url" do you mean only the server name or IP address? 

Hi Dan, I mean the public IP address. I'm trying to connect via internet. No problem in connecting via local IP. Best regards. Prof. Dr. Said El Noshokaty.

Hi Michelle, in Windows firewall all TCP and UDP ports are allowed. Same for sqlservr.exe and sqlbrowser.exe. I tried also the connection with firewall and antivurus turned off. When I run TCPView.exe, sqlservr.exe on port '65004' is TCP listening, and services.exe on port '1095' is TCP listening. When I tried the default port '1433' instead of '65004' for SQLExpress, stop and then start server services, I received the error 'The request failed or the service did not respond in a timely fashion'. Best regards. Prof. Dr. Said El Noshokaty

N.B. When I run SQL Server Agent for SQLExpress, I receive the error 'The service cannot be started either because it is disabled or because it has no enabled devices associated with it'. This does not affect SQLExpress to be connected locally. I do not know whether it affects SQLExpress to be connected via the internet. By the way, no problem when SQL Server Agent for MSSQLSERVER (default server) is run.


• Edited by Prof. Dr. Said El Noshokaty Friday, February 06, 2015 7:08 PM New information

Hi Dan, I'm still waiting more insights on my problem. Latest is that I installed SQL Server 2008 on another i3 PC on same LAN running same Win 7. I tried to connect from first PC to the second, now targeting the default instance on port 1433. Using public IP address only, Ireceived 'Err 40 - Could not open a connection to SQL Server'. Using public IP address + 1433, I got 'ERR 0 - No connection could be made because the target machine actively refused it'. On the targeted PC, where both firewall and antivirus are turned off, Netstat shows for the PC local IP address established connections only between SQL Server (port 1433) and both Management Studio and Reporting Services, and between antivirus and unknown IP addresses (77.234.44.65:80, 216.58.211.72:443, 2.19.30.13:443). Best regards. Prof. Dr. Said El Noshokaty 

Hi Michelle, please refer to my reply to community member: Dan Guzman, SQL Server MVP. Best regards. Prof. Dr. Said El Noshokaty

 

• Edited by Prof. Dr. Said El Noshokaty 19 hours 45 minutes ago re-editing

Hi Olaf, please refer to my reply to community member: Dan Guzman, SQL Server MVP. Best regards. Prof. Dr. Said El Noshokaty.