Error 17 SQL SERVER

Cannot enable TCP/IP on SQL Server 2000 when switching to a new server.
Dynamic port - Client Configuration error cannot connect.
Help
--
Regards,
JamieMore Info... DMZ server cannot be accessed from server inside DMZ. Called
for support on this one. Old DMZ was aliased in code using a name that was
different from the actual server name. Once the actual server name was used
as an alias the TCP/IP worked fine. To enable the alias, a second server
needed to be setup using an ole db alias.
--
Regards,
Jamie
"thejamie" wrote:
> Cannot enable TCP/IP on SQL Server 2000 when switching to a new server.
> Dynamic port - Client Configuration error cannot connect.
> Help
> --
> Regards,
> Jamiesql

Error 15004 Name cannot be null

I made a publisher for marge replication via ISDN Dialup connected server and registered server x to y and y to x with TCP/IP.

I can see both data on each other.

I publish one database and try to configure pull subscription on 2nd one got following error.

SQL Server enterprise manager could not create a pull asubscription to publication pmst

Error 15004 Name cannot be null

Thanks to all of youYou've got a relatively unusual configuration for replication. I don't know of anywhere to look for specific details to help you, but I've got some ideas.

I'd start by synchronizing the clocks on both servers, preferably to a common time source or better yet synch one machine's clock to the other's clock. Open a copy of SQL Profiler on both machines and trace with no filtering (so you can see every command executed against the server). Try to re-subscribe again. The last command in each profile is suspect, the one with the later timestamp is likely to be the source of your problem.

You are probably looking for an empty string or NULL string parameter. Once you find it, you'll have to post what you find and maybe one of us can help you.

-PatP|||Do "SELECT @.@.SERVERNAME" on both servers.

Error - SQL Server requires Encryption On

Hello All,

I have a commercial application built for Pocket PC's that connects to SQL Server 2005 via TCP/IP over wireless networks. In installations for our sales people we installed SQL 2005 Express on their notebooks for demonstrations. In one of these installs we are getting the following error message: "An error occurred - SQL Server requires Encryption On". We do not use encrypted connections and I have verified encryption is turned off in the Options tab in SQL 2005 login screens.

Here is the connection string we use in the app.config file on the Pocket PC's:
<add key="connStr" value="Data Source=192.168.0.19,1433;Initial Catalog=SQL0018;User ID = User01;Password=PW01"/>

Other apps on the notebook are connecting to this same SQL Server without any issues. Thank you in advance for any help here,

Jack

Hi Jack,

The registry key that controls this behaviour is below (assuming express is the first SQLServer you installed on the machine). If that key is set to 1, then set it to 0 and it should fix your problem.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\ForceEncryption

If it was set to 1, I am not sure how that came to pass. I also do not know where the gui component that manipulates this key resides, maybe someone can offer insight here.

Of course the real fun starts if it isn't set to 1.

I hope this helps!

John (MSFT)

|||http://msdn.microsoft.com/msdnmag/issues/01/06/sqlce/ fyi too.|||

Thank you John, that was it. I apologize for taking so long to respond but my sales person is in L.A. and I am in Florida and with the long weekend we couldnt connect until late yesterday.

Would love to know how that got set in the first place though. That was a tough one to find. Thanks again.

Jack