hello,
We're running W2000 sp4 fr/ SQL 2000 SP3 fr and get error 17122 in the
application event log every time SQL is brought up. The error text
reads
"initdata: Warning: Could not set working set size to 1168512 KB".
What does
this really mean, is it harmful and how can I correct it? Thanks for
any info.
Thanks
A.S
Hi,
Not a real problem, this is only a warning due to incompatibility with
PAE/AWE !
Just disable the "reserve physical memory for SQLServer" by :
sp_configure 'set working set size',0
go
reconfigure with override
go
See http://support.microsoft.com/kb/822164/en-us
Guillaume.
"Zizou-Real" wrote:
> hello,
> We're running W2000 sp4 fr/ SQL 2000 SP3 fr and get error 17122 in the
> application event log every time SQL is brought up. The error text
> reads
> "initdata: Warning: Could not set working set size to 1168512 KB".
> What does
> this really mean, is it harmful and how can I correct it? Thanks for
> any info.
>
> Thank’s
> A.S
>
>
sql
Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts
Tuesday, March 20, 2012
Monday, March 19, 2012
Could not open FCB for invalid file ID
We've been getting the following error this week on our SQL Server 2000
sp3 box:
Error: 5180, Severity: 22, State: 1
Could not open FCB for invalid file ID 0 in database 'database_name'
I've found a couple of articles relating to text and image columns may
be the cause of this, however the databases we recieved this error in
do not have text or image columns. We have gotten this error twice
over the past week, in two seperate databases on the same server. I
ran DBCC CHECKDB, and both databases passed.
Does anyone have anymore information on this error?Hi
Check that Anti-Virus does not scan these files.
Regards
Mike
"dosberg@.yahoo.com" wrote:
> We've been getting the following error this week on our SQL Server 2000
> sp3 box:
> Error: 5180, Severity: 22, State: 1
> Could not open FCB for invalid file ID 0 in database 'database_name'
> I've found a couple of articles relating to text and image columns may
> be the cause of this, however the databases we recieved this error in
> do not have text or image columns. We have gotten this error twice
> over the past week, in two seperate databases on the same server. I
> ran DBCC CHECKDB, and both databases passed.
> Does anyone have anymore information on this error?
>
sp3 box:
Error: 5180, Severity: 22, State: 1
Could not open FCB for invalid file ID 0 in database 'database_name'
I've found a couple of articles relating to text and image columns may
be the cause of this, however the databases we recieved this error in
do not have text or image columns. We have gotten this error twice
over the past week, in two seperate databases on the same server. I
ran DBCC CHECKDB, and both databases passed.
Does anyone have anymore information on this error?Hi
Check that Anti-Virus does not scan these files.
Regards
Mike
"dosberg@.yahoo.com" wrote:
> We've been getting the following error this week on our SQL Server 2000
> sp3 box:
> Error: 5180, Severity: 22, State: 1
> Could not open FCB for invalid file ID 0 in database 'database_name'
> I've found a couple of articles relating to text and image columns may
> be the cause of this, however the databases we recieved this error in
> do not have text or image columns. We have gotten this error twice
> over the past week, in two seperate databases on the same server. I
> ran DBCC CHECKDB, and both databases passed.
> Does anyone have anymore information on this error?
>
Sunday, March 11, 2012
Could not get the data of the row from the OLE DB provider 'SQLOLE
We are running SQL2000 SP3 on two servers. One is Server 2003 the other is
Server 2000. Both servers are linked to one another. The 2003 server is
running DTC. We are running several lightweight jobs that are occasionally,
and more often than we like, having the following error:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp basically set variables with data from both the primary server A and
the linked server B using views. This part is successful. The next step is
updating information in server B via a view. This appears to be where the
job is creating the above error. The last part of the sp is another update
entirely on the local server A.
I appreciate your help...
Thanks...Hi
Error 7312 is "Could not set up parameter for remote server '%.*ls'."
I have sometimes seen this error when a remote server has a deadlock or when
a lock can not be acquired to satisfy the request. Have a look at what is
happening on the linked server when this occurs.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisD" <ChrisD@.discussions.microsoft.com> wrote in message
news:D508BC5E-178C-4518-BF00-D17BA13143DF@.microsoft.com...
> We are running SQL2000 SP3 on two servers. One is Server 2003 the other
is
> Server 2000. Both servers are linked to one another. The 2003 server is
> running DTC. We are running several lightweight jobs that are
occasionally,
> and more often than we like, having the following error:
> Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
> [SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB
error
> trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
> [SQLSTATE 01000] (Error 7300). The step failed.
> The sp basically set variables with data from both the primary server A
and
> the linked server B using views. This part is successful. The next step
is
> updating information in server B via a view. This appears to be where the
> job is creating the above error. The last part of the sp is another
update
> entirely on the local server A.
> I appreciate your help...
> Thanks...
>
Server 2000. Both servers are linked to one another. The 2003 server is
running DTC. We are running several lightweight jobs that are occasionally,
and more often than we like, having the following error:
Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
[SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB error
trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
[SQLSTATE 01000] (Error 7300). The step failed.
The sp basically set variables with data from both the primary server A and
the linked server B using views. This part is successful. The next step is
updating information in server B via a view. This appears to be where the
job is creating the above error. The last part of the sp is another update
entirely on the local server A.
I appreciate your help...
Thanks...Hi
Error 7312 is "Could not set up parameter for remote server '%.*ls'."
I have sometimes seen this error when a remote server has a deadlock or when
a lock can not be acquired to satisfy the request. Have a look at what is
happening on the linked server when this occurs.
Regards
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"ChrisD" <ChrisD@.discussions.microsoft.com> wrote in message
news:D508BC5E-178C-4518-BF00-D17BA13143DF@.microsoft.com...
> We are running SQL2000 SP3 on two servers. One is Server 2003 the other
is
> Server 2000. Both servers are linked to one another. The 2003 server is
> running DTC. We are running several lightweight jobs that are
occasionally,
> and more often than we like, having the following error:
> Could not get the data of the row from the OLE DB provider 'SQLOLEDB'.
> [SQLSTATE 42000] (Error 7346) [SQLSTATE 01000] (Error 7312) OLE DB
error
> trace [OLE/DB Provider 'SQLOLEDB' IRowset::GetData returned 0x80040e23].
> [SQLSTATE 01000] (Error 7300). The step failed.
> The sp basically set variables with data from both the primary server A
and
> the linked server B using views. This part is successful. The next step
is
> updating information in server B via a view. This appears to be where the
> job is creating the above error. The last part of the sp is another
update
> entirely on the local server A.
> I appreciate your help...
> Thanks...
>
Thursday, March 8, 2012
Could not find stored procedure ''?
Hi
I recently recovered my SQL2000 Sp3 Merge Replication structure from a
failure after adding a few new articles to my publication. Everything was
going fine (getting everyone up again), until I noticed 5 out of the 100
sites with the following problem:
The merge process could not retrieve column information for table
'dbo.C_ClaimStatus'.
(Source: Merge Replication Provider (Agent); Error number: -2147201016)
Could not find stored procedure ''.
(Source: DAYMED\CC (Data source); Error number: 2812)
I tried re-initialising these subcriptions again, but the problem stayed.
What bugs me is that all my sites were restarted in exactly the same way
(re-initialise site with a pre and post snapshot script to run) and these
are the only 5 sites with this problem.
(All sites are running MSDE sp3 or SQL2000 sp3 and are pull subscriptions)
Has anybody had this before, and if so, how do I fix this?
Regards
Paul Kleynhans
Paul,
This may be due to a failed sp installation. Reapplying sp3a may fix it and
to get a bit more info, have a look at sqlsp.log file from the c:\windows
directory - this might shed some light on any failed actions during the sp
installation.
Regards,
Paul Ibison
I recently recovered my SQL2000 Sp3 Merge Replication structure from a
failure after adding a few new articles to my publication. Everything was
going fine (getting everyone up again), until I noticed 5 out of the 100
sites with the following problem:
The merge process could not retrieve column information for table
'dbo.C_ClaimStatus'.
(Source: Merge Replication Provider (Agent); Error number: -2147201016)
Could not find stored procedure ''.
(Source: DAYMED\CC (Data source); Error number: 2812)
I tried re-initialising these subcriptions again, but the problem stayed.
What bugs me is that all my sites were restarted in exactly the same way
(re-initialise site with a pre and post snapshot script to run) and these
are the only 5 sites with this problem.
(All sites are running MSDE sp3 or SQL2000 sp3 and are pull subscriptions)
Has anybody had this before, and if so, how do I fix this?
Regards
Paul Kleynhans
Paul,
This may be due to a failed sp installation. Reapplying sp3a may fix it and
to get a bit more info, have a look at sqlsp.log file from the c:\windows
directory - this might shed some light on any failed actions during the sp
installation.
Regards,
Paul Ibison
Friday, February 24, 2012
could not bulk copy out of table 'contE6E5BDF7F1C24EC588142A934ACF00D1'
Hi all,
Sorry to post this one again but I have added some more info....
I have a sql2000 SP3 merge replication set up using dynamic filters
to 29 sites/publications so each site only see's it's own data.
I have been adding new tables to the schema using sp_mergearticle
(but that is another story !!). I have been running the
sp_mergearticle , running the snapshot, merging, new tables published
...etc OK. I did this 10 times and then hit the error The process
could not bulk copy out of table
'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
agent for one of the publications.
I added the -output (Outputverboselevel 2) and got the follow info at
the end (it failes when it starts to bulk copy)
Bulk copying snapshot data for system table 'MSmerge_contents'
select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
[9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
SourceTypeId = 5
SourceName = GODZILLA
ErrorCode = 8624
ErrorText = Internal SQL Server error.
The process could not bulk copy out of table
'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
Disconnecting from Publisher 'GODZILLA'
I ran the profiler whilst the snapshot was generated, I could see the
view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
(any anything else it had temp created) Is there any way I can capture
the view before it is dropped or stop the drop from occuring. I am sure
if I can get hold of this view then I will be able to find the fault.
I am confused as to why this has been fine on 10 of the publications
then suddenly decided to error.
The file versions I have are:
SQLSRV32.DLL = 2000.81.9042.0
SQLSRV32.RLL = 2000.81.9001.0
odbcbcp.dll = 2000.81.9042.0
Thanks
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I've had my share of problems with dynamic filters, but not the one you are
encountering. Can you drop this subscription and filter and then try to
recreate it using another folder?
If you want to catch this transitory view you are best to query it in the
publication database.
IE repeatedly run
sp_helptext contE6E5BDF7F1C24EC588142A934ACF00D1
Or run profiler to try to capture its creation
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eesd36JnEHA.556@.tk2msftngp13.phx.gbl...
> Hi all,
> Sorry to post this one again but I have added some more info....
>
> I have a sql2000 SP3 merge replication set up using dynamic filters
> to 29 sites/publications so each site only see's it's own data.
> I have been adding new tables to the schema using sp_mergearticle
> (but that is another story !!). I have been running the
> sp_mergearticle , running the snapshot, merging, new tables published
> ...etc OK. I did this 10 times and then hit the error The process
> could not bulk copy out of table
> 'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
> agent for one of the publications.
> I added the -output (Outputverboselevel 2) and got the follow info at
> the end (it failes when it starts to bulk copy)
> Bulk copying snapshot data for system table 'MSmerge_contents'
> select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> [9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
> cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> SourceTypeId = 5
> SourceName = GODZILLA
> ErrorCode = 8624
> ErrorText = Internal SQL Server error.
> The process could not bulk copy out of table
> 'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
> Disconnecting from Publisher 'GODZILLA'
>
> I ran the profiler whilst the snapshot was generated, I could see the
> view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
> errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
> (any anything else it had temp created) Is there any way I can capture
> the view before it is dropped or stop the drop from occuring. I am sure
> if I can get hold of this view then I will be able to find the fault.
>
> I am confused as to why this has been fine on 10 of the publications
> then suddenly decided to error.
> The file versions I have are:
> SQLSRV32.DLL = 2000.81.9042.0
> SQLSRV32.RLL = 2000.81.9001.0
> odbcbcp.dll = 2000.81.9042.0
>
> Thanks
> Ian
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hilary,
Thanks for your responses.
The trouble is the temp view gets a new name each time I run the
snapshot so I do not know what to look for with sp_helptext.
I could drop the publication/subscription but it has over 100 tables
with un-merged data so I will have to manually put the data in(unless
there is an easier way that I do not know about ?)
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The way I view it you have about 4 options
1) call PSS
2) figure out the proc which is used to generate this view and modify it to
write a perm view.
3) create a new publication which has this problem filter in and deploy it
to the subscriber
4) backup the publication database and restore it on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eq1LVMMnEHA.608@.TK2MSFTNGP09.phx.gbl...
> Hilary,
> Thanks for your responses.
> The trouble is the temp view gets a new name each time I run the
> snapshot so I do not know what to look for with sp_helptext.
> I could drop the publication/subscription but it has over 100 tables
> with un-merged data so I will have to manually put the data in(unless
> there is an easier way that I do not know about ?)
> Regards,
> Ian
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||I've decided to raise a call at Microsoft. If I still cannot resolve
then I will just re-create the publication etc so I will loose nothing
by doing so (except a few ).
I will let you know the outcome.Thanks again for your responses.
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Sorry to post this one again but I have added some more info....
I have a sql2000 SP3 merge replication set up using dynamic filters
to 29 sites/publications so each site only see's it's own data.
I have been adding new tables to the schema using sp_mergearticle
(but that is another story !!). I have been running the
sp_mergearticle , running the snapshot, merging, new tables published
...etc OK. I did this 10 times and then hit the error The process
could not bulk copy out of table
'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
agent for one of the publications.
I added the -output (Outputverboselevel 2) and got the follow info at
the end (it failes when it starts to bulk copy)
Bulk copying snapshot data for system table 'MSmerge_contents'
select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
[9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
SourceTypeId = 5
SourceName = GODZILLA
ErrorCode = 8624
ErrorText = Internal SQL Server error.
The process could not bulk copy out of table
'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
Disconnecting from Publisher 'GODZILLA'
I ran the profiler whilst the snapshot was generated, I could see the
view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
(any anything else it had temp created) Is there any way I can capture
the view before it is dropped or stop the drop from occuring. I am sure
if I can get hold of this view then I will be able to find the fault.
I am confused as to why this has been fine on 10 of the publications
then suddenly decided to error.
The file versions I have are:
SQLSRV32.DLL = 2000.81.9042.0
SQLSRV32.RLL = 2000.81.9001.0
odbcbcp.dll = 2000.81.9042.0
Thanks
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
I've had my share of problems with dynamic filters, but not the one you are
encountering. Can you drop this subscription and filter and then try to
recreate it using another folder?
If you want to catch this transitory view you are best to query it in the
publication database.
IE repeatedly run
sp_helptext contE6E5BDF7F1C24EC588142A934ACF00D1
Or run profiler to try to capture its creation
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eesd36JnEHA.556@.tk2msftngp13.phx.gbl...
> Hi all,
> Sorry to post this one again but I have added some more info....
>
> I have a sql2000 SP3 merge replication set up using dynamic filters
> to 29 sites/publications so each site only see's it's own data.
> I have been adding new tables to the schema using sp_mergearticle
> (but that is another story !!). I have been running the
> sp_mergearticle , running the snapshot, merging, new tables published
> ...etc OK. I did this 10 times and then hit the error The process
> could not bulk copy out of table
> 'contE6E5BDF7F1C24EC588142A934ACF00D1'. when running the snapshot
> agent for one of the publications.
> I added the -output (Outputverboselevel 2) and got the follow info at
> the end (it failes when it starts to bulk copy)
> Bulk copying snapshot data for system table 'MSmerge_contents'
> select * from cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> [9/16/2004 2:56:22 PM]GODZILLA.MearsData: select * from
> cont21D0C82D8E3E47B8A3C3BC024732C0AC where 1 = 2
> SourceTypeId = 5
> SourceName = GODZILLA
> ErrorCode = 8624
> ErrorText = Internal SQL Server error.
> The process could not bulk copy out of table
> 'cont21D0C82D8E3E47B8A3C3BC024732C0AC'.
> Disconnecting from Publisher 'GODZILLA'
>
> I ran the profiler whilst the snapshot was generated, I could see the
> view contE6E5BDF7F1C24EC588142A934ACF00D1 being queried, then when it
> errored it sent a drop command on contE6E5BDF7F1C24EC588142A934ACF00D1
> (any anything else it had temp created) Is there any way I can capture
> the view before it is dropped or stop the drop from occuring. I am sure
> if I can get hold of this view then I will be able to find the fault.
>
> I am confused as to why this has been fine on 10 of the publications
> then suddenly decided to error.
> The file versions I have are:
> SQLSRV32.DLL = 2000.81.9042.0
> SQLSRV32.RLL = 2000.81.9001.0
> odbcbcp.dll = 2000.81.9042.0
>
> Thanks
> Ian
>
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||Hilary,
Thanks for your responses.
The trouble is the temp view gets a new name each time I run the
snapshot so I do not know what to look for with sp_helptext.
I could drop the publication/subscription but it has over 100 tables
with un-merged data so I will have to manually put the data in(unless
there is an easier way that I do not know about ?)
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||The way I view it you have about 4 options
1) call PSS
2) figure out the proc which is used to generate this view and modify it to
write a perm view.
3) create a new publication which has this problem filter in and deploy it
to the subscriber
4) backup the publication database and restore it on the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"ian bentley" <ian@.ianpb.fsnet.co.uk> wrote in message
news:eq1LVMMnEHA.608@.TK2MSFTNGP09.phx.gbl...
> Hilary,
> Thanks for your responses.
> The trouble is the temp view gets a new name each time I run the
> snapshot so I do not know what to look for with sp_helptext.
> I could drop the publication/subscription but it has over 100 tables
> with un-merged data so I will have to manually put the data in(unless
> there is an easier way that I do not know about ?)
> Regards,
> Ian
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||I've decided to raise a call at Microsoft. If I still cannot resolve
then I will just re-create the publication etc so I will loose nothing
by doing so (except a few ).
I will let you know the outcome.Thanks again for your responses.
Regards,
Ian
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Tuesday, February 14, 2012
Corrupted Model DB
I have a sql 2k sp3 db server that isn't starting. It's giving an error message that says "Errror: 9003 Severity 20, State 1. The LSN (626:44:1) passed to log scan in database model is invalid."
I tried starting the server in single user mode (sqlservr.exe -c -m) hoping to just restore the model database.
However, I am still unable to connect to the database using Ent Mgr or SQL Query Analyzer. Both applications give me a "SQL Server does not exist or access is denied" message.
I've got a few questions:
- Based on the error message, #9003, am I right in thinking that I can restore a good backup of my model db to fix my problem?
- Should I be able to connect to my server using SQL Ent Mgr or SQL Query Analyzer when it is started in single user mode? If not, do I need to use OSQL?
- Am I wasting my time with this approach and should I just rebuild my master db? <groan>
TIA,
-StuartYou should be able to restore the model database with either Enterprise
Manager or Query Analyzer. Make sure that SQL Server Agent is not running.
Make sure that SQL Server is listening on named pipes and try to connect to
SQL Server using a "." from Query Analyser.
Rand
This posting is provided "as is" with no warranties and confers no rights.
I tried starting the server in single user mode (sqlservr.exe -c -m) hoping to just restore the model database.
However, I am still unable to connect to the database using Ent Mgr or SQL Query Analyzer. Both applications give me a "SQL Server does not exist or access is denied" message.
I've got a few questions:
- Based on the error message, #9003, am I right in thinking that I can restore a good backup of my model db to fix my problem?
- Should I be able to connect to my server using SQL Ent Mgr or SQL Query Analyzer when it is started in single user mode? If not, do I need to use OSQL?
- Am I wasting my time with this approach and should I just rebuild my master db? <groan>
TIA,
-StuartYou should be able to restore the model database with either Enterprise
Manager or Query Analyzer. Make sure that SQL Server Agent is not running.
Make sure that SQL Server is listening on named pipes and try to connect to
SQL Server using a "." from Query Analyser.
Rand
This posting is provided "as is" with no warranties and confers no rights.
Subscribe to:
Posts (Atom)