when i tried to install the lastest MSDE release A, it has this error. How should I solve it?
See the following KB article for more info on this problem:
http://support.microsoft.com/?id=838302
You can avoid the problem by (temporarily) changing your default system
locale to a locale that isn't in the list in that article, reboot, then
retry the installation. You can also avoid the problem by passing the
COLLATION command line parameter to setup (e.g.
"COLLATION=SQL_Latin1_General_CP1_CI_AS".
Bart
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Thread-Topic: Cannot determine default collation
thread-index: AcRS8jxBIFmv0lEuTbeceZiciXUOYg==
X-WBNR-Posting-Host: 61.10.7.203
From: =?Utf-8?B?U2Fu?= <San@.discussions.microsoft.com>
Subject: Cannot determine default collation
Date: Tue, 15 Jun 2004 09:03:01 -0700
Lines: 1
Message-ID: <9101766C-F170-4F20-A300-554889E2A0C2@.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.sqlserver.msde
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 127.0.0.1
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGXA01.phx.gbl!TK2MSFTNG
XA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.msde:15056
X-Tomcat-NG: microsoft.public.sqlserver.msde
when i tried to install the lastest MSDE release A, it has this error.
How should I solve it?
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Sunday, March 25, 2012
Thursday, March 22, 2012
cannot deliver sp_repldropcolum schema change
Hello
As our customers use our product often offline, we implemted a sql server
2000 merge replication with msde anonymous subscribers.
With the new product release go some schemachanges, which we implemted with
sp_repladdcolumn and sp_repldropcolumn (e.g." exec sp_repldropcolumn
@.source_object = 'verlauf_ver', @.column = 'c_mandant',
@.force_reinit_subscription = 1").
I can complete the changes on the publisher without errors (only the
warning, that you can synchronize with sql 2000 and above only).
When I synchronize the subscriber, firstly it seems to work, but the it
stops and says, it cannot deliver the changes "exec sp_repldropcolumn..."
Are there any ideas?
Is it possible, there's a kind of restriction on the amount of changes?
Thanks for any help
Regards
Please can you post up the exact error message. Also you might want to
enable logging and see if that gives any more info (and post that up as well
please).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hello Paul
At the moment, I'm checking out something else.
But after that, I'll do what you ask me for. But can you tell me, how I can
enable Logging? And where to find this Log?
Thanks a lot
Aline
"Paul Ibison" wrote:
> Please can you post up the exact error message. Also you might want to
> enable logging and see if that gives any more info (and post that up as well
> please).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||Hi Aline - this article explains it well:
http://support.microsoft.com/?id=312292
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hello Paul
Thanks for the Link, which was very useful. I didn't realise, I could enable
such a logging (though I've already read about it before)
So here's the statement:
exec sp_repldropcolumn @.source_object = 'c_controldef', @.column = 'mandid',
@.force_invalidate_snapshot = 1, @.force_reinit_subscription = 1
and here's the log (in German, sorry):
Microsoft SQL Server-Merge-Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Percent Complete: 0
Verbindung mit Abonnent 'winxpsp2\syseca'
Connecting to Abonnent 'winxpsp2\syseca.challenge'
Server: winxpsp2\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:53]winxpsp2\syseca.challenge: {call sp_MSgetversion }
[16.11.2006 13:55:53]winxpsp2\syseca.challenge: {?=call
sp_helpsubscription_properties (N'vistatestpc\syseca', N'challenge',
N'challenge')}
Distributor security mode: 0, login name: rai_application, password: ********.
Percent Complete: 0
Verbindung mit Verteiler 'vistatestpc\syseca'
Connecting to Verteiler 'vistatestpc\syseca.'
Server: vistatestpc\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: guest
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:53]vistatestpc\syseca.: {call sp_MSgetversion }
[16.11.2006 13:55:53]vistatestpc\syseca.: {call sp_helpdistpublisher
(N'vistatestpc\syseca') }
[16.11.2006 13:55:53]vistatestpc\syseca.distribution: select datasource,
srvid from master..sysservers where upper(srvname) =
upper(N'vistatestpc\syseca')
[16.11.2006 13:55:53]vistatestpc\syseca.distribution: {call
sp_MSadd_merge_anonymous_agent(N'0', N'challenge', N'challenge',
N'challenge', N'winxpsp2\syseca',?, 667)}
[16.11.2006 13:55:53]vistatestpc\syseca.distribution: {call
sp_MShelp_profile (2, 4, N'')}
Percent Complete: 0
Connecting to Verleger 'vistatestpc\syseca.challenge'
Initialisiert
Percent Complete: 1
Verbindung mit Verleger 'vistatestpc\syseca'
Server: vistatestpc\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:53]vistatestpc\syseca.challenge: set nocount on declare
@.dbname sysname select @.dbname = db_name() declare @.collation nvarchar(255)
select @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Connecting to Verleger 'vistatestpc\syseca.challenge'
Server: vistatestpc\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:54]vistatestpc\syseca.challenge: {call sp_MSgetversion }
Percent Complete: 3
Ruft Publikationsinformationen ab
Percent Complete: 4
Ruft Abonnementinformationen ab
Connecting to Abonnent 'winxpsp2\syseca.challenge'
Server: winxpsp2\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
Server: winxpsp2\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:54]vistatestpc\syseca.challenge: exec sp_datatype_info 0, 3
Percent Complete: 4
[16.11.2006 13:55:54]winxpsp2\syseca.challenge: exec sp_repldropcolumn
'[dbo].[c_controldef]', 'mandid', 1
Eine Spalte wurde zur replizierten Tabelle hinzugefügt oder aus dieser
gel?scht.
Das Schemaskript 'exec sp_repldropcolumn '[dbo].[c_controldef]', 'mandid',
1' konnte nicht an den Abonnenten weitergegeben werden.
Percent Complete: 0
Das Schemaskript 'exec sp_repldropcolumn '[dbo].[c_controldef]', 'mandid',
1' konnte nicht an den Abonnenten weitergegeben werden.
Percent Complete: 0
Category:NULL
Source: Mergereplikationsprovider
Number: -2147201001
Message: Das Schemaskript 'exec sp_repldropcolumn '[dbo].[c_controldef]',
'mandid', 1' konnte nicht an den Abonnenten weitergegeben werden.
at the end it says: The schemascript sp_repldropcolumn
'[dbo].[c_controldef]', 'mandid', 1' couldn't be delivered to the subscriber
Unfortunately it doesn't tell my why.
There are a lot of different changes before which work fine. And afterwards
are also 46 sp_repldropcolumn.
Strangely, if I comment out these 47 sp_repldropcolumn's, update the
publisher, synchronize the subscriber, and then update the publisher with
these 47 47 sp_repldropcolumn's and synch the subscriber, it works...
As the product is install at more than 100 customers, I need something
automatic.
Any further help?
Thanks
Aline
|||My guess is that something references the column on the subscriber. Please
take a look at this article and see if it applies:
http://support.microsoft.com/kb/816755
One way to test this would be to restore a backup of the subscriber database
to another database nema and try to drop the column directly and hopefully
you wont be able to and will get a message referring to the constraint that
prevents the drop. If you can get this, you can drop the constraint using
sp_addscriptexec (assuming it is nothing to do with a filter).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Paul
It still doesn't work correctly. I've got the following error, when adding a
script:
Script:
....
exec sp_addscriptexec @.publication = N'challenge',
@.scriptfile='c:\programme\syseca\DB-Scripts\Replikation\ReplicationScripts\DropConstra ints.sql'
exec sp_repldropcolumn @.source_object = 'c_controldef', @.column = 'mandid',
@.force_invalidate_snapshot = 1, @.force_reinit_subscription = 1
...
error:
xpsql.cpp: Fehler 997 von GetProxyAccount in Zeile 604
Meldung 21330, Ebene 16, Status 1, Server VISTATESTPC\SYSECA, Prozedur
sp_MScopyscriptfile, Zeile 31
Fehler beim Erstellen eines Unterverzeichnisses unter dem
Replikationsarbeitsverzeichnis. (md
"\\vistatestpc\snapshot\20061116210031497")
--> error while building subdirectory...
I think, the path should be something like this:
"\\vistatestpc\snapshot\unc\SERVERNAME$INSTANCENAM E_PUBLICATION_DATABASE\20061116210031497"
Shouldn't the distributor handle this? By the way: Distributor and Publisher
are installed on the same server and dbms.
what can I do?
Thanks a lot
Aline
|||I'm not familiar with the normal log messages, but it looks like you have
configured a proxy account. Is the proxy account that the merge agent is
using in the Local admins group on the server? (or at least set up with the
necessary rights)? (it's generally much easier to have the merge agent run
as the sql server agent although SQL Serever 2005 uses these proxies by
default) Also, is there enough space on the server?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||sql server agent runs as a local administrator. so I think it has all
necessary rights.
what confuses me is, why does it try to make a new folder and why are these
typical "unc\servername..." missing in the path?
|||I'll take a proper look tomorrow when I get back to work if nobody's solved
it by then.
Before that, can you confirm is you are using a proxy account for
non-sysadmins or not, and that the account (if you are) has the necessary
rights.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
As our customers use our product often offline, we implemted a sql server
2000 merge replication with msde anonymous subscribers.
With the new product release go some schemachanges, which we implemted with
sp_repladdcolumn and sp_repldropcolumn (e.g." exec sp_repldropcolumn
@.source_object = 'verlauf_ver', @.column = 'c_mandant',
@.force_reinit_subscription = 1").
I can complete the changes on the publisher without errors (only the
warning, that you can synchronize with sql 2000 and above only).
When I synchronize the subscriber, firstly it seems to work, but the it
stops and says, it cannot deliver the changes "exec sp_repldropcolumn..."
Are there any ideas?
Is it possible, there's a kind of restriction on the amount of changes?
Thanks for any help
Regards
Please can you post up the exact error message. Also you might want to
enable logging and see if that gives any more info (and post that up as well
please).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hello Paul
At the moment, I'm checking out something else.
But after that, I'll do what you ask me for. But can you tell me, how I can
enable Logging? And where to find this Log?
Thanks a lot
Aline
"Paul Ibison" wrote:
> Please can you post up the exact error message. Also you might want to
> enable logging and see if that gives any more info (and post that up as well
> please).
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
>
>
|||Hi Aline - this article explains it well:
http://support.microsoft.com/?id=312292
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hello Paul
Thanks for the Link, which was very useful. I didn't realise, I could enable
such a logging (though I've already read about it before)
So here's the statement:
exec sp_repldropcolumn @.source_object = 'c_controldef', @.column = 'mandid',
@.force_invalidate_snapshot = 1, @.force_reinit_subscription = 1
and here's the log (in German, sorry):
Microsoft SQL Server-Merge-Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Percent Complete: 0
Verbindung mit Abonnent 'winxpsp2\syseca'
Connecting to Abonnent 'winxpsp2\syseca.challenge'
Server: winxpsp2\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:53]winxpsp2\syseca.challenge: {call sp_MSgetversion }
[16.11.2006 13:55:53]winxpsp2\syseca.challenge: {?=call
sp_helpsubscription_properties (N'vistatestpc\syseca', N'challenge',
N'challenge')}
Distributor security mode: 0, login name: rai_application, password: ********.
Percent Complete: 0
Verbindung mit Verteiler 'vistatestpc\syseca'
Connecting to Verteiler 'vistatestpc\syseca.'
Server: vistatestpc\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: guest
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:53]vistatestpc\syseca.: {call sp_MSgetversion }
[16.11.2006 13:55:53]vistatestpc\syseca.: {call sp_helpdistpublisher
(N'vistatestpc\syseca') }
[16.11.2006 13:55:53]vistatestpc\syseca.distribution: select datasource,
srvid from master..sysservers where upper(srvname) =
upper(N'vistatestpc\syseca')
[16.11.2006 13:55:53]vistatestpc\syseca.distribution: {call
sp_MSadd_merge_anonymous_agent(N'0', N'challenge', N'challenge',
N'challenge', N'winxpsp2\syseca',?, 667)}
[16.11.2006 13:55:53]vistatestpc\syseca.distribution: {call
sp_MShelp_profile (2, 4, N'')}
Percent Complete: 0
Connecting to Verleger 'vistatestpc\syseca.challenge'
Initialisiert
Percent Complete: 1
Verbindung mit Verleger 'vistatestpc\syseca'
Server: vistatestpc\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:53]vistatestpc\syseca.challenge: set nocount on declare
@.dbname sysname select @.dbname = db_name() declare @.collation nvarchar(255)
select @.collation = convert(nvarchar(255), databasepropertyex(@.dbname,
N'COLLATION')) select collationproperty(@.collation, N'CODEPAGE') as
'CodePage', collationproperty(@.collation, N'LCID') as 'LCID',
collationproperty(@.collation, N'COMPARISONSTYLE') as 'ComparisonStyle'
Connecting to Verleger 'vistatestpc\syseca.challenge'
Server: vistatestpc\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:54]vistatestpc\syseca.challenge: {call sp_MSgetversion }
Percent Complete: 3
Ruft Publikationsinformationen ab
Percent Complete: 4
Ruft Abonnementinformationen ab
Connecting to Abonnent 'winxpsp2\syseca.challenge'
Server: winxpsp2\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
Server: winxpsp2\syseca
DBMS: Microsoft SQL Server
Version: 08.00.0760
user name: rai_application
API conformance: 2
SQL conformance: 1
transaction capable: 2
read only: N
identifier quote char: "
non_nullable_columns: 1
owner usage: 31
max table name len: 128
max column name len: 128
need long data len: Y
max columns in table: 1024
max columns in index: 16
max char literal len: 524288
max statement len: 524288
max row size: 524288
[16.11.2006 13:55:54]vistatestpc\syseca.challenge: exec sp_datatype_info 0, 3
Percent Complete: 4
[16.11.2006 13:55:54]winxpsp2\syseca.challenge: exec sp_repldropcolumn
'[dbo].[c_controldef]', 'mandid', 1
Eine Spalte wurde zur replizierten Tabelle hinzugefügt oder aus dieser
gel?scht.
Das Schemaskript 'exec sp_repldropcolumn '[dbo].[c_controldef]', 'mandid',
1' konnte nicht an den Abonnenten weitergegeben werden.
Percent Complete: 0
Das Schemaskript 'exec sp_repldropcolumn '[dbo].[c_controldef]', 'mandid',
1' konnte nicht an den Abonnenten weitergegeben werden.
Percent Complete: 0
Category:NULL
Source: Mergereplikationsprovider
Number: -2147201001
Message: Das Schemaskript 'exec sp_repldropcolumn '[dbo].[c_controldef]',
'mandid', 1' konnte nicht an den Abonnenten weitergegeben werden.
at the end it says: The schemascript sp_repldropcolumn
'[dbo].[c_controldef]', 'mandid', 1' couldn't be delivered to the subscriber
Unfortunately it doesn't tell my why.
There are a lot of different changes before which work fine. And afterwards
are also 46 sp_repldropcolumn.
Strangely, if I comment out these 47 sp_repldropcolumn's, update the
publisher, synchronize the subscriber, and then update the publisher with
these 47 47 sp_repldropcolumn's and synch the subscriber, it works...
As the product is install at more than 100 customers, I need something
automatic.
Any further help?
Thanks
Aline
|||My guess is that something references the column on the subscriber. Please
take a look at this article and see if it applies:
http://support.microsoft.com/kb/816755
One way to test this would be to restore a backup of the subscriber database
to another database nema and try to drop the column directly and hopefully
you wont be able to and will get a message referring to the constraint that
prevents the drop. If you can get this, you can drop the constraint using
sp_addscriptexec (assuming it is nothing to do with a filter).
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Paul
It still doesn't work correctly. I've got the following error, when adding a
script:
Script:
....
exec sp_addscriptexec @.publication = N'challenge',
@.scriptfile='c:\programme\syseca\DB-Scripts\Replikation\ReplicationScripts\DropConstra ints.sql'
exec sp_repldropcolumn @.source_object = 'c_controldef', @.column = 'mandid',
@.force_invalidate_snapshot = 1, @.force_reinit_subscription = 1
...
error:
xpsql.cpp: Fehler 997 von GetProxyAccount in Zeile 604
Meldung 21330, Ebene 16, Status 1, Server VISTATESTPC\SYSECA, Prozedur
sp_MScopyscriptfile, Zeile 31
Fehler beim Erstellen eines Unterverzeichnisses unter dem
Replikationsarbeitsverzeichnis. (md
"\\vistatestpc\snapshot\20061116210031497")
--> error while building subdirectory...
I think, the path should be something like this:
"\\vistatestpc\snapshot\unc\SERVERNAME$INSTANCENAM E_PUBLICATION_DATABASE\20061116210031497"
Shouldn't the distributor handle this? By the way: Distributor and Publisher
are installed on the same server and dbms.
what can I do?
Thanks a lot
Aline
|||I'm not familiar with the normal log messages, but it looks like you have
configured a proxy account. Is the proxy account that the merge agent is
using in the Local admins group on the server? (or at least set up with the
necessary rights)? (it's generally much easier to have the merge agent run
as the sql server agent although SQL Serever 2005 uses these proxies by
default) Also, is there enough space on the server?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||sql server agent runs as a local administrator. so I think it has all
necessary rights.
what confuses me is, why does it try to make a new folder and why are these
typical "unc\servername..." missing in the path?
|||I'll take a proper look tomorrow when I get back to work if nobody's solved
it by then.
Before that, can you confirm is you are using a proxy account for
non-sysadmins or not, and that the account (if you are) has the necessary
rights.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
Friday, February 24, 2012
Cannot connect to SQL Server or MSDE when enable ICF
Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPH
Hi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPH
Hi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
Cannot connect to SQL Server or MSDE when enable ICF
Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the ICF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I don´t know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I have installed both MSDE and SQL server on my machine, while I test my application from another machine my App cannot connect to my machine. Then I think the problem is because the ICF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I don´t know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
Cannot connect to SQL Server or MSDE when enable ICF
Hi,
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I hav
e installed both MSDE and SQL server on my machine, while I test my applicat
ion from another machine my App cannot connect to my machine. Then I think t
he problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I hav
e installed both MSDE and SQL server on my machine, while I test my applicat
ion from another machine my App cannot connect to my machine. Then I think t
he problem is because the I
CF.
Is there anyone know how to configure the port for SQL server or MSDE?
Cheer,
KPHHi,
when you look in the properties of your server there you can see the port,
the server is using.
I dont know if the icf can be configured so that a special port is open.
Perhaps you should use zonealarm for this or an other firewall which can be
more configured.
Or disable the icf, if possible.
I think the standardport is 1433.
Regards
Alexander
"KPH" <KPH@.discussions.microsoft.com> schrieb im Newsbeitrag
news:2D296E26-38B1-48A4-8414-9D8C84A366C7@.microsoft.com...
> Hi,
> I enable Internet Connection Firewall (ICF) on my machine (WinXP SP1). I
have installed both MSDE and SQL server on my machine, while I test my
application from another machine my App cannot connect to my machine. Then I
think the problem is because the ICF.
> Is there anyone know how to configure the port for SQL server or MSDE?
> Cheer,
> KPH
Cannot connect to Sql Server 2005 Express. Any idea why ?
Hi everybody
I have a system with :
WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed SqlServer
2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise Manager
from SQLServer 2000 to connect to it (manual says I can) but with no
success. I tried to log on with windows authentication as well as with Sql
authentication . I tried the following names to connect :
(local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
so on but never got connected. It always say that the
SQL Server does not exist or Access denied.
I checked in the services where it is set to automatic and is running. I
also stopped and restarted but with no success. What i am missing ?
At the end I uninstalled everything and reinstalled only Framework 2.0 and
Sql Server 2005 Beta but having the same problem.
Anyone know how to fix this ?
Thanks in advance
Raja
hi, Raja,
"Ing. Rajesh Kumar" <iambad(Without This)@.post.cz> ha scritto nel messaggio
news:OFSx33CcEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi everybody
> I have a system with :
> WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed
SqlServer
> 2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise
Manager
> from SQLServer 2000 to connect to it (manual says I can) but with no
> success. I tried to log on with windows authentication as well as with Sql
> authentication . I tried the following names to connect :
> (local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
> so on but never got connected. It always say that the
> SQL Server does not exist or Access denied.
> I checked in the services where it is set to automatic and is running. I
> also stopped and restarted but with no success. What i am missing ?
> At the end I uninstalled everything and reinstalled only Framework 2.0 and
> Sql Server 2005 Beta but having the same problem.
frorm microsoft.private.sqlserver2005.express newsgroup:
1. Enable Protocols
a. Launch SQL Computer Manager
b. Expand "Server Network Configuration"
c. Expand Protocols for "SQLEXPRESS"
d. Enable Np (for local access)
e. Enable TCP (for remote access)
2. Restart SQL Express
a. can be done from either SQL Computer Manager, Services applet, or
command line
3. Start SQL Browser service from Service applet or command line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I have a system with :
WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed SqlServer
2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise Manager
from SQLServer 2000 to connect to it (manual says I can) but with no
success. I tried to log on with windows authentication as well as with Sql
authentication . I tried the following names to connect :
(local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
so on but never got connected. It always say that the
SQL Server does not exist or Access denied.
I checked in the services where it is set to automatic and is running. I
also stopped and restarted but with no success. What i am missing ?
At the end I uninstalled everything and reinstalled only Framework 2.0 and
Sql Server 2005 Beta but having the same problem.
Anyone know how to fix this ?
Thanks in advance
Raja
hi, Raja,
"Ing. Rajesh Kumar" <iambad(Without This)@.post.cz> ha scritto nel messaggio
news:OFSx33CcEHA.2908@.TK2MSFTNGP10.phx.gbl...
> Hi everybody
> I have a system with :
> WinXP Pro, MSDE 2000, Framework 2.0 beta. On top of it i installed
SqlServer
> 2005 Beta with Mixed Mode. I am using Query Analyzer and Enterperise
Manager
> from SQLServer 2000 to connect to it (manual says I can) but with no
> success. I tried to log on with windows authentication as well as with Sql
> authentication . I tried the following names to connect :
> (local)\SQLEXPRESS; COMP_NAME\SQLEXPRESS; SQLEXPRESS; MSSQL$SQLEXPRESS and
> so on but never got connected. It always say that the
> SQL Server does not exist or Access denied.
> I checked in the services where it is set to automatic and is running. I
> also stopped and restarted but with no success. What i am missing ?
> At the end I uninstalled everything and reinstalled only Framework 2.0 and
> Sql Server 2005 Beta but having the same problem.
frorm microsoft.private.sqlserver2005.express newsgroup:
1. Enable Protocols
a. Launch SQL Computer Manager
b. Expand "Server Network Configuration"
c. Expand Protocols for "SQLEXPRESS"
d. Enable Np (for local access)
e. Enable TCP (for remote access)
2. Restart SQL Express
a. can be done from either SQL Computer Manager, Services applet, or
command line
3. Start SQL Browser service from Service applet or command line
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Tuesday, February 14, 2012
Cannot connect to Named Instance of MSDE through Enterprise Mananger...
Hi- I am hoping someone can help me or shed some light on an issue I am having.
I have recently moved to a dedicated server with MSDE installed on it. The server was installed as the default instance and I changed the password to the SA account. I then copied my entire SA database over to the new MSDE database and everything was working good so it seemed. I believe at some point during copying of the data, or after installalling an application the SA account begain to fail and the password was changed. I have no idea how this happened, and better yet when I tried to change it logged in as the administrator with OSQL it told me I did not have sysadmin rights (I tried multiple Windows NT Auth logins and still got this error trying to change the password).
So... I reinstalled MSDE and created a named instane. I then attached the mdf/ldf files to my named instance and am able to connect ok from a .NET application directly to my new MSDE Named Instance database. Sounds like everything is great right? Not really, I can't figure out how to connect through enterprise manager and its driving me CRAZY!
1. I CAN connect via any .NET app and a connection string
2. I CAN connect via the server with OSQL
3. I CAN connect via the web based enterprise manager (which is very limited and a freeware ASP app).
4. I CANNOT connect via enterprise manager. I have verified from the (SVRNETCN.EXE utility) that the port is open and have tried connecting to MY_IPADDRESS\NAMEDINSTANCE\ but no luck.
One additional side note, when I wasn't using a named instance I had no problems connecting through enterprise manager to my default MSDE instance.
Any help would be grealy appriciated, this is driving me nuts!
-Chad
Ok, I got this figured out. For anyone else that has this issue here is what solved my problem.
Within the client utility create an alias named YourDomainOrIPAddress\NamedInstance and make sure to open up the TCP port with the SVRNETCN.EXE on the server. Also, enabled TCP/IP on the client utility and make sure its the same port.
Additionally within Enterprise Manager I kept trying YourDomainOrIPAdress\NamedInstance:Port# instead what you need to do is try YourDomainOrIPAddress,Port# (Common instead of semi colon).
-Chad
cannot connect to named instance of msde
I installed a named instance of MSDE SP4. It seemed to go OK, and no errors
were reported.
The instance is listed in the computer's services, and it is running.
However, neither the computer name nor the new MSDE instance is listed in
the SQL Server Service Manager (although an instance on a networked computer
is listed). And I cannot connect via osql.
Any suggestions?
hi Paul,
Paul Pedersen wrote:
> I installed a named instance of MSDE SP4. It seemed to go OK, and no
> errors were reported.
> The instance is listed in the computer's services, and it is running.
> However, neither the computer name nor the new MSDE instance is
> listed in the SQL Server Service Manager (although an instance on a
> networked computer is listed). And I cannot connect via osql.
> Any suggestions?
if you can not connect from remote client, it can be depending on disabled
network protocols (default for MSDE installation, you can bypass at install
time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
time, using the Server Network Utility [svrnetcn.exe] to enable the
desired/required network protocol) or, for instance, firewall/network
problems (Windows XP sp2 Firewall requires to provide an exception for the
service or to the port)..
as you are reporting the SQL Server Service Manager does not list the
instances, I'd guess it's becouse the very first scenario
(http://support.microsoft.com/default...b;EN-US;814132)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||That did the trick. Thank you!
Is there some reason that disabling the protocols is the default? It seems
to me that without that, MSDE is completely unusable. Like I said before, I
couldn't even get osql to connect. Maybe that's a different problem.
One note: the Server Network Utility says that changes will take effect
after the service is restarted, but restarting MSDE didn't make it work. I
had to reboot the computer
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
> install time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later,
> at run time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> That did the trick. Thank you!
> Is there some reason that disabling the protocols is the default? It
> seems to me that without that, MSDE is completely unusable. Like I
> said before, I couldn't even get osql to connect. Maybe that's a
> different problem.
actually not... Microsoft provided a setup that should protect all "passive"
users from external malicious attacks (think of Slammer and the like) only
enabling trusted WinNT connections and disabling network protocols ...
and this is not a bad idea... always give the least required privilege
pattern :D:D
> One note: the Server Network Utility says that changes will take
> effect after the service is restarted, but restarting MSDE didn't
> make it work. I had to reboot the computer
stopping and restarding the service is usually enonght thought...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks again.
It took a fair amount of trial before I realized that to connect to a named
MSDE instance with osql, you have to preface the name with server\, even if
it's on the same machine.
Only one problem left. In testing, I uninstalled and reinstalled with
DISABLENETWORKPROTOCOLS=0. But the instance does not show up on the network.
In other words, I installed MSDE on Machine A. The Service Manager on
Machine A can see its own server, plus an instance of SQL Server on Machine
B. Machine B can see its own SQL Server instance, but cannot see the MSDE
instance on Machine A.
On Machine A, the Network Utility says the tcp/ip default port is 1059 (must
be some default, because I did not set it), and Hide Server is not checked.
Do you have suggestions about this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hk1c1Fhii6nU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> actually not... Microsoft provided a setup that should protect all
> "passive" users from external malicious attacks (think of Slammer and the
> like) only enabling trusted WinNT connections and disabling network
> protocols ...
> and this is not a bad idea... always give the least required privilege
> pattern :D:D
>
> stopping and restarding the service is usually enonght thought...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> On Machine A, the Network Utility says the tcp/ip default port is
> 1059 (must be some default, because I did not set it), and Hide
> Server is not checked.
it's not a default... Microsoft only got 1 unique TCP/IP port for SQL Server
assigned by IANA, port TCP/IP 1433... but named instances never listen to
that port that is "reserved" for default instances... so Microsoft embedded
an additional service in order to allow dynamic ports assignemen/resolution
for named instance, and the MDAC stack had to be modified as well to
integrate this feature (MDAC 2.6 and above)
for named instance you have 2 options... dynamic (default) or fixed static
port assignement..
loosely speaking, for dynamic port, when the specified instance starts, it
always searches for an unused port (actually it always uses the very same
port, if free)... the SQL Server Resolution Service, listening on UDP 1434
port, intercepts all remote connections to the instances, asks the instance
for it's used port, and redirects all connections to that specific port,
adding some little overhead to the traffic...
again, very very loosely speaking, the client makes a query, which is
reloaded by the MDAC stack to the appropriate network protocol [we are
talking about TCP/IP], that intiates the connection over a random tcp port
greater than 1024 to destination port; the listener service is the first
hand-shaker and intercepts the foreign call, queries the instance for it's
used port and negotiates a TCP/IP port for the 2 end points...
for a static assigned port, the listener on UDP 1434 port is not required,
but you have to map a server alias on each remote client pointing to the
correct fixed assigned port.. and again, the client intiates the connection
over a random tcp port greater than 1024 to destination port (say 1059). The
Subscriber should be allowed to make inbound (ANY) connections to
{say 1059} on a random port. The Publisher should be allowed to establish
outgoing connections to the subscriber from (ANY) to {say 1059}...
> Do you have suggestions about this?
>
WinXP sp2 or personal firewall?
the Windows XP sp2 integrated Firewall closes all ports... you have to add
an exception for that in order to allow external access,
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
http://support.microsoft.com/?id=841249 ,
http://support.microsoft.com/default.aspx?kbid=839980
please excuse my poor english... hope it's understandable
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
I am having the same problem, but I am using Enterprise Manager on the same
machine where the named instance is running. What can I do, please?!
TIA
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Sorry, I forgot to mention that I am using win2000p for dev and win2000
server for production
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
dl wrote:
> Hi Andrea
> I am having the same problem, but I am using Enterprise Manager on
> the same machine where the named instance is running. What can I do,
> please?!
> TIA
what kind of exception are you reported with?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your help. Your English is fine.
I don't know why, but it started working. I didn't change anything. But if
it's working, I won't complain.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hldmoFhkqsrU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> it's not a default... Microsoft only got 1 unique TCP/IP port for SQL
> Server assigned by IANA, port TCP/IP 1433... but named instances never
> listen to that port that is "reserved" for default instances... so
> Microsoft embedded an additional service in order to allow dynamic ports
> assignemen/resolution for named instance, and the MDAC stack had to be
> modified as well to integrate this feature (MDAC 2.6 and above)
> for named instance you have 2 options... dynamic (default) or fixed static
> port assignement..
> loosely speaking, for dynamic port, when the specified instance starts, it
> always searches for an unused port (actually it always uses the very same
> port, if free)... the SQL Server Resolution Service, listening on UDP 1434
> port, intercepts all remote connections to the instances, asks the
> instance for it's used port, and redirects all connections to that
> specific port, adding some little overhead to the traffic...
> again, very very loosely speaking, the client makes a query, which is
> reloaded by the MDAC stack to the appropriate network protocol [we are
> talking about TCP/IP], that intiates the connection over a random tcp port
> greater than 1024 to destination port; the listener service is the first
> hand-shaker and intercepts the foreign call, queries the instance for it's
> used port and negotiates a TCP/IP port for the 2 end points...
> for a static assigned port, the listener on UDP 1434 port is not required,
> but you have to map a server alias on each remote client pointing to the
> correct fixed assigned port.. and again, the client intiates the
> connection over a random tcp port greater than 1024 to destination port
> (say 1059). The Subscriber should be allowed to make inbound (ANY)
> connections to
> {say 1059} on a random port. The Publisher should be allowed to establish
> outgoing connections to the subscriber from (ANY) to {say 1059}...
>
> WinXP sp2 or personal firewall?
> the Windows XP sp2 integrated Firewall closes all ports... you have to add
> an exception for that in order to allow external access,
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
> http://support.microsoft.com/?id=841249 ,
> http://support.microsoft.com/default.aspx?kbid=839980
> please excuse my poor english... hope it's understandable
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
were reported.
The instance is listed in the computer's services, and it is running.
However, neither the computer name nor the new MSDE instance is listed in
the SQL Server Service Manager (although an instance on a networked computer
is listed). And I cannot connect via osql.
Any suggestions?
hi Paul,
Paul Pedersen wrote:
> I installed a named instance of MSDE SP4. It seemed to go OK, and no
> errors were reported.
> The instance is listed in the computer's services, and it is running.
> However, neither the computer name nor the new MSDE instance is
> listed in the SQL Server Service Manager (although an instance on a
> networked computer is listed). And I cannot connect via osql.
> Any suggestions?
if you can not connect from remote client, it can be depending on disabled
network protocols (default for MSDE installation, you can bypass at install
time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
time, using the Server Network Utility [svrnetcn.exe] to enable the
desired/required network protocol) or, for instance, firewall/network
problems (Windows XP sp2 Firewall requires to provide an exception for the
service or to the port)..
as you are reporting the SQL Server Service Manager does not list the
instances, I'd guess it's becouse the very first scenario
(http://support.microsoft.com/default...b;EN-US;814132)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||That did the trick. Thank you!
Is there some reason that disabling the protocols is the default? It seems
to me that without that, MSDE is completely unusable. Like I said before, I
couldn't even get osql to connect. Maybe that's a different problem.
One note: the Server Network Utility says that changes will take effect
after the service is restarted, but restarting MSDE didn't make it work. I
had to reboot the computer
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
> install time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later,
> at run time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> That did the trick. Thank you!
> Is there some reason that disabling the protocols is the default? It
> seems to me that without that, MSDE is completely unusable. Like I
> said before, I couldn't even get osql to connect. Maybe that's a
> different problem.
actually not... Microsoft provided a setup that should protect all "passive"
users from external malicious attacks (think of Slammer and the like) only
enabling trusted WinNT connections and disabling network protocols ...
and this is not a bad idea... always give the least required privilege
pattern :D:D
> One note: the Server Network Utility says that changes will take
> effect after the service is restarted, but restarting MSDE didn't
> make it work. I had to reboot the computer
stopping and restarding the service is usually enonght thought...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks again.
It took a fair amount of trial before I realized that to connect to a named
MSDE instance with osql, you have to preface the name with server\, even if
it's on the same machine.
Only one problem left. In testing, I uninstalled and reinstalled with
DISABLENETWORKPROTOCOLS=0. But the instance does not show up on the network.
In other words, I installed MSDE on Machine A. The Service Manager on
Machine A can see its own server, plus an instance of SQL Server on Machine
B. Machine B can see its own SQL Server instance, but cannot see the MSDE
instance on Machine A.
On Machine A, the Network Utility says the tcp/ip default port is 1059 (must
be some default, because I did not set it), and Hide Server is not checked.
Do you have suggestions about this?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hk1c1Fhii6nU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> actually not... Microsoft provided a setup that should protect all
> "passive" users from external malicious attacks (think of Slammer and the
> like) only enabling trusted WinNT connections and disabling network
> protocols ...
> and this is not a bad idea... always give the least required privilege
> pattern :D:D
>
> stopping and restarding the service is usually enonght thought...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Paul,
Paul Pedersen wrote:
> On Machine A, the Network Utility says the tcp/ip default port is
> 1059 (must be some default, because I did not set it), and Hide
> Server is not checked.
it's not a default... Microsoft only got 1 unique TCP/IP port for SQL Server
assigned by IANA, port TCP/IP 1433... but named instances never listen to
that port that is "reserved" for default instances... so Microsoft embedded
an additional service in order to allow dynamic ports assignemen/resolution
for named instance, and the MDAC stack had to be modified as well to
integrate this feature (MDAC 2.6 and above)
for named instance you have 2 options... dynamic (default) or fixed static
port assignement..
loosely speaking, for dynamic port, when the specified instance starts, it
always searches for an unused port (actually it always uses the very same
port, if free)... the SQL Server Resolution Service, listening on UDP 1434
port, intercepts all remote connections to the instances, asks the instance
for it's used port, and redirects all connections to that specific port,
adding some little overhead to the traffic...
again, very very loosely speaking, the client makes a query, which is
reloaded by the MDAC stack to the appropriate network protocol [we are
talking about TCP/IP], that intiates the connection over a random tcp port
greater than 1024 to destination port; the listener service is the first
hand-shaker and intercepts the foreign call, queries the instance for it's
used port and negotiates a TCP/IP port for the 2 end points...
for a static assigned port, the listener on UDP 1434 port is not required,
but you have to map a server alias on each remote client pointing to the
correct fixed assigned port.. and again, the client intiates the connection
over a random tcp port greater than 1024 to destination port (say 1059). The
Subscriber should be allowed to make inbound (ANY) connections to
{say 1059} on a random port. The Publisher should be allowed to establish
outgoing connections to the subscriber from (ANY) to {say 1059}...
> Do you have suggestions about this?
>
WinXP sp2 or personal firewall?
the Windows XP sp2 integrated Firewall closes all ports... you have to add
an exception for that in order to allow external access,
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
http://support.microsoft.com/?id=841249 ,
http://support.microsoft.com/default.aspx?kbid=839980
please excuse my poor english... hope it's understandable
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
I am having the same problem, but I am using Enterprise Manager on the same
machine where the named instance is running. What can I do, please?!
TIA
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Sorry, I forgot to mention that I am using win2000p for dev and win2000
server for production
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hjoumFh9q50U1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> if you can not connect from remote client, it can be depending on disabled
> network protocols (default for MSDE installation, you can bypass at
install
> time providing the DISABLENETWORKPROTOCOLS=0 paramenter or later, at run
> time, using the Server Network Utility [svrnetcn.exe] to enable the
> desired/required network protocol) or, for instance, firewall/network
> problems (Windows XP sp2 Firewall requires to provide an exception for the
> service or to the port)..
> as you are reporting the SQL Server Service Manager does not list the
> instances, I'd guess it's becouse the very first scenario
> (http://support.microsoft.com/default...b;EN-US;814132)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi,
dl wrote:
> Hi Andrea
> I am having the same problem, but I am using Enterprise Manager on
> the same machine where the named instance is running. What can I do,
> please?!
> TIA
what kind of exception are you reported with?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thank you for your help. Your English is fine.
I don't know why, but it started working. I didn't change anything. But if
it's working, I won't complain.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3hldmoFhkqsrU1@.individual.net...
> hi Paul,
> Paul Pedersen wrote:
> it's not a default... Microsoft only got 1 unique TCP/IP port for SQL
> Server assigned by IANA, port TCP/IP 1433... but named instances never
> listen to that port that is "reserved" for default instances... so
> Microsoft embedded an additional service in order to allow dynamic ports
> assignemen/resolution for named instance, and the MDAC stack had to be
> modified as well to integrate this feature (MDAC 2.6 and above)
> for named instance you have 2 options... dynamic (default) or fixed static
> port assignement..
> loosely speaking, for dynamic port, when the specified instance starts, it
> always searches for an unused port (actually it always uses the very same
> port, if free)... the SQL Server Resolution Service, listening on UDP 1434
> port, intercepts all remote connections to the instances, asks the
> instance for it's used port, and redirects all connections to that
> specific port, adding some little overhead to the traffic...
> again, very very loosely speaking, the client makes a query, which is
> reloaded by the MDAC stack to the appropriate network protocol [we are
> talking about TCP/IP], that intiates the connection over a random tcp port
> greater than 1024 to destination port; the listener service is the first
> hand-shaker and intercepts the foreign call, queries the instance for it's
> used port and negotiates a TCP/IP port for the 2 end points...
> for a static assigned port, the listener on UDP 1434 port is not required,
> but you have to map a server alias on each remote client pointing to the
> correct fixed assigned port.. and again, the client intiates the
> connection over a random tcp port greater than 1024 to destination port
> (say 1059). The Subscriber should be allowed to make inbound (ANY)
> connections to
> {say 1059} on a random port. The Publisher should be allowed to establish
> outgoing connections to the subscriber from (ANY) to {say 1059}...
>
> WinXP sp2 or personal firewall?
> the Windows XP sp2 integrated Firewall closes all ports... you have to add
> an exception for that in order to allow external access,
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 ,
> http://support.microsoft.com/?id=841249 ,
> http://support.microsoft.com/default.aspx?kbid=839980
> please excuse my poor english... hope it's understandable
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Cannot connect to MSDE on SBS 2003
My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
Cannot connect to MSDE on SBS 2003
My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
Cannot connect to MSDE on a W2003 server
I have installed MSDE with SP3a with a instance name on a
Windwos Server 2003 Enterprise edition.
The install works fine.
I installed the client software on a W2k en W98 client
PC, the install work fine.
When i run the program, the program normaly sees the
servernaam and instance name.
This do'nt work on the Windows 2003 server. (2000 server
works fine)
Have enyone a idee?* Did you apply the SP3 version of MSDE? If not TCP will be disabled on
Windows 2003. You must apply SP3 before TCP connections (the default from a
remote client) will work.
* What error do you get when you try to connect?
* Do you get the same error from Query Analyzer, OSQL, and Enterprise
Manager or just from your application?
* If you force TCP, named pipes, or shared memory does it start working or
change the error?
* Do both remote and local connections fail for each protocol? For MSDE
2000 SP3 remote connections are disabled by default, you have to enable TCP
and/or named pipes on the server side before remote connections will work.
To Enable TCP/IP Sockets Server Net-Library
1. On the taskbar, click "Start", and then click "Run".
2. In the "Open" text box, type "svrnetcn.exe" (without the quotation
marks). Note: By default, the svrnetcn.exe is available in the
following folder: <Installation Drive>/Program Files/Microsoft SQL
Server/80/Tools/BINN
3. Click "OK".
4. In the "SQL Server Network Utility" dialog box, click "General" tab.
5. Click the desired instance of Microsoft SQL Server 2000 Desktop Engine
(Windows) or MSDE 2000 SP3a or SQL Server 2000 in the
"Instance(s) on this server" list.
6. In the "Disabled Protocols" list box, click "TCP/IP", and then click
"Enable".
7. In the "Enabled Protocols" list box, click "TCP/IP", and then click
"Properties".
8. In the "<Server Name> - TCP/IP" dialog box, in the "Default Port" text
box, type "0" (without the quotation marks), and then click "OK".
9. In the "SQL Server Network Utility" dialog box, click "OK". Note: You
may receive a message stating that the changes made will be saved, but will
take effect only after restarting the SQL Server service. In the "SQL
Server Network Utility" message box, click "OK".
10. Restart the SQL Server service of the instance of Microsoft SQL Server
2000 Desktop Engine (Windows) or MSDE 2000 SP3a or SQL Server 2000.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Windwos Server 2003 Enterprise edition.
The install works fine.
I installed the client software on a W2k en W98 client
PC, the install work fine.
When i run the program, the program normaly sees the
servernaam and instance name.
This do'nt work on the Windows 2003 server. (2000 server
works fine)
Have enyone a idee?* Did you apply the SP3 version of MSDE? If not TCP will be disabled on
Windows 2003. You must apply SP3 before TCP connections (the default from a
remote client) will work.
* What error do you get when you try to connect?
* Do you get the same error from Query Analyzer, OSQL, and Enterprise
Manager or just from your application?
* If you force TCP, named pipes, or shared memory does it start working or
change the error?
* Do both remote and local connections fail for each protocol? For MSDE
2000 SP3 remote connections are disabled by default, you have to enable TCP
and/or named pipes on the server side before remote connections will work.
To Enable TCP/IP Sockets Server Net-Library
1. On the taskbar, click "Start", and then click "Run".
2. In the "Open" text box, type "svrnetcn.exe" (without the quotation
marks). Note: By default, the svrnetcn.exe is available in the
following folder: <Installation Drive>/Program Files/Microsoft SQL
Server/80/Tools/BINN
3. Click "OK".
4. In the "SQL Server Network Utility" dialog box, click "General" tab.
5. Click the desired instance of Microsoft SQL Server 2000 Desktop Engine
(Windows) or MSDE 2000 SP3a or SQL Server 2000 in the
"Instance(s) on this server" list.
6. In the "Disabled Protocols" list box, click "TCP/IP", and then click
"Enable".
7. In the "Enabled Protocols" list box, click "TCP/IP", and then click
"Properties".
8. In the "<Server Name> - TCP/IP" dialog box, in the "Default Port" text
box, type "0" (without the quotation marks), and then click "OK".
9. In the "SQL Server Network Utility" dialog box, click "OK". Note: You
may receive a message stating that the changes made will be saved, but will
take effect only after restarting the SQL Server service. In the "SQL
Server Network Utility" message box, click "OK".
10. Restart the SQL Server service of the instance of Microsoft SQL Server
2000 Desktop Engine (Windows) or MSDE 2000 SP3a or SQL Server 2000.
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.
Cannot connect to MSDE from C# code
Hello everybody and happy holidays to all.
I'm new to C#, and I appologize for this basic question.
I am trying to connect to an SQL database from a very short C# program, which I found on the Microsoft site, demonstrating this subject.
Here is my setup:
Windows 2000 Professional
dotNET Framework 1.1 with sp1 installed
MSDE 2000
Note: I do not own nor do I have Visual Studio.NET of any kind installed.
I'm new to C#, and I appologize for this basic question.
I am trying to connect to an SQL database from a very short C# program, which I found on the Microsoft site, demonstrating this subject.
Here is my setup:
Windows 2000 Professional
dotNET Framework 1.1 with sp1 installed
MSDE 2000
Note: I do not own nor do I have Visual Studio.NET of any kind installed.
Now, here is what works:
osql -E -S localhost\vsdotnet
1>
And I can create and populate a database, which I called mydb.
Now, in my simple C# demo program I have this line
SqlConnection mycon = new SqlConnection("server=localhost;database=mydb;trusted_connection=true");
And the program compiles OK using "csc" command. But when I run it, I get this message:
Couldn't Open Connection to server=localhost;database=mydb;trusted_connection=true
Could anybody comment on what am I missing?
Thanks.The complete answer can't be given without knowing if you chose to use intgrated NT security or not during the MSDE installation. Either which way your connection string is incomplete.
If you installed MSDE using NT integrated security your connection string should also contain: Persist Security Info=False;Integrated Security=SSPI;
If not you will have to provide a username password pair such as:
uid=sa;pwd=secret;
Hope this helps
Cheers
Gary
Cannot connect to MSDE database from Enterprise Manager
Hello,
I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003 a
s the default instance.
MSDE has been installed with the following options:
[Options]
TARGETDIR="C:\Program Files\MSDE 2000\"
SAPWD="<My Password>"
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
I try to connect to this MSDE database from another machine where SQL Server
2000 3.0a is running, using the Enterprise Manager.
In Enterprise Manager I enter the IP-address of the server where the MSDE-da
tabase is running and choose the option "Connect using the SQl server login
information..." where I enter "sa" and "<My Password>", the same assigned to
MSDE during setup.
As result I always get the message: "SQL Server does not exist or access is
denied. ConnectionOpen (Connect())".
I don't have any more ideas about what might be wrong...
Can anybody help me please?Are you sure MSDE isn't a named instance (so you would enter <ip
address>\<instance name> )?
"Roberto Rocco" <roberto@.rocco.de> wrote in message
news:eHYPhUZ0DHA.3196@.TK2MSFTNGP11.phx.gbl...
Hello,
I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003
as the default instance.
MSDE has been installed with the following options:
[Options]
TARGETDIR="C:\Program Files\MSDE 2000\"
SAPWD="<My Password>"
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
I try to connect to this MSDE database from another machine where SQL Server
2000 3.0a is running, using the Enterprise Manager.
In Enterprise Manager I enter the IP-address of the server where the
MSDE-database is running and choose the option "Connect using the SQl server
login information..." where I enter "sa" and "<My Password>", the same
assigned to MSDE during setup.
As result I always get the message: "SQL Server does not exist or access is
denied. ConnectionOpen (Connect())".
I don't have any more ideas about what might be wrong...
Can anybody help me please?|||Hello Foo,
thank you for your fast reply. Yes, I am sure that it is the default
instance.
Meanwhile I made some other tests: Running the same MSDE installation on
another machine (Windows XP) with the same Options.ini file (same settings,
same password, etc.) works pretty well!!
So I guess it must be "something" on the Windows 2003 Server.
I checked if it has a firewall configured, but it has not.
Can some ports be disabled on the Windows 2003 Server?
Are there other places to check?
Roberto.
"Foo Man Chew" <foo@.man.chew> schrieb im Newsbeitrag
news:OHbGqBa0DHA.2580@.TK2MSFTNGP09.phx.gbl...
Server
server
is
Port 1433 was blocked on the Windows 2003 Server. After adjusting the Packet
Filter Policies to permit Port 1433 access I was able to connect to the MSDE
database.
Thanks all for your support.
Roberto.
"Roberto Rocco" <roberto@.rocco.de> schrieb im Newsbeitrag
news:OTXwf%23f0DHA.1532@.TK2MSFTNGP10.phx.gbl...
settings,
I have the same problem, I have changed the TCP/IP filtering under the
TCP/IP setting on the network adapter to 'Enable TCP/IP Filtering' and
set to 'Permit All' on all types, but it still doesn't work. Are you
talking about something else? If so can you post a short guide of what
to change and where it is found in the Windows 2003 maze.
Thanks
Best Regards
Andrew.
da644
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message238297.html
I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003 a
s the default instance.
MSDE has been installed with the following options:
[Options]
TARGETDIR="C:\Program Files\MSDE 2000\"
SAPWD="<My Password>"
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
I try to connect to this MSDE database from another machine where SQL Server
2000 3.0a is running, using the Enterprise Manager.
In Enterprise Manager I enter the IP-address of the server where the MSDE-da
tabase is running and choose the option "Connect using the SQl server login
information..." where I enter "sa" and "<My Password>", the same assigned to
MSDE during setup.
As result I always get the message: "SQL Server does not exist or access is
denied. ConnectionOpen (Connect())".
I don't have any more ideas about what might be wrong...
Can anybody help me please?Are you sure MSDE isn't a named instance (so you would enter <ip
address>\<instance name> )?
"Roberto Rocco" <roberto@.rocco.de> wrote in message
news:eHYPhUZ0DHA.3196@.TK2MSFTNGP11.phx.gbl...
Hello,
I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003
as the default instance.
MSDE has been installed with the following options:
[Options]
TARGETDIR="C:\Program Files\MSDE 2000\"
SAPWD="<My Password>"
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
I try to connect to this MSDE database from another machine where SQL Server
2000 3.0a is running, using the Enterprise Manager.
In Enterprise Manager I enter the IP-address of the server where the
MSDE-database is running and choose the option "Connect using the SQl server
login information..." where I enter "sa" and "<My Password>", the same
assigned to MSDE during setup.
As result I always get the message: "SQL Server does not exist or access is
denied. ConnectionOpen (Connect())".
I don't have any more ideas about what might be wrong...
Can anybody help me please?|||Hello Foo,
thank you for your fast reply. Yes, I am sure that it is the default
instance.
Meanwhile I made some other tests: Running the same MSDE installation on
another machine (Windows XP) with the same Options.ini file (same settings,
same password, etc.) works pretty well!!
So I guess it must be "something" on the Windows 2003 Server.
I checked if it has a firewall configured, but it has not.
Can some ports be disabled on the Windows 2003 Server?
Are there other places to check?
Roberto.
"Foo Man Chew" <foo@.man.chew> schrieb im Newsbeitrag
news:OHbGqBa0DHA.2580@.TK2MSFTNGP09.phx.gbl...
quote:
> Are you sure MSDE isn't a named instance (so you would enter <ip
> address>\<instance name> )?
>
>
> "Roberto Rocco" <roberto@.rocco.de> wrote in message
> news:eHYPhUZ0DHA.3196@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003
> as the default instance.
> MSDE has been installed with the following options:
> [Options]
> TARGETDIR="C:\Program Files\MSDE 2000\"
> SAPWD="<My Password>"
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> I try to connect to this MSDE database from another machine where SQL
Server
quote:
> 2000 3.0a is running, using the Enterprise Manager.
> In Enterprise Manager I enter the IP-address of the server where the
> MSDE-database is running and choose the option "Connect using the SQl
server
quote:
> login information..." where I enter "sa" and "<My Password>", the same
> assigned to MSDE during setup.
> As result I always get the message: "SQL Server does not exist or access
is
quote:|||Problem solved!
> denied. ConnectionOpen (Connect())".
> I don't have any more ideas about what might be wrong...
> Can anybody help me please?
>
Port 1433 was blocked on the Windows 2003 Server. After adjusting the Packet
Filter Policies to permit Port 1433 access I was able to connect to the MSDE
database.
Thanks all for your support.
Roberto.
"Roberto Rocco" <roberto@.rocco.de> schrieb im Newsbeitrag
news:OTXwf%23f0DHA.1532@.TK2MSFTNGP10.phx.gbl...
quote:
> Hello Foo,
> thank you for your fast reply. Yes, I am sure that it is the default
> instance.
> Meanwhile I made some other tests: Running the same MSDE installation on
> another machine (Windows XP) with the same Options.ini file (same
settings,
quote:|||Hi.
> same password, etc.) works pretty well!!
> So I guess it must be "something" on the Windows 2003 Server.
> I checked if it has a firewall configured, but it has not.
> Can some ports be disabled on the Windows 2003 Server?
> Are there other places to check?
> Roberto.
> "Foo Man Chew" <foo@.man.chew> schrieb im Newsbeitrag
> news:OHbGqBa0DHA.2580@.TK2MSFTNGP09.phx.gbl...
2003[QUOTE]
> Server
> server
> is
>
I have the same problem, I have changed the TCP/IP filtering under the
TCP/IP setting on the network adapter to 'Enable TCP/IP Filtering' and
set to 'Permit All' on all types, but it still doesn't work. Are you
talking about something else? If so can you post a short guide of what
to change and where it is found in the Windows 2003 maze.
Thanks
Best Regards
Andrew.
da644
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message238297.html
Cannot connect to MSDE
Hello all,
I have two computers in LAN. Both computers are visible
one to another. First computer has MSDE installed on it.
Second cumputer runs application that needs to connect to
MSDE installed on the first computer. The problem is that
application installed on second computer cannot connect to
MSDE and i cant figure out why is that so.
The application running on first computer(the one that
has MSDE installed on it) can connect to MSDE without any
problems. MSDE is configured to use SQL Server
authentication. Can anyone help me please ?
Regards,
Tom
hi Tom,
Tom wrote:
> Hello all,
> I have two computers in LAN. Both computers are visible
> one to another. First computer has MSDE installed on it.
> Second cumputer runs application that needs to connect to
> MSDE installed on the first computer. The problem is that
> application installed on second computer cannot connect to
> MSDE and i cant figure out why is that so.
> The application running on first computer(the one that
> has MSDE installed on it) can connect to MSDE without any
> problems. MSDE is configured to use SQL Server
> authentication. Can anyone help me please ?
> Regards,
> Tom
MSDE installs by default disabling network protocols to prevent external
mailcius attacks...
you have to manually enable them, bot at install time providing the
DISABLENETWORKPROTOCOLS=0
parameter to setup.exe boostrap installer and/or later using the Server
Network Utility (svrnet.cn.exe) to enable the desired/required network
protocol (usually TCP/IP)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
I'm having the same problem. I am working in a peer-to-peer LAN (all XP
stations) and have all my tools installed on one station (MSDE, Visual
Studio, you great DbaMGR2k, Book Online, etc) and things are working
fine, but I can't access SQL from the other stations. All the stations
can see each others and share all other resources.
- I used svrnetcn.exe to make certain TCP/IP protocol was installed, it was
- I tried added named pipes too but it doesn't help
- I logged in as Administrator but still have the problem
Questions:
- Do I need to install MSDE on all the stations?
- Could Windows XP SP2 firewall be the problem?
Thanks
Richard
Andrea Montanari wrote:
> hi Tom,
> Tom wrote:
>
> MSDE installs by default disabling network protocols to prevent external
> mailcius attacks...
> you have to manually enable them, bot at install time providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to setup.exe boostrap installer and/or later using the Server
> Network Utility (svrnet.cn.exe) to enable the desired/required network
> protocol (usually TCP/IP)
|||hi Richard,
Richard Fagen wrote:
> Hi Andrea,
> I'm having the same problem. I am working in a peer-to-peer LAN (all
> XP stations) and have all my tools installed on one station (MSDE,
> Visual Studio,
> you great DbaMGR2k
thank's :D
>, Book Online, etc) and things are
> working
> fine, but I can't access SQL from the other stations. All the
> stations can see each others and share all other resources.
> - I used svrnetcn.exe to make certain TCP/IP protocol was installed,
> it was
> - I tried added named pipes too but it doesn't help
> - I logged in as Administrator but still have the problem
> Questions:
> - Do I need to install MSDE on all the stations?
no, you don't
> - Could Windows XP SP2 firewall be the problem?
probably yes...
please have a look at http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
personally I always solved my troubles adding an exception to the firewall
for the related TCP/IP port both specifying a subnet range and/or defined
pc's IP ... if you can restrict the IP list your server will appreciate it
:D
for named instance the UDP 1434 port must be opened as well, if you do not
specify an ALIAS on all remote clients pointing to a static defined (and not
dinamically assigned) port
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for the links
> probably yes...
> please have a look at http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
I tried what it said and I even tried disabling the XP SP2 firewall on
both PCs but the second PC (the one without MSDE installed) still can't
see the first PC (with MSDE and the databases).
I tried using your utility, DbaMGR2k, on the second PC but when I try to
connect, I get the error message, "429 - ActiveX component can't create
object"
I am new to MSDE and I am not sure if I need aliases, named pipes,
special libaries etc. What I do have configured is TCP/IP protocol and
I checked and it uses the default port 1433. I also only have one
instance, the default, created during installation.
I could try to install MSDE on a third PC with all the defaults and see
what happens, but I'm fairly certain I didn't change anything from the
recommended defaults during the initial installation.
Any ideas why the other stations still can't see MSDE?
Thanks.
Richard Fagen
> personally I always solved my troubles adding an exception to the firewall
> for the related TCP/IP port both specifying a subnet range and/or defined
> pc's IP ... if you can restrict the IP list your server will appreciate it
> :D
> for named instance the UDP 1434 port must be opened as well, if you do not
> specify an ALIAS on all remote clients pointing to a static defined (and not
> dinamically assigned) port
|||hi Richard,
Richard Fagen wrote:
> I tried what it said and I even tried disabling the XP SP2 firewall on
> both PCs but the second PC (the one without MSDE installed) still
> can't see the first PC (with MSDE and the databases).
can you reach the MSDE installed pc from the remote client for standard
sharing?
can you ping it?
can you telnet it, in the form
c:\..\>telnet ComputerName 1433;
if the screen becomes black you are in... then just type QUIT to exit..
> I tried using your utility, DbaMGR2k, on the second PC but when I try
> to connect, I get the error message, "429 - ActiveX component can't
> create object"
DbaMgr2k does not provide the SQL-DMO dependencies it relies on becouse of
the presence several international localizations and service pack level..
in the application folder you can find the Depend2k.txt file which lists, in
the SQL-DMO section, all the required files you can get from the MSDE
installed pc and copy on the destination pc.. please fullfill the indicated
hyerarchy and register via regsvr32 the required file (just 1)
please feel free to privately contact me for any question or concern about
the project, as long as for suggestions and feedback, as this is OT in this
public newsgroup...
> I am new to MSDE and I am not sure if I need aliases, named pipes,
> special libaries etc. What I do have configured is TCP/IP protocol
> and I checked and it uses the default port 1433. I also only have one
> instance, the default, created during installation.
that's ok.. the default instance listens on TCP/IP 1433 (if it has not been
changed) and does not require an ALIAS nor the UDP 1434 port for the SQL
Server Resolution Service to work as it is not needed..
> Any ideas why the other stations still can't see MSDE?
if all TCP/IP requirements and checks has been satisfied, I do think it's
just a network problem.. please verify your connectivity other then SQL
Server...
again... for my personal tests I just referenced
http://support.microsoft.com/default.aspx?kbid=841252 and worked like a
charm...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I have two computers in LAN. Both computers are visible
one to another. First computer has MSDE installed on it.
Second cumputer runs application that needs to connect to
MSDE installed on the first computer. The problem is that
application installed on second computer cannot connect to
MSDE and i cant figure out why is that so.
The application running on first computer(the one that
has MSDE installed on it) can connect to MSDE without any
problems. MSDE is configured to use SQL Server
authentication. Can anyone help me please ?
Regards,
Tom
hi Tom,
Tom wrote:
> Hello all,
> I have two computers in LAN. Both computers are visible
> one to another. First computer has MSDE installed on it.
> Second cumputer runs application that needs to connect to
> MSDE installed on the first computer. The problem is that
> application installed on second computer cannot connect to
> MSDE and i cant figure out why is that so.
> The application running on first computer(the one that
> has MSDE installed on it) can connect to MSDE without any
> problems. MSDE is configured to use SQL Server
> authentication. Can anyone help me please ?
> Regards,
> Tom
MSDE installs by default disabling network protocols to prevent external
mailcius attacks...
you have to manually enable them, bot at install time providing the
DISABLENETWORKPROTOCOLS=0
parameter to setup.exe boostrap installer and/or later using the Server
Network Utility (svrnet.cn.exe) to enable the desired/required network
protocol (usually TCP/IP)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
I'm having the same problem. I am working in a peer-to-peer LAN (all XP
stations) and have all my tools installed on one station (MSDE, Visual
Studio, you great DbaMGR2k, Book Online, etc) and things are working
fine, but I can't access SQL from the other stations. All the stations
can see each others and share all other resources.
- I used svrnetcn.exe to make certain TCP/IP protocol was installed, it was
- I tried added named pipes too but it doesn't help
- I logged in as Administrator but still have the problem
Questions:
- Do I need to install MSDE on all the stations?
- Could Windows XP SP2 firewall be the problem?
Thanks
Richard
Andrea Montanari wrote:
> hi Tom,
> Tom wrote:
>
> MSDE installs by default disabling network protocols to prevent external
> mailcius attacks...
> you have to manually enable them, bot at install time providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to setup.exe boostrap installer and/or later using the Server
> Network Utility (svrnet.cn.exe) to enable the desired/required network
> protocol (usually TCP/IP)
|||hi Richard,
Richard Fagen wrote:
> Hi Andrea,
> I'm having the same problem. I am working in a peer-to-peer LAN (all
> XP stations) and have all my tools installed on one station (MSDE,
> Visual Studio,
> you great DbaMGR2k
thank's :D
>, Book Online, etc) and things are
> working
> fine, but I can't access SQL from the other stations. All the
> stations can see each others and share all other resources.
> - I used svrnetcn.exe to make certain TCP/IP protocol was installed,
> it was
> - I tried added named pipes too but it doesn't help
> - I logged in as Administrator but still have the problem
> Questions:
> - Do I need to install MSDE on all the stations?
no, you don't
> - Could Windows XP SP2 firewall be the problem?
probably yes...
please have a look at http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
personally I always solved my troubles adding an exception to the firewall
for the related TCP/IP port both specifying a subnet range and/or defined
pc's IP ... if you can restrict the IP list your server will appreciate it
:D
for named instance the UDP 1434 port must be opened as well, if you do not
specify an ALIAS on all remote clients pointing to a static defined (and not
dinamically assigned) port
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for the links
> probably yes...
> please have a look at http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
I tried what it said and I even tried disabling the XP SP2 firewall on
both PCs but the second PC (the one without MSDE installed) still can't
see the first PC (with MSDE and the databases).
I tried using your utility, DbaMGR2k, on the second PC but when I try to
connect, I get the error message, "429 - ActiveX component can't create
object"
I am new to MSDE and I am not sure if I need aliases, named pipes,
special libaries etc. What I do have configured is TCP/IP protocol and
I checked and it uses the default port 1433. I also only have one
instance, the default, created during installation.
I could try to install MSDE on a third PC with all the defaults and see
what happens, but I'm fairly certain I didn't change anything from the
recommended defaults during the initial installation.
Any ideas why the other stations still can't see MSDE?
Thanks.
Richard Fagen
> personally I always solved my troubles adding an exception to the firewall
> for the related TCP/IP port both specifying a subnet range and/or defined
> pc's IP ... if you can restrict the IP list your server will appreciate it
> :D
> for named instance the UDP 1434 port must be opened as well, if you do not
> specify an ALIAS on all remote clients pointing to a static defined (and not
> dinamically assigned) port
|||hi Richard,
Richard Fagen wrote:
> I tried what it said and I even tried disabling the XP SP2 firewall on
> both PCs but the second PC (the one without MSDE installed) still
> can't see the first PC (with MSDE and the databases).
can you reach the MSDE installed pc from the remote client for standard
sharing?
can you ping it?
can you telnet it, in the form
c:\..\>telnet ComputerName 1433;
if the screen becomes black you are in... then just type QUIT to exit..
> I tried using your utility, DbaMGR2k, on the second PC but when I try
> to connect, I get the error message, "429 - ActiveX component can't
> create object"
DbaMgr2k does not provide the SQL-DMO dependencies it relies on becouse of
the presence several international localizations and service pack level..
in the application folder you can find the Depend2k.txt file which lists, in
the SQL-DMO section, all the required files you can get from the MSDE
installed pc and copy on the destination pc.. please fullfill the indicated
hyerarchy and register via regsvr32 the required file (just 1)
please feel free to privately contact me for any question or concern about
the project, as long as for suggestions and feedback, as this is OT in this
public newsgroup...
> I am new to MSDE and I am not sure if I need aliases, named pipes,
> special libaries etc. What I do have configured is TCP/IP protocol
> and I checked and it uses the default port 1433. I also only have one
> instance, the default, created during installation.
that's ok.. the default instance listens on TCP/IP 1433 (if it has not been
changed) and does not require an ALIAS nor the UDP 1434 port for the SQL
Server Resolution Service to work as it is not needed..
> Any ideas why the other stations still can't see MSDE?
if all TCP/IP requirements and checks has been satisfied, I do think it's
just a network problem.. please verify your connectivity other then SQL
Server...
again... for my personal tests I just referenced
http://support.microsoft.com/default.aspx?kbid=841252 and worked like a
charm...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Sunday, February 12, 2012
Cannot connect to FTP Site (Merge replication)
Hi;
We have mulitple clients (subscribers) with MSDE SP3. All but one subsriber
are able to retrieve the subscription and replication. The error message on
the failing subscriber is "The computer is disconnected from the network".
The computer runs XP Pro like most of the others and is connected via a VPN
like the others.
The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
The process could not connect to FTP site 'PL000' using port 21.
(Source: lachlan (Agent); Error number: 0)
The computer is disconnected from the network
(Source: (OS); Error number: 12163)
Any ideas what can cause this? The subscriber that fails was infected with a
virus earlier, but it is now clean the the virus software does not detect
any new or existing virus.
Thomas Born
there are many possibilities
1) the ftp server/site is not active
2) you have specified anonymous only in your ftp server and are trying to
connect using an NT account
3) the ftp server is listening on a different port
4) the snapshot folder does not have read rights for the NT account you are
using or if you are using anonymous authentication to the IUSER_MachineName
account
5) You are using an NT account that does not exist on the machine hosting
the FTP server.
6) your subscriber is on the deny acccess IP address list
Return to your publisher and confirm that all of the above is correctly set
up
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Thomas Born" <tborn_news@.hotmail.com> wrote in message
news:u2gIGJYZEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Hi;
> We have mulitple clients (subscribers) with MSDE SP3. All but one
subsriber
> are able to retrieve the subscription and replication. The error message
on
> the failing subscriber is "The computer is disconnected from the network".
> The computer runs XP Pro like most of the others and is connected via a
VPN
> like the others.
>
> The schema script '' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> --
> The process could not connect to FTP site 'PL000' using port 21.
> (Source: lachlan (Agent); Error number: 0)
> ----
--
> --
> The computer is disconnected from the network
> (Source: (OS); Error number: 12163)
> ----
--
> --
> Any ideas what can cause this? The subscriber that fails was infected with
a
> virus earlier, but it is now clean the the virus software does not detect
> any new or existing virus.
> Thomas Born
>
|||Thanks for the respone,
I am using anonymous authentication from all the other subscribers as well
and they are working. Also very sure that the server listens on 21. Need to
check 6) but I don't think it is a problem.
I have tested it with having two different machines as the subscriber on my
network at home. One is working and the other one gets the computer
disconnected message. I am getting close to reinstall the operating system
on the failing subscriber, will see if that fixes the problem.
Thomas
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OFyXETaZEHA.3012@.tk2msftngp13.phx.gbl...
> there are many possibilities
> 1) the ftp server/site is not active
> 2) you have specified anonymous only in your ftp server and are trying to
> connect using an NT account
> 3) the ftp server is listening on a different port
> 4) the snapshot folder does not have read rights for the NT account you
are
> using or if you are using anonymous authentication to the
IUSER_MachineName
> account
> 5) You are using an NT account that does not exist on the machine hosting
> the FTP server.
> 6) your subscriber is on the deny acccess IP address list
> Return to your publisher and confirm that all of the above is correctly
set[vbcol=seagreen]
> up
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Thomas Born" <tborn_news@.hotmail.com> wrote in message
> news:u2gIGJYZEHA.3564@.TK2MSFTNGP11.phx.gbl...
> subsriber
> on
network".[vbcol=seagreen]
> VPN
> ----
> --
> ----
> --
> ----
> --
with[vbcol=seagreen]
> a
detect
>
|||Re-installing the operating system to fix ftp is radical.
Can you open up IE, and in the address bar connect to the ftp site on the
publisher. What do the ftp logs on the publisher reveal?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Thomas Born" <tborn_news@.hotmail.com> wrote in message
news:eWZ00$%23ZEHA.3708@.TK2MSFTNGP10.phx.gbl...
> Thanks for the respone,
> I am using anonymous authentication from all the other subscribers as well
> and they are working. Also very sure that the server listens on 21. Need
to
> check 6) but I don't think it is a problem.
> I have tested it with having two different machines as the subscriber on
my[vbcol=seagreen]
> network at home. One is working and the other one gets the computer
> disconnected message. I am getting close to reinstall the operating system
> on the failing subscriber, will see if that fixes the problem.
> Thomas
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OFyXETaZEHA.3012@.tk2msftngp13.phx.gbl...
to[vbcol=seagreen]
> are
> IUSER_MachineName
hosting[vbcol=seagreen]
> set
message[vbcol=seagreen]
> network".
a[vbcol=seagreen]
number: -2147201001)
> ----
> ----
> ----
> with
> detect
>
We have mulitple clients (subscribers) with MSDE SP3. All but one subsriber
are able to retrieve the subscription and replication. The error message on
the failing subscriber is "The computer is disconnected from the network".
The computer runs XP Pro like most of the others and is connected via a VPN
like the others.
The schema script '' could not be propagated to the subscriber.
(Source: Merge Replication Provider (Agent); Error number: -2147201001)
The process could not connect to FTP site 'PL000' using port 21.
(Source: lachlan (Agent); Error number: 0)
The computer is disconnected from the network
(Source: (OS); Error number: 12163)
Any ideas what can cause this? The subscriber that fails was infected with a
virus earlier, but it is now clean the the virus software does not detect
any new or existing virus.
Thomas Born
there are many possibilities
1) the ftp server/site is not active
2) you have specified anonymous only in your ftp server and are trying to
connect using an NT account
3) the ftp server is listening on a different port
4) the snapshot folder does not have read rights for the NT account you are
using or if you are using anonymous authentication to the IUSER_MachineName
account
5) You are using an NT account that does not exist on the machine hosting
the FTP server.
6) your subscriber is on the deny acccess IP address list
Return to your publisher and confirm that all of the above is correctly set
up
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Thomas Born" <tborn_news@.hotmail.com> wrote in message
news:u2gIGJYZEHA.3564@.TK2MSFTNGP11.phx.gbl...
> Hi;
> We have mulitple clients (subscribers) with MSDE SP3. All but one
subsriber
> are able to retrieve the subscription and replication. The error message
on
> the failing subscriber is "The computer is disconnected from the network".
> The computer runs XP Pro like most of the others and is connected via a
VPN
> like the others.
>
> The schema script '' could not be propagated to the subscriber.
> (Source: Merge Replication Provider (Agent); Error number: -2147201001)
> ----
--
> --
> The process could not connect to FTP site 'PL000' using port 21.
> (Source: lachlan (Agent); Error number: 0)
> ----
--
> --
> The computer is disconnected from the network
> (Source: (OS); Error number: 12163)
> ----
--
> --
> Any ideas what can cause this? The subscriber that fails was infected with
a
> virus earlier, but it is now clean the the virus software does not detect
> any new or existing virus.
> Thomas Born
>
|||Thanks for the respone,
I am using anonymous authentication from all the other subscribers as well
and they are working. Also very sure that the server listens on 21. Need to
check 6) but I don't think it is a problem.
I have tested it with having two different machines as the subscriber on my
network at home. One is working and the other one gets the computer
disconnected message. I am getting close to reinstall the operating system
on the failing subscriber, will see if that fixes the problem.
Thomas
"Hilary Cotter" <hilaryk@.att.net> wrote in message
news:OFyXETaZEHA.3012@.tk2msftngp13.phx.gbl...
> there are many possibilities
> 1) the ftp server/site is not active
> 2) you have specified anonymous only in your ftp server and are trying to
> connect using an NT account
> 3) the ftp server is listening on a different port
> 4) the snapshot folder does not have read rights for the NT account you
are
> using or if you are using anonymous authentication to the
IUSER_MachineName
> account
> 5) You are using an NT account that does not exist on the machine hosting
> the FTP server.
> 6) your subscriber is on the deny acccess IP address list
> Return to your publisher and confirm that all of the above is correctly
set[vbcol=seagreen]
> up
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "Thomas Born" <tborn_news@.hotmail.com> wrote in message
> news:u2gIGJYZEHA.3564@.TK2MSFTNGP11.phx.gbl...
> subsriber
> on
network".[vbcol=seagreen]
> VPN
> ----
> --
> ----
> --
> ----
> --
with[vbcol=seagreen]
> a
detect
>
|||Re-installing the operating system to fix ftp is radical.
Can you open up IE, and in the address bar connect to the ftp site on the
publisher. What do the ftp logs on the publisher reveal?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"Thomas Born" <tborn_news@.hotmail.com> wrote in message
news:eWZ00$%23ZEHA.3708@.TK2MSFTNGP10.phx.gbl...
> Thanks for the respone,
> I am using anonymous authentication from all the other subscribers as well
> and they are working. Also very sure that the server listens on 21. Need
to
> check 6) but I don't think it is a problem.
> I have tested it with having two different machines as the subscriber on
my[vbcol=seagreen]
> network at home. One is working and the other one gets the computer
> disconnected message. I am getting close to reinstall the operating system
> on the failing subscriber, will see if that fixes the problem.
> Thomas
> "Hilary Cotter" <hilaryk@.att.net> wrote in message
> news:OFyXETaZEHA.3012@.tk2msftngp13.phx.gbl...
to[vbcol=seagreen]
> are
> IUSER_MachineName
hosting[vbcol=seagreen]
> set
message[vbcol=seagreen]
> network".
a[vbcol=seagreen]
number: -2147201001)
> ----
> ----
> ----
> with
> detect
>
Friday, February 10, 2012
Cannot connect SQL 2005 with OLE DB Provider for SQL Server
Cannot connect SQL 2005 with OLE DB Provider for SQL Server
MSSQL 2000 Utilities & MSDE was uninstalled.
After installation SQL 2005 Standard Full all connections was OK (tested).
Aftert restarting the computer I cannot connect to MSSQL with OLE DB Provider for SQL Server.
I try to connect from Delphi 5 SP2 (ADOConnection) and from MS Access 2003 SP2.
Error "SQL Server denied or does not exists or access denied"
Versions:
Windows Xp Pro SP 2
ADO/MDAC: 2.81.1117.0 (xpsp_sp2_rtm.040803-2158)
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600
Connection sting:
Provider=SQLOLEDB.1;Persist Security Info=False;User ID=sa;Password=pwd;Data Source=GMSAlexHome;Initial Catalog=GMSSample;Application Name="GMS Office Tools Service Pack"
Question: how to connect to SQL 2005 with SQL DB Provider.
All old applications does not work.
On local machine when ServerName = 'localhost' or '.' - all OK.
When using SQL server name - error.
Before rebooting all was OK.
Thanks in advance.
If you try to connect from the local PC and it works fine, but does not work from the network then most likely SQL Server is not enabled to accept external network requests. Also if your server name contains instance name, then it also suppose to be specified in your connection string, like servername\instancename|||On local computer connection avaible only as <localhost> and <.>.
There is no instance name and other sql servers.
SQLSRV Works more than 3 times slower than MSDE 2000 on small test DB (about 100 mb).
VERY many bugs in tools and very slow.... $(((
What comps in MS? I have P4 3MHz 1 Gb SATA - VERY slow.
Sory for digression.
|||Do you compare performance based on exact same data and structure? If your indexes are not the same as in MSDE 2000 then you cannot compare performance.
About bugs. If you have any, you could report them here. If you do this and they really exist, I believe, it will help to improve product
|||As Val mentioned, please double check using "SQL Server Configuration Manager" tool that your SQL instance has remote TCP and/or Named Pipe support enabled.
Also, please make sure that the Windows Firewall is not blocking the ports used by SQL Server. You can explicitly add TCP port 1433 to the exception list or you can add Sqlservr.exe program to the exception list (to ensure both TCP and Named Pipes are not blocked).
Jimmy Wu
Subscribe to:
Posts (Atom)