Cannot Register Remote Server

Dear all,
I've installed SQL2005 on my local machine. And there is another SERVER whic
h has install both SQL2000 and SQL2005. I can use my local Management Studio
to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL200
5 instance.
How can I register and connect to the SERVER\SQL2005 server?
The SERVER\SQL2005 has been configured to enable the protocols of shared mem
ory, namepipe and tcpip already.
The SERVER has installed SQL2000 first and then install SQL2005 server.
Thanks a lot.
Regards,
Alex AUHi Alex
Can you conncet to this server using SQLCMD? If not check that Remote
Connections have been set in the surface area configuration tool.
John
"Alex AU" wrote:

> Dear all,
> I've installed SQL2005 on my local machine. And there is another SERVER wh
ich has install both SQL2000 and SQL2005. I can use my local Management Stud
io to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL2
005 instance.
> How can I register and connect to the SERVER\SQL2005 server?
> The SERVER\SQL2005 has been configured to enable the protocols of shared m
emory, namepipe and tcpip already.
> The SERVER has installed SQL2000 first and then install SQL2005 server.
> Thanks a lot.
>
> Regards,
> Alex AU|||Alex AU wrote:
> Dear all,
> I've installed SQL2005 on my local machine. And there is another
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> How can I register and connect to the SERVER\SQL2005 server?
> The SERVER\SQL2005 has been configured to enable the protocols
> of shared memory, namepipe and tcpip already.
> The SERVER has installed SQL2000 first and then install SQL2005 server.
> Thanks a lot.
>
> Regards,
> Alex AU
Are both SQL2000 and SQL2005 installed as named instances on the server?
It could be that SQL2000 is installed as a default instance (hence you
can connect to it just with the servername) and SQL2005 is installed as
a named instance so you need to use that instance name to connect.
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||Dear John,
I've already setup the remote connections to accept namepine and tcpip conne
ction in the surface area configuration tool.
I can use ODBC to establish connection from my workstation to the SERVER\SQL
2005 but just cannot register the server in the Management Studio on my work
station.
Thanks.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:3238D38E-5324
-49BB-A188-43078C16F3A1@.microsoft.com...
Hi Alex
Can you conncet to this server using SQLCMD? If not check that Remote
Connections have been set in the surface area configuration tool.
John
"Alex AU" wrote:

> Dear all,
>
> I've installed SQL2005 on my local machine. And there is another SERVER wh
ich has install both SQL2000 and SQL2005. I can use my local Management Stud
io to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL2
005 instance.
>
> How can I register and connect to the SERVER\SQL2005 server?
>
> The SERVER\SQL2005 has been configured to enable the protocols of shared m
emory, namepipe and tcpip already.
>
> The SERVER has installed SQL2000 first and then install SQL2005 server.
>
> Thanks a lot.
>
>
>
> Regards,
>
> Alex AU|||Dear Steen,
The SQL2000 is the default instance and SQL2005 is a named instance. When I
register the SQL2005 on my workstation's Management Studio, I've already use
d the name instance to try connect but it failed.
I've already set the remote connection with namepipe and tcpip in the servic
e area configuration on the server. When I try to use ODBC on my workstation
to connect to the SERVER\SQL2005, I can successfully establish the connecti
on. I just cannot register the SERVER\SQL2005 on my workstation's management
studio.
Thanks
Regards,
Alex AU
"Steen Persson (DK)" <spe@.REMOVEdatea.dk> wrote in message news:u0NxbpJrGHA.
2256@.TK2MSFTNGP03.phx.gbl...
Alex AU wrote:
Dear all,
I've installed SQL2005 on my local machine. And there is another SERVER whic
h has install both SQL2000 and SQL2005. I can use my local Management Studio
to register the SERVER\SQL2000 instance but I cannot register SERVER\SQL200
5 instance.
How can I register and connect to the SERVER\SQL2005 server?
The SERVER\SQL2005 has been configured to enable the protocols of shared mem
ory, namepipe and tcpip already.
The SERVER has installed SQL2000 first and then install SQL2005 server.
Thanks a lot.
Regards,
Alex AU
Are both SQL2000 and SQL2005 installed as named instances on the server? It
could be that SQL2000 is installed as a default instance (hence you can conn
ect to it just with the servername) and SQL2005 is installed as a named inst
ance so you need to use that instance name to connect.
--
Regards
Steen Schlüter Persson
Databaseadministrator / Systemadministrator|||Hi Alex
And SQLCMD allows you to connect?
John
"Alex AU" wrote:

> Dear John,
> I've already setup the remote connections to accept namepine and tcpip
> connection in the surface area configuration tool.
> I can use ODBC to establish connection from my workstation to the
> SERVER\SQL2005 but just cannot register the server in the Management
> Studio on my workstation.
> Thanks.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3238D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...
> Hi Alex
> Can you conncet to this server using SQLCMD? If not check that Remote
> Connections have been set in the surface area configuration tool.
> John
> "Alex AU" wrote:
>
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> shared memory, namepipe and tcpip already.
> server.
>|||Dear John,
I've tried sqlcmd, it also failed. The command I used and error as follow:
sqlcmd -S SERVER\SQL2005
HResult 0xFFFFFFFF, Level 16, State 1
SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFF
FFF].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while est
abli
shing a connection to the server. When connecting to SQL Server 2005, this f
ailu
re may be caused by the fact that under the default settings SQL Server does
not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
Thanks a lot.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:342A5195-A4E1
-4477-AFDF-F592B3809BDC@.microsoft.com...
Hi Alex
And SQLCMD allows you to connect?
John
"Alex AU" wrote:

> Dear John,
>
> I've already setup the remote connections to accept namepine and tcpip
> connection in the surface area configuration tool.
>
> I can use ODBC to establish connection from my workstation to the
> SERVER\SQL2005 but just cannot register the server in the Management
> Studio on my workstation.
>
> Thanks.
>
>
>
> Regards,
>
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:3238D38E-5324-49BB-A188-43078C16F3A1@.microsoft.com...
> Hi Alex
>
> Can you conncet to this server using SQLCMD? If not check that Remote
> Connections have been set in the surface area configuration tool.
>
> John
>
> "Alex AU" wrote:
>
> SERVER which has install both SQL2000 and SQL2005. I can use my local
> Management Studio to register the SERVER\SQL2000 instance but I cannot
> register SERVER\SQL2005 instance.
> shared memory, namepipe and tcpip already.
> server.
>|||Hi Alex
This is indicating that the remote connections setting are not set on the
protocols. What does the SQLServer 2005 Configuration Manager tool say (i.e.
not SAC!). Also make sure that you can resolve the server name correctly.
You may also want to look at SQLPing to to see to search for servers
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
John
"Alex AU" wrote:

> Dear John,
> I've tried sqlcmd, it also failed. The command I used and error as follow:
> sqlcmd -S SERVER\SQL2005
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
> Thanks a lot.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:342A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...
> Hi Alex
> And SQLCMD allows you to connect?
> John
> "Alex AU" wrote:
>
> Remote
>|||Thanks John,
I've used the tools on that SERVER and I've found that the port number for S
QL2005 using is 1025. (SQL2000 use 1433).
I finally figure out what causing the connection issue, it's the firewall se
ttings. I use a Windows XP with SP2 as a server and the firewall has turned
on. It only allow SQL connection from port 1433 and that's the reason why I
cannot connect with SQL Management Studio with port 1025 (SQL2005). When I s
hut down the firewall, it works.
Sorry for the chaos that I've made. But I really appreciate for your kindly
help.
I've got one more question related to this. I've tried to add exception rule
in the XP firewall settings for port 1025, but I still cannot connect. I ca
n only connect when the firewall is off. Can anyone help with this? (or shou
ld I post in other newsgroup for this issue?)
Thanks.
Regards,
Alex AU
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:E4A5B93E-6A03
-4406-87B6-399E4A150D02@.microsoft.com...
Hi Alex
This is indicating that the remote connections setting are not set on the
protocols. What does the SQLServer 2005 Configuration Manager tool say (i.e.
not SAC!). Also make sure that you can resolve the server name correctly.
You may also want to look at SQLPing to to see to search for servers
http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
John
"Alex AU" wrote:

> Dear John,
>
> I've tried sqlcmd, it also failed. The command I used and error as follow:
>
> sqlcmd -S SERVER\SQL2005
>
> HResult 0xFFFFFFFF, Level 16, State 1
> SQL Network Interfaces: Error Locating Server/Instance Specified
> [xFFFFFFFF].
> Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while
> establi
> shing a connection to the server. When connecting to SQL Server 2005, this
> failu
> re may be caused by the fact that under the default settings SQL Server
> does not
> allow remote connections..
> Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.
>
> Thanks a lot.
>
>
>
> Regards,
>
> Alex AU
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:342A5195-A4E1-4477-AFDF-F592B3809BDC@.microsoft.com...
> Hi Alex
>
> And SQLCMD allows you to connect?
>
> John
>
> "Alex AU" wrote:
>
> Remote
>|||Hi
I don't know the intricacies of the XP firewall as I have always used a
third party one. The following describes what you should need to set up in
terms of rules, change this for the port you are using and it should be ok.
http://support.microsoft.com/kb/287932
John
"Alex AU" wrote:

> Thanks John,
> I've used the tools on that SERVER and I've found that the port number for
> SQL2005 using is 1025. (SQL2000 use 1433).
> I finally figure out what causing the connection issue, it's the firewall
> settings. I use a Windows XP with SP2 as a server and the firewall has
> turned on. It only allow SQL connection from port 1433 and that's the
> reason why I cannot connect with SQL Management Studio with port 1025
> (SQL2005). When I shut down the firewall, it works.
> Sorry for the chaos that I've made. But I really appreciate for your
> kindly help.
> I've got one more question related to this. I've tried to add exception
> rule in the XP firewall settings for port 1025, but I still cannot
> connect. I can only connect when the firewall is off. Can anyone help with
> this? (or should I post in other newsgroup for this issue?)
> Thanks.
>
> Regards,
> Alex AU
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:E4A5B93E-6A03-4406-87B6-399E4A150D02@.microsoft.com...
> Hi Alex
> This is indicating that the remote connections setting are not set on
> the
> protocols. What does the SQLServer 2005 Configuration Manager tool say
> (i.e.
> not SAC!). Also make sure that you can resolve the server name
> correctly.
> You may also want to look at SQLPing to to see to search for servers
> http://www.sqlsecurity.com/Tools/Fr...65/Default.aspx
> John
> "Alex AU" wrote:
>
> follow:
> while
> this
> Server
> tcpip
> Management
> tool.
> another
> local
> cannot
> of
> SQL2005
>

Cannot read the next data row for the data set abc.

Dear All.

I am facing the above mentioned error quite frequently. I am using SQL 2005 reporting services and my database is in SQL 2005. I am using a stored procedure and pass the parameters to the SP through the report. The SP returns the results in about 4-5 seconds at max but when the report is run, it usually takes a long time for processing and then it throws the following error:

Cannot read the next data row for the data set ABC. A severe error occurred on the current command. The results, if any, should be discarded.

Can anyone from Microsoft please specify the exact reason for this error and how can we solve it?

Also there is another problem, some of my reports use SPs. When the SPs are run independantly, they return the results efficiently in about 2-3 seconds but when the report is run using the same SPs, the report returns the results in 2-3 minutes. Any reasons? Any configuration change that may be required for reporting server?

Thanks in advance.

Kashif

Hello,

I have similar problem. My RS 2005 report is based on query like dataset but it uses UDFs to recive some data. When I run it sometimes I get such a result:

An error has occurred during report processing. (rsProcessingAborted)

Cannot read the next data row for the data set MainDataSource. (rsErrorReadingNextDataRow)

Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.|||

You might try to add a NOLOCK hint to your joins.

Or you can 'set transaction isolation level read uncommitted' for procs where you don't want to issue read locks.

That might help.

Jarret

|||

Dear Jarret.

i have already tried the read uncommitted isolation level but no use. The problem is intermittant and we dont exactly know when and why does this occur. sometimes the report runs fine and at other times, it generates this problem. I hope to get an answer from Microsoft as this is starting to create problems for us as the number of report users increase, the error is occurring more frequently.

Regards

|||

I think it's caused by Reporting Services not by SQL Server itself. When I run my report query from Management Studio I always get results. The error with deadlock occurs only in Reporting Services...

I've also noticed that this error frequency rises with the number of users using the database (but that should be obvious).

Regards

Maciej

|||

Has the problem been solved yet? I too am having the same problem -- I'm wondering if it's associated with the upgrade to SQL Server 2005 SP2?

--Peter

Cannot read the next data row for the data set abc.

Dear All.

I am facing the above mentioned error quite frequently. I am using SQL 2005 reporting services and my database is in SQL 2005. I am using a stored procedure and pass the parameters to the SP through the report. The SP returns the results in about 4-5 seconds at max but when the report is run, it usually takes a long time for processing and then it throws the following error:

Cannot read the next data row for the data set ABC. A severe error occurred on the current command. The results, if any, should be discarded.

Can anyone from Microsoft please specify the exact reason for this error and how can we solve it?

Also there is another problem, some of my reports use SPs. When the SPs are run independantly, they return the results efficiently in about 2-3 seconds but when the report is run using the same SPs, the report returns the results in 2-3 minutes. Any reasons? Any configuration change that may be required for reporting server?

Thanks in advance.

Kashif

Hello,

I have similar problem. My RS 2005 report is based on query like dataset but it uses UDFs to recive some data. When I run it sometimes I get such a result:

An error has occurred during report processing. (rsProcessingAborted)

Cannot read the next data row for the data set MainDataSource. (rsErrorReadingNextDataRow)

Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.|||

You might try to add a NOLOCK hint to your joins.

Or you can 'set transaction isolation level read uncommitted' for procs where you don't want to issue read locks.

That might help.

Jarret

|||

Dear Jarret.

i have already tried the read uncommitted isolation level but no use. The problem is intermittant and we dont exactly know when and why does this occur. sometimes the report runs fine and at other times, it generates this problem. I hope to get an answer from Microsoft as this is starting to create problems for us as the number of report users increase, the error is occurring more frequently.

Regards

|||

I think it's caused by Reporting Services not by SQL Server itself. When I run my report query from Management Studio I always get results. The error with deadlock occurs only in Reporting Services...

I've also noticed that this error frequency rises with the number of users using the database (but that should be obvious).

Regards

Maciej

|||

Has the problem been solved yet? I too am having the same problem -- I'm wondering if it's associated with the upgrade to SQL Server 2005 SP2?

--Peter

Cannot read the next data row for the data set abc.

Dear All.

I am facing the above mentioned error quite frequently. I am using SQL 2005 reporting services and my database is in SQL 2005. I am using a stored procedure and pass the parameters to the SP through the report. The SP returns the results in about 4-5 seconds at max but when the report is run, it usually takes a long time for processing and then it throws the following error:

Cannot read the next data row for the data set ABC. A severe error occurred on the current command. The results, if any, should be discarded.

Can anyone from Microsoft please specify the exact reason for this error and how can we solve it?

Also there is another problem, some of my reports use SPs. When the SPs are run independantly, they return the results efficiently in about 2-3 seconds but when the report is run using the same SPs, the report returns the results in 2-3 minutes. Any reasons? Any configuration change that may be required for reporting server?

Thanks in advance.

Kashif

Hello,

I have similar problem. My RS 2005 report is based on query like dataset but it uses UDFs to recive some data. When I run it sometimes I get such a result:

An error has occurred during report processing. (rsProcessingAborted)

Cannot read the next data row for the data set MainDataSource. (rsErrorReadingNextDataRow)

Transaction (Process ID 62) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.|||

You might try to add a NOLOCK hint to your joins.

Or you can 'set transaction isolation level read uncommitted' for procs where you don't want to issue read locks.

That might help.

Jarret

|||

Dear Jarret.

i have already tried the read uncommitted isolation level but no use. The problem is intermittant and we dont exactly know when and why does this occur. sometimes the report runs fine and at other times, it generates this problem. I hope to get an answer from Microsoft as this is starting to create problems for us as the number of report users increase, the error is occurring more frequently.

Regards

|||

I think it's caused by Reporting Services not by SQL Server itself. When I run my report query from Management Studio I always get results. The error with deadlock occurs only in Reporting Services...

I've also noticed that this error frequency rises with the number of users using the database (but that should be obvious).

Regards

Maciej

|||

Has the problem been solved yet? I too am having the same problem -- I'm wondering if it's associated with the upgrade to SQL Server 2005 SP2?

--Peter

sql

cannot query directory services

Dear all,
I would like to query informations that are located in the (AD) Active
Directory Windows 2003 with my server Windows 2000SP4 and MS SQL 2000 SP4 in
the same domain and AD.
I create the link server with the following script :
EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
'ADSDSOObject', 'adsdatasource'
GO
and I query AD with the following :
SELECT [Name], SN [Last Name], ST State
FROM OPENQUERY( ADSI,
'SELECT Name, SN, ST
FROM ''LDAP://ADSISrv/ OU=myOU,DC=mycompagny,DC=com''
WHERE objectCategory = ''Person'' AND
objectClass = ''contact''')
GO
Then I get the following error :
Server: Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing a query for execution against OLE DB
provider 'ADSDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Prep
are
returned 0x80040e14].
I clarify that I used Integrated Windows security and also used the USERID
and password of service SQLserver as recommanded to launch my query.
But I get the above error. Why ?
Thanks for your next reply,
JobHi
You may get a better response in the ADSI news groups e.g
microsoft.public.adsi.general, but I think the error is probably because the
syntax of your query is incorrect, check out
http://msdn.microsoft.com/library/d...ap_provider.asp
John
"Job" wrote:

> Dear all,
> I would like to query informations that are located in the (AD) Active
> Directory Windows 2003 with my server Windows 2000SP4 and MS SQL 2000 SP4
in
> the same domain and AD.
> I create the link server with the following script :
> EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
> 'ADSDSOObject', 'adsdatasource'
> GO
> and I query AD with the following :
> SELECT [Name], SN [Last Name], ST State
> FROM OPENQUERY( ADSI,
> 'SELECT Name, SN, ST
> FROM ''LDAP://ADSISrv/ OU=myOU,DC=mycompagny,DC=com''
> WHERE objectCategory = ''Person'' AND
> objectClass = ''contact''')
> GO
> Then I get the following error :
> Server: Msg 7321, Level 16, State 2, Line 1
> An error occurred while preparing a query for execution against OLE DB
> provider 'ADSDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Pr
epare
> returned 0x80040e14].
> I clarify that I used Integrated Windows security and also used the USERID
> and password of service SQLserver as recommanded to launch my query.
> But I get the above error. Why ?
> Thanks for your next reply,
> Job
>
>

cannot query directory services

Dear all,
I would like to query informations that are located in the (AD) Active
Directory Windows 2003 with my server Windows 2000SP4 and MS SQL 2000 SP4 in
the same domain and AD.
I create the link server with the following script :
EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
'ADSDSOObject', 'adsdatasource'
GO
and I query AD with the following :
SELECT [Name], SN [Last Name], ST State
FROM OPENQUERY( ADSI,
'SELECT Name, SN, ST
FROM ''LDAP://ADSISrv/ OU=myOU,DC=mycompagny,DC=com''
WHERE objectCategory = ''Person'' AND
objectClass = ''contact''')
GO
Then I get the following error :
Server: Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing a query for execution against OLE DB
provider 'ADSDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Prepare
returned 0x80040e14].
I clarify that I used Integrated Windows security and also used the USERID
and password of service SQLserver as recommanded to launch my query.
But I get the above error. Why ?
Thanks for your next reply,
JobHi
You may get a better response in the ADSI news groups e.g
microsoft.public.adsi.general, but I think the error is probably because the
syntax of your query is incorrect, check out
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/adsi_ldap_provider.asp
John
"Job" wrote:
> Dear all,
> I would like to query informations that are located in the (AD) Active
> Directory Windows 2003 with my server Windows 2000SP4 and MS SQL 2000 SP4 in
> the same domain and AD.
> I create the link server with the following script :
> EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
> 'ADSDSOObject', 'adsdatasource'
> GO
> and I query AD with the following :
> SELECT [Name], SN [Last Name], ST State
> FROM OPENQUERY( ADSI,
> 'SELECT Name, SN, ST
> FROM ''LDAP://ADSISrv/ OU=myOU,DC=mycompagny,DC=com''
> WHERE objectCategory = ''Person'' AND
> objectClass = ''contact''')
> GO
> Then I get the following error :
> Server: Msg 7321, Level 16, State 2, Line 1
> An error occurred while preparing a query for execution against OLE DB
> provider 'ADSDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Prepare
> returned 0x80040e14].
> I clarify that I used Integrated Windows security and also used the USERID
> and password of service SQLserver as recommanded to launch my query.
> But I get the above error. Why ?
> Thanks for your next reply,
> Job
>
>sql

cannot query directory services

Dear all,
I would like to query informations that are located in the (AD) Active
Directory Windows 2003 with my server Windows 2000SP4 and MS SQL 2000 SP4 in
the same domain and AD.
I create the link server with the following script :
EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
'ADSDSOObject', 'adsdatasource'
GO
and I query AD with the following :
SELECT [Name], SN [Last Name], ST State
FROM OPENQUERY( ADSI,
'SELECT Name, SN, ST
FROM ''LDAP://ADSISrv/ OU=myOU,DC=mycompagny,DC=com''
WHERE objectCategory = ''Person'' AND
objectClass = ''contact''')
GO
Then I get the following error :
Server: Msg 7321, Level 16, State 2, Line 1
An error occurred while preparing a query for execution against OLE DB
provider 'ADSDSOObject'.
OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Prepare
returned 0x80040e14].
I clarify that I used Integrated Windows security and also used the USERID
and password of service SQLserver as recommanded to launch my query.
But I get the above error. Why ?
Thanks for your next reply,
Job
Hi
You may get a better response in the ADSI news groups e.g
microsoft.public.adsi.general, but I think the error is probably because the
syntax of your query is incorrect, check out
http://msdn.microsoft.com/library/de...p_provider.asp
John
"Job" wrote:

> Dear all,
> I would like to query informations that are located in the (AD) Active
> Directory Windows 2003 with my server Windows 2000SP4 and MS SQL 2000 SP4 in
> the same domain and AD.
> I create the link server with the following script :
> EXEC sp_addlinkedserver 'ADSI', 'Active Directory Services 2.5',
> 'ADSDSOObject', 'adsdatasource'
> GO
> and I query AD with the following :
> SELECT [Name], SN [Last Name], ST State
> FROM OPENQUERY( ADSI,
> 'SELECT Name, SN, ST
> FROM ''LDAP://ADSISrv/ OU=myOU,DC=mycompagny,DC=com''
> WHERE objectCategory = ''Person'' AND
> objectClass = ''contact''')
> GO
> Then I get the following error :
> Server: Msg 7321, Level 16, State 2, Line 1
> An error occurred while preparing a query for execution against OLE DB
> provider 'ADSDSOObject'.
> OLE DB error trace [OLE/DB Provider 'ADSDSOObject' ICommandPrepare::Prepare
> returned 0x80040e14].
> I clarify that I used Integrated Windows security and also used the USERID
> and password of service SQLserver as recommanded to launch my query.
> But I get the above error. Why ?
> Thanks for your next reply,
> Job
>
>

Cannot open user default Database login failed

Dear all,

I got the error message:

Error 27052 Could not connect to Microsoft SQL Server 'VPC' Cannot open User default Database login failed.

This error is happened when installing one application to Virtual Machine (Machine name: VPC).

Does anyone knows how to solve this problem? I checked from www.microsoft.com but i just got the limited information:

27502

The parameter is not valid.

Not applicable

SSCE_M_CMN_INVALIDPARAMETER

There is no further information.

Thanks & Regards,

Agus Suryadi

When you log in to SQL Server, SQL Server figures out who you are and then puts your session into a specific database. The database it puts you into is either the one you specified on your connection string (if you specified one) or into your default database, the database that your login has as its default.

If you can get into the SQL Server you could check the login you were connecting with to see what its default database is, then check to see if a database with that name currently exists.

Perhaps the application that is being installed expects a certain database to already be created, but apparently it's not there (or the Login/user doesn't have permissions to access it).

Don

Cannot insert the value NULL into column 'ID'

Hi dear experts:

The message is

"Cannot insert the value NULL into column 'ID_Month', table 'Database_DW.dbo.Incident_Summary'; column does not allow nulls..."

At my table, I have a primary key which make autonumber for any record set in column 'ID_Month'. How can I insert autonumber in column 'ID_Month'by SQL statement?

Thank you in advance.

It's possible you are explictly inserting null into the column rather than ignoring it. Check all column mappings and sql statements to ensure you are not referencing that column. For example:

insert Database_DW.dbo.Incident_Summary(ID_Month, column1) select(NULL,somevalue) from sometable; would return that error.

|||

Hi Michanne,

thank you for the quick respond. Yes, you are wright, I am inserting nulls in the column that does not allow nulls.

My question is how to insert next number in the column by sql statement. I copied the d/base with data, 57 records exists in it and I don't know how to insert the record that will be number 58.

Thanks.

|||

Leave it empty in your statement. Don't reference in your column list either. It will insert it automatically as long as 58 is the next identity value. (SELECT IDENT_SEED('table') will tell you this.) I think that is what you are getting at....

There are also functions that allow you to override the identity key value but you only need to do that if you care about the value or have to correct the value in the table. To do that look up the syntax for "Set Identity insert" in BOL.

Hope that helps!

|||

Thanks for following michanne!

I can't leave it. In this case I receive a message "Cannot insert the value NULL into column 'ID_Month'. It is something with identity syntax. I can't figure out.

Thank you!

|||

Check the schema. If it is >truly< an identity it will work to insert all other columns and ignore the one that is an identity.

|||

Once again, thank you!! Checked the schema, no identity, it is float with no null values.

Your suggestion was so helpful!!

CANNOT GENERATE SSPI CONTENT

Dear support,
I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
Server SP4. However, when I register the SQL Server through Enterprise
Manager (or connect the SQL Server through Query Analyzer), the error:
A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
REASON: CANNOT GENERATE SSPI CONTENT
PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
However, I can succesfully register by typing the IP Address.
Can anyone help?Maybe the server is unable to resolve the "mySQLServer" name? Can you ping
it? Are you trying to connect using Named Pipes? Is it using port 1433?
I would consider adding an Alias to the client network utility that points
"mySQLServer" at the IP address that works correctly (and of course points
to the correct port).
Or, if it ain't broke, don't fix it; since IP address works, use the IP
address?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>|||Probably problem is with your DNS, on the computer on which SQL server is
installed check computer name and primary DNS suffix.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>|||Hi all,
I can successfully ping my SQL server (with my SQL server name is the same
as my Server name).
It is quite impossible to use IP as my system (a lot of programs and
configure) has been developed and is using SQL server name for the SQL
connection.
BTW, I have many SQL server and only this SQL server got the "Cannot
generate SSPI content" problem. Any more hints ?
"Daniel Joskovski" wrote:
> Probably problem is with your DNS, on the computer on which SQL server is
> installed check computer name and primary DNS suffix.
> Regards,
> Daniel
> "jenny" <jenny@.discussions.microsoft.com> wrote in message
> news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> > Dear support,
> >
> > I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> > Server SP4. However, when I register the SQL Server through Enterprise
> > Manager (or connect the SQL Server through Query Analyzer), the error:
> > A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> > REASON: CANNOT GENERATE SSPI CONTENT
> > PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> > PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> > However, I can succesfully register by typing the IP Address.
> >
> > Can anyone help?
> >
> >
>
>|||> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
(a) the name of the data source should not be hard-coded into programs. At
the very least, all of your applications should get this kind of global
parameter from a single, central location. In your current state, what are
you going to do when you change the SQL auth password? Or switch from SQL
auth to Windows auth? Or move the database to a server with a different
name?
(b) barring (a), have you seen my suggestion to add the server name -> IP
mapping in the client network utility on the workstations that can't connect
to this SQL Server by name?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Hi Aaron,
Thanks first.
The SQL server name is not hardcode... It is stored in the configuration
file or database value. To be more accurate, now my system is working fine
by using the SQL Server Name except for the following cases:
- Register the SQL Server through Enterprise Manager
- Connect to the SQL Server through Query Analyzer
- Run osql command with connection typed with the SQL Server Name
Some of my predefined script are coded with the SQL Server Name and is
worked fine for other SQL Servers except the one I mentioned. I even got the
same problem when I connect the SQL Server on the same Server. (e.g. The SQL
Server A is installed in the Windows Server A.) However, I have one finding
that if I add the SQL Server IP entry in the "host" file, I can then solve
the above 3 problems. I wonder, is adding the host file the only
(appropriate) way to solve the problem ? Is there any other methods as I
only got one SQL Server having this problem. Thanks a lot again.
For more information, my SQL Server is running cluster, using NamePiped and
TCP/IP connection with port 1433.
For your option (b), I'll consider... But curious that why other SQL servers
of my system works without problem (they have similar settings during
installation)
"Aaron [SQL Server MVP]" wrote:
> > It is quite impossible to use IP as my system (a lot of programs and
> > configure) has been developed and is using SQL server name for the SQL
> > connection.
> (a) the name of the data source should not be hard-coded into programs. At
> the very least, all of your applications should get this kind of global
> parameter from a single, central location. In your current state, what are
> you going to do when you change the SQL auth password? Or switch from SQL
> auth to Windows auth? Or move the database to a server with a different
> name?
> (b) barring (a), have you seen my suggestion to add the server name -> IP
> mapping in the client network utility on the workstations that can't connect
> to this SQL Server by name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>|||It is possible to ping your server name and still have problems with DNS,
try to ping FQDN for example instead of Ping Stockholm, ping
Stockholm.nwtraders.msft or better check full name of computer on which is
SQL server installed.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:952A3B38-2035-4D64-95FA-0CC2F0F2BB87@.microsoft.com...
> Hi all,
> I can successfully ping my SQL server (with my SQL server name is the same
> as my Server name).
> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
> BTW, I have many SQL server and only this SQL server got the "Cannot
> generate SSPI content" problem. Any more hints ?
> "Daniel Joskovski" wrote:
> > Probably problem is with your DNS, on the computer on which SQL server
is
> > installed check computer name and primary DNS suffix.
> > Regards,
> > Daniel
> >
> > "jenny" <jenny@.discussions.microsoft.com> wrote in message
> > news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> > > Dear support,
> > >
> > > I'm running SQL Server Enterprise Edition with SP3a on Windows
Advanced
> > > Server SP4. However, when I register the SQL Server through
Enterprise
> > > Manager (or connect the SQL Server through Query Analyzer), the error:
> > > A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> > > REASON: CANNOT GENERATE SSPI CONTENT
> > > PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER
REGISRATION
> > > PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY
AGAIN
> > > However, I can succesfully register by typing the IP Address.
> > >
> > > Can anyone help?
> > >
> > >
> >
> >
> >

CANNOT GENERATE SSPI CONTENT

Dear support,
I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
Server SP4. However, when I register the SQL Server through Enterprise
Manager (or connect the SQL Server through Query Analyzer), the error:
A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
REASON: CANNOT GENERATE SSPI CONTENT
PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
However, I can succesfully register by typing the IP Address.
Can anyone help?
Maybe the server is unable to resolve the "mySQLServer" name? Can you ping
it? Are you trying to connect using Named Pipes? Is it using port 1433?
I would consider adding an Alias to the client network utility that points
"mySQLServer" at the IP address that works correctly (and of course points
to the correct port).
Or, if it ain't broke, don't fix it; since IP address works, use the IP
address?
http://www.aspfaq.com/
(Reverse address to reply.)
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>
|||Probably problem is with your DNS, on the computer on which SQL server is
installed check computer name and primary DNS suffix.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
> Dear support,
> I'm running SQL Server Enterprise Edition with SP3a on Windows Advanced
> Server SP4. However, when I register the SQL Server through Enterprise
> Manager (or connect the SQL Server through Query Analyzer), the error:
> A CONNECTION COULD NOT BE ESTABLISTHED TO <my SQL Server>
> REASON: CANNOT GENERATE SSPI CONTENT
> PLEASE VERIFY SQL SERVER IS RUNNING AND CHECK YOUR SQL SERVER REGISRATION
> PROPERTIES (BY RIGHT-CLICKING ON THE <my SQL Server> NODE) AND TRY AGAIN
> However, I can succesfully register by typing the IP Address.
> Can anyone help?
>
|||Hi all,
I can successfully ping my SQL server (with my SQL server name is the same
as my Server name).
It is quite impossible to use IP as my system (a lot of programs and
configure) has been developed and is using SQL server name for the SQL
connection.
BTW, I have many SQL server and only this SQL server got the "Cannot
generate SSPI content" problem. Any more hints ?
"Daniel Joskovski" wrote:

> Probably problem is with your DNS, on the computer on which SQL server is
> installed check computer name and primary DNS suffix.
> Regards,
> Daniel
> "jenny" <jenny@.discussions.microsoft.com> wrote in message
> news:B808753B-9601-4E94-9984-3C717EF093AA@.microsoft.com...
>
>
|||> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
(a) the name of the data source should not be hard-coded into programs. At
the very least, all of your applications should get this kind of global
parameter from a single, central location. In your current state, what are
you going to do when you change the SQL auth password? Or switch from SQL
auth to Windows auth? Or move the database to a server with a different
name?
(b) barring (a), have you seen my suggestion to add the server name -> IP
mapping in the client network utility on the workstations that can't connect
to this SQL Server by name?
http://www.aspfaq.com/
(Reverse address to reply.)
|||Hi Aaron,
Thanks first.
The SQL server name is not hardcode... It is stored in the configuration
file or database value. To be more accurate, now my system is working fine
by using the SQL Server Name except for the following cases:
- Register the SQL Server through Enterprise Manager
- Connect to the SQL Server through Query Analyzer
- Run osql command with connection typed with the SQL Server Name
Some of my predefined script are coded with the SQL Server Name and is
worked fine for other SQL Servers except the one I mentioned. I even got the
same problem when I connect the SQL Server on the same Server. (e.g. The SQL
Server A is installed in the Windows Server A.) However, I have one finding
that if I add the SQL Server IP entry in the "host" file, I can then solve
the above 3 problems. I wonder, is adding the host file the only
(appropriate) way to solve the problem ? Is there any other methods as I
only got one SQL Server having this problem. Thanks a lot again.
For more information, my SQL Server is running cluster, using NamePiped and
TCP/IP connection with port 1433.
For your option (b), I'll consider... But curious that why other SQL servers
of my system works without problem (they have similar settings during
installation)
"Aaron [SQL Server MVP]" wrote:

> (a) the name of the data source should not be hard-coded into programs. At
> the very least, all of your applications should get this kind of global
> parameter from a single, central location. In your current state, what are
> you going to do when you change the SQL auth password? Or switch from SQL
> auth to Windows auth? Or move the database to a server with a different
> name?
> (b) barring (a), have you seen my suggestion to add the server name -> IP
> mapping in the client network utility on the workstations that can't connect
> to this SQL Server by name?
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
>
|||It is possible to ping your server name and still have problems with DNS,
try to ping FQDN for example instead of Ping Stockholm, ping
Stockholm.nwtraders.msft or better check full name of computer on which is
SQL server installed.
Regards,
Daniel
"jenny" <jenny@.discussions.microsoft.com> wrote in message
news:952A3B38-2035-4D64-95FA-0CC2F0F2BB87@.microsoft.com...[vbcol=seagreen]
> Hi all,
> I can successfully ping my SQL server (with my SQL server name is the same
> as my Server name).
> It is quite impossible to use IP as my system (a lot of programs and
> configure) has been developed and is using SQL server name for the SQL
> connection.
> BTW, I have many SQL server and only this SQL server got the "Cannot
> generate SSPI content" problem. Any more hints ?
> "Daniel Joskovski" wrote:
is[vbcol=seagreen]
Advanced[vbcol=seagreen]
Enterprise[vbcol=seagreen]
REGISRATION[vbcol=seagreen]
AGAIN[vbcol=seagreen]

Cannot find the identity range allocation entry for the Subscriber

Dear All,
When I am synchronizing the merge push subscription, receiving following error
Cannot find the identity range allocation entry for the Subscriber in the
MSmerge_identity_range table. Reinitialize the subscription.
What could be the cause of message, and is there some way so I can avoid
re-initialization of susbscription
How did you deploy this subscriber? Did you do a no-sync?
"M. M. Ansari" <MMAnsari@.discussions.microsoft.com> wrote in message
news:15A3AA2B-9F5F-45BC-BBC7-4C48FEF239E7@.microsoft.com...
> Dear All,
> When I am synchronizing the merge push subscription, receiving following
> error
> Cannot find the identity range allocation entry for the Subscriber in the
> MSmerge_identity_range table. Reinitialize the subscription.
> What could be the cause of message, and is there some way so I can avoid
> re-initialization of susbscription
>