Tuesday, March 27, 2012
Cannot Register Remote Server
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
>
Tuesday, March 20, 2012
Cannot open database during merge replication
I am replicating an SQL2005 express machine to SQL2005 standard edition server using merge replication.
I have a simple VB application using ADO polling msMerge_history at the subscriber every second so that i can show the end user the progress of the replication.
When the subscription first subscribes and after the initial snapshot is applied replication downloads all changes from the server that have been changed since the snapshot was created.
Towards the end of this download faze the VB polling application fails with "Cannot open database "DBName" requested by the login. The login failed."
This connection fails 4 or 5 times and then normal polling resumes. The scary thing is that sometimes when the polling connection fails the merge replication does not complete and if i check msMerge_Sessions the "runstatus" is stuck at 3 (InProgress).
1) Is the reason the ADO polling connection fails because of some sort of lock between replication and reading the system tables?
2) Is replication getting stuck because of locks?
3) What can i do to get around this?
cheers,
Tim
Hello Tim,
Please try to use uncommited read isolation level (or SELECT ... WITH (NOLOCK) )when querying msMerge_Sessions table.
But result row set from this query contains uncommitted transactions.
This posting is provided AS IS with no warranties, and confers no rights
Cannot open database during merge replication
I have previously posted in the MSDN forums with no responses, so any
hints on this would be greatly appreciated.
I am replicating an SQL2005 express machine to SQL2005 standard
edition server using merge replication.
I have a simple VB application using ADO polling msMerge_history at
the subscriber every second so that i can show the end user the
progress of the replication.
When the subscription first subscribes and after the initial snapshot
is applied replication downloads all changes from the server that have
been changed since the snapshot was created.
Towards the end of this download faze the VB polling application fails
with "Cannot open database "DBName" requested by the login. The login
failed."
This connection fails 4 or 5 times and then normal polling resumes.
The scary thing is that sometimes when the polling connection fails
the merge replication does not complete and if i check
msMerge_Sessions the "runstatus" is stuck at 3 (InProgress).
1) Is the reason the ADO polling connection fails because of some sort
of lock between replication and reading the system tables?
2) Is replication getting stuck because of locks?
3) What can i do to get around this?
cheers,
Tim
The status event is the best way to monitor progress of your sync.
Merge replication does put schema and application locks on your tables,
including the sysmergerarticles table - this is probably what you are
seeing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mar72Vin" <mar72vin@.gmail.com> wrote in message
news:1173826362.218126.53350@.l75g2000hse.googlegro ups.com...
> Hi All,
> I have previously posted in the MSDN forums with no responses, so any
> hints on this would be greatly appreciated.
> I am replicating an SQL2005 express machine to SQL2005 standard
> edition server using merge replication.
> I have a simple VB application using ADO polling msMerge_history at
> the subscriber every second so that i can show the end user the
> progress of the replication.
> When the subscription first subscribes and after the initial snapshot
> is applied replication downloads all changes from the server that have
> been changed since the snapshot was created.
> Towards the end of this download faze the VB polling application fails
> with "Cannot open database "DBName" requested by the login. The login
> failed."
> This connection fails 4 or 5 times and then normal polling resumes.
> The scary thing is that sometimes when the polling connection fails
> the merge replication does not complete and if i check
> msMerge_Sessions the "runstatus" is stuck at 3 (InProgress).
> 1) Is the reason the ADO polling connection fails because of some sort
> of lock between replication and reading the system tables?
> 2) Is replication getting stuck because of locks?
> 3) What can i do to get around this?
> cheers,
> Tim
>
|||Hi Hilary,
Thanks for the quick reply.
We are not using the replication component to start replication so we
can't use the "status event"
We run replmerg.exe independently so that replication can be started
via windows Task Scheduler. This way we do not need to have our
replication monitor open whilst replicating.
However when we do have our replication monitor open the replmerg.exe
disappears out of the taskmanager and leaves replication stuck at the
"in progress" status. This only happens after applying the initial
snapshot. (subsequent replications succeed)
The last message recorded to msMerge_History is usually "Web
Syncronization progress xx% Complete."
Why would the replmerge.exe just "give up" at this stage?
thanks for your time.
Cheers,
Tim
On Mar 14, 12:45 pm, "Hilary Cotter" <hilary.cot...@.gmail.com> wrote:[vbcol=seagreen]
> The status event is the best way to monitor progress of your sync.
> Merge replication does put schema and application locks on your tables,
> including the sysmergerarticles table - this is probably what you are
> seeing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTShttp://www.indexserverfaq.com
> "Mar72Vin" <mar72...@.gmail.com> wrote in message
> news:1173826362.218126.53350@.l75g2000hse.googlegro ups.com...
>
>
>
>
|||Looks like i have been barking up the wrong tree. The connections from
the ado application are not causing this error.
I ran replmerg.exe and captured the results (see below), It looks like
replication is trying to use the SYSTEM login at some point to access
the database and it does not have access.
The SQL2005Express instance is running under the system account, I
can't see why it should have troubles connecting to this database.
Any Ideas?
cheers,
Tim
2007-03-14 04:56:34.347 Connecting to Subscriber 'BARNEYXP\MDSZINC'
2007-03-14 04:56:34.347 Connecting to OLE DB Subscriber at datasource:
'BARNEYXP\MDSZINC', location: '', catalog: 'MDS200703146',
providerstring: '' using provider 'SQLNCLI'
2007-03-14 04:56:36.811 Percent Complete: 0
2007-03-14 04:56:36.811 Category:AGENT
Source: BARNEYXP\MDSZINC
Number: 20052
Message: The process could not access database 'MDS200703146' on
server 'BARNEYXP\MDSZINC'.
2007-03-14 04:56:36.811 Percent Complete: 0
2007-03-14 04:56:36.811 Category:SQLSERVER
Source: BARNEYXP\MDSZINC
Number: 4060
Message: Cannot open database "MDS200703146" requested by the login.
The login failed.
2007-03-14 04:56:36.811 Percent Complete: 0
2007-03-14 04:56:36.811 Category:SQLSERVER
Source: BARNEYXP\MDSZINC
Number: 18456
Message: Login failed for user 'NT AUTHORITY\SYSTEM'.
|||It sounds like one of the accounts you are trying to connect to the
publisher/distributor/or subscriber is not defined. You will need to use an
account which is in the pal on the publisher and in the sysadmin or dbo_role
on the subscriber. It will need rights to read, and list files and folders
on the snapshot share.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mar72Vin" <mar72vin@.gmail.com> wrote in message
news:1173852824.327599.170440@.n59g2000hsh.googlegr oups.com...
> Looks like i have been barking up the wrong tree. The connections from
> the ado application are not causing this error.
> I ran replmerg.exe and captured the results (see below), It looks like
> replication is trying to use the SYSTEM login at some point to access
> the database and it does not have access.
> The SQL2005Express instance is running under the system account, I
> can't see why it should have troubles connecting to this database.
> Any Ideas?
> cheers,
> Tim
>
> 2007-03-14 04:56:34.347 Connecting to Subscriber 'BARNEYXP\MDSZINC'
> 2007-03-14 04:56:34.347 Connecting to OLE DB Subscriber at datasource:
> 'BARNEYXP\MDSZINC', location: '', catalog: 'MDS200703146',
> providerstring: '' using provider 'SQLNCLI'
> 2007-03-14 04:56:36.811 Percent Complete: 0
> 2007-03-14 04:56:36.811 Category:AGENT
> Source: BARNEYXP\MDSZINC
> Number: 20052
> Message: The process could not access database 'MDS200703146' on
> server 'BARNEYXP\MDSZINC'.
> 2007-03-14 04:56:36.811 Percent Complete: 0
> 2007-03-14 04:56:36.811 Category:SQLSERVER
> Source: BARNEYXP\MDSZINC
> Number: 4060
> Message: Cannot open database "MDS200703146" requested by the login.
> The login failed.
> 2007-03-14 04:56:36.811 Percent Complete: 0
> 2007-03-14 04:56:36.811 Category:SQLSERVER
> Source: BARNEYXP\MDSZINC
> Number: 18456
> Message: Login failed for user 'NT AUTHORITY\SYSTEM'.
>
sql
Sunday, March 11, 2012
Cannot login to SQL2005 newsgroup
newsgroup rather than here, but I cannot login to the NNTP server using:
* Server: privatenews.microsoft.com
* Account name: privatenews\sql05
* Password: feedback
Does anyone know how to login? Does the newsgroup still exists?
Thanks!
Beto.These were only during beta. MS does not create new newsgroups for each vers
ion. So, just post here
(in appropriate group) and mention what version you are using..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005 news
group rather than here,
> but I cannot login to the NNTP server using:
> * Server: privatenews.microsoft.com
> * Account name: privatenews\sql05
> * Password: feedback
> Does anyone know how to login? Does the newsgroup still exists?
> Thanks!
> Beto.
>|||The beta newsgroups are closed now that SQL 2005 is released. Post
questions about the released version to the microsoft.public.sqlserver
groups. Since the public groups are for all SQL Server versions, be sure to
specify the SQL Server version you are using.
Hope this helps.
Dan Guzman
SQL Server MVP
"beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005
> newsgroup rather than here, but I cannot login to the NNTP server using:
> * Server: privatenews.microsoft.com
> * Account name: privatenews\sql05
> * Password: feedback
> Does anyone know how to login? Does the newsgroup still exists?
> Thanks!
> Beto.
>|||Thanks for your reply!
I hope tha someone could answer my previous post here then.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:e7oTrPQ8FHA.1000@.tk2msftngp13.phx.gbl...
> The beta newsgroups are closed now that SQL 2005 is released. Post
> questions about the released version to the microsoft.public.sqlserver
> groups. Since the public groups are for all SQL Server versions, be sure
> to specify the SQL Server version you are using.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
> news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
>
Cannot login to SQL2005 newsgroup
newsgroup rather than here, but I cannot login to the NNTP server using:
* Server: privatenews.microsoft.com
* Account name: privatenews\sql05
* Password: feedback
Does anyone know how to login? Does the newsgroup still exists?
Thanks!
Beto.
These were only during beta. MS does not create new newsgroups for each version. So, just post here
(in appropriate group) and mention what version you are using..
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005 newsgroup rather than here,
> but I cannot login to the NNTP server using:
> * Server: privatenews.microsoft.com
> * Account name: privatenews\sql05
> * Password: feedback
> Does anyone know how to login? Does the newsgroup still exists?
> Thanks!
> Beto.
>
|||The beta newsgroups are closed now that SQL 2005 is released. Post
questions about the released version to the microsoft.public.sqlserver
groups. Since the public groups are for all SQL Server versions, be sure to
specify the SQL Server version you are using.
Hope this helps.
Dan Guzman
SQL Server MVP
"beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005
> newsgroup rather than here, but I cannot login to the NNTP server using:
> * Server: privatenews.microsoft.com
> * Account name: privatenews\sql05
> * Password: feedback
> Does anyone know how to login? Does the newsgroup still exists?
> Thanks!
> Beto.
>
|||Thanks for your reply!
I hope tha someone could answer my previous post here then.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:e7oTrPQ8FHA.1000@.tk2msftngp13.phx.gbl...
> The beta newsgroups are closed now that SQL 2005 is released. Post
> questions about the released version to the microsoft.public.sqlserver
> groups. Since the public groups are for all SQL Server versions, be sure
> to specify the SQL Server version you are using.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
> news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
>
Cannot login to SQL2005 newsgroup
newsgroup rather than here, but I cannot login to the NNTP server using:
* Server: privatenews.microsoft.com
* Account name: privatenews\sql05
* Password: feedback
Does anyone know how to login? Does the newsgroup still exists?
Thanks!
Beto.These were only during beta. MS does not create new newsgroups for each version. So, just post here
(in appropriate group) and mention what version you are using..
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005 newsgroup rather than here,
> but I cannot login to the NNTP server using:
> * Server: privatenews.microsoft.com
> * Account name: privatenews\sql05
> * Password: feedback
> Does anyone know how to login? Does the newsgroup still exists?
> Thanks!
> Beto.
>|||The beta newsgroups are closed now that SQL 2005 is released. Post
questions about the released version to the microsoft.public.sqlserver
groups. Since the public groups are for all SQL Server versions, be sure to
specify the SQL Server version you are using.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005
> newsgroup rather than here, but I cannot login to the NNTP server using:
> * Server: privatenews.microsoft.com
> * Account name: privatenews\sql05
> * Password: feedback
> Does anyone know how to login? Does the newsgroup still exists?
> Thanks!
> Beto.
>|||Thanks for your reply!
I hope tha someone could answer my previous post here then.
"Dan Guzman" <guzmanda@.nospam-online.sbcglobal.net> wrote in message
news:e7oTrPQ8FHA.1000@.tk2msftngp13.phx.gbl...
> The beta newsgroups are closed now that SQL 2005 is released. Post
> questions about the released version to the microsoft.public.sqlserver
> groups. Since the public groups are for all SQL Server versions, be sure
> to specify the SQL Server version you are using.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "beto @. southworks" <beto@.NOSPAN.southworks.net> wrote in message
> news:OLGAUJQ8FHA.3660@.TK2MSFTNGP09.phx.gbl...
>> Hi! I'm trying to refeer my SQL2005 questions directly to the SQL2005
>> newsgroup rather than here, but I cannot login to the NNTP server using:
>> * Server: privatenews.microsoft.com
>> * Account name: privatenews\sql05
>> * Password: feedback
>> Does anyone know how to login? Does the newsgroup still exists?
>> Thanks!
>> Beto.
>
Wednesday, March 7, 2012
Cannot Install SQL2005 developer on Windows XP with Office 2007 pr
professional.
When I try and install SQL2005 developer get an error 1706: Setup cannot
find the required file c:/program files/Microsoft Office11/1033/setup.chm
Any assistance is appreciated.
GavinHi Gavin,
This is actually a known bug and Microsoft is aware of it. Until a fix
is released you need to workaround it by uninstalling Microsoft Office
2003 Web Components from the Add/Remove Software control panel and then
re-run the SQL Server setup.
Hope this helps!
Jonathan
gavin wrote:
> Have a new computer with Windows XP SP2 and all updates and Office 2007
> professional.
> When I try and install SQL2005 developer get an error 1706: Setup cannot
> find the required file c:/program files/Microsoft Office11/1033/setup.chm
> Any assistance is appreciated.
> Gavin|||On Aug 2, 10:17 am, Jonathan Psaila-Depasquale
<nos...@.nospamplease.com> wrote:
> Hi Gavin,
> This is actually a known bug and Microsoft is aware of it. Until a fix
> is released you need to workaround it by uninstalling Microsoft Office
> 2003 Web Components from the Add/Remove Software control panel and then
> re-run the SQL Server setup.
> Hope this helps!
> Jonathan
>
> gavin wrote:
> > Have a new computer with Windows XP SP2 and all updates and Office 2007
> > professional.
> > When I try and install SQL2005 developer get an error 1706: Setup cannot
> > find the required file c:/program files/Microsoft Office11/1033/setup.chm
> > Any assistance is appreciated.
> > Gavin- Hide quoted text -
> - Show quoted text -
Interesting. I was curious to what it was looking in the Office11
folder, as I believe Office 2007 falls withing the Office12 arena. I
have the same setup (no Office Web Components) and had no issues
installing the SQL 2005 developer edition.
Cannot Install SQL2005 developer on Windows XP with Office 2007 pr
professional.
When I try and install SQL2005 developer get an error 1706: Setup cannot
find the required file c:/program files/Microsoft Office11/1033/setup.chm
Any assistance is appreciated.
Gavin
On Aug 2, 10:17 am, Jonathan Psaila-Depasquale
<nos...@.nospamplease.com> wrote:
> Hi Gavin,
> This is actually a known bug and Microsoft is aware of it. Until a fix
> is released you need to workaround it by uninstalling Microsoft Office
> 2003 Web Components from the Add/Remove Software control panel and then
> re-run the SQL Server setup.
> Hope this helps!
> Jonathan
>
> gavin wrote:
>
> - Show quoted text -
Interesting. I was curious to what it was looking in the Office11
folder, as I believe Office 2007 falls withing the Office12 arena. I
have the same setup (no Office Web Components) and had no issues
installing the SQL 2005 developer edition.
Cannot Install SQL2005 developer on Windows XP with Office 2007 pr
professional.
When I try and install SQL2005 developer get an error 1706: Setup cannot
find the required file c:/program files/Microsoft Office11/1033/setup.chm
Any assistance is appreciated.
GavinOn Aug 2, 10:17 am, Jonathan Psaila-Depasquale
<nos...@.nospamplease.com> wrote:
> Hi Gavin,
> This is actually a known bug and Microsoft is aware of it. Until a fix
> is released you need to workaround it by uninstalling Microsoft Office
> 2003 Web Components from the Add/Remove Software control panel and then
> re-run the SQL Server setup.
> Hope this helps!
> Jonathan
>
> gavin wrote:
>
> - Show quoted text -
Interesting. I was curious to what it was looking in the Office11
folder, as I believe Office 2007 falls withing the Office12 arena. I
have the same setup (no Office Web Components) and had no issues
installing the SQL 2005 developer edition.
Sunday, February 12, 2012
Cannot generate SSPI context
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that
I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
AnatoliAll the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.
Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with m
y
network account from within an RDP session.
"Anatoli" wrote:
> Hi,
> Im having trouble connecting to the SQL2005 default instance installed on
> one of my sql servers within my domain. I have a second SQL2005 server tha
t I
> can connect to just fine. Both are in the same OU.
> This particular server, I can connect to AS2005, but not to SQL2005. I kee
p
> getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
> error. I've not changed anything in terms of settings on my PC, nor have a
ny
> settings been changed on the SQL server, though I was able to connect to
> SQL2005 for this server last week. Something obviously has changed, but I
> have no idea where to look. One of the other SysAdmins has no problems
> connecting to the database.
> I'm hoping this is just something simple to fix.
> regards,
> Anatoli|||Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus|||Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to othe
r
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
"MarkusB" wrote:
> Anatoli,
> check these links.
> http://support.microsoft.com/kb/811889/
> http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> Hope this helps
> Markus
>|||Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.
regards,
"Anatoli" wrote:
[vbcol=seagreen]
> Markus,
> Thanks for your reply. From what I can tell, this problem is specific to m
y
> domain account. That is that I can connect remotely to the SQL server usin
g
> the SA account, but I can't connect using my domain account. I tried using
> another PC from which one of other admins was able to easily connect to
> SQL2005. I don't use a roaming profile, and this was the first time I logg
ed
> onto that PC and still I got the same error. Again, when I logged in local
ly
> to the SQL server I didn't have any problems SSMS connecting.
> So from what I can tell, there aren't any setting issues on the SQL server
> side nor are there any issues from my PC side as I'm able to connect to ot
her
> instances of SQL 2005 with my domain account.
> Are there any settings associated with the login to cause such an error?
> "MarkusB" wrote:
>
Cannot generate SSPI context
Im having trouble connecting to the SQL2005 default instance installed on
one of my sql servers within my domain. I have a second SQL2005 server that I
can connect to just fine. Both are in the same OU.
This particular server, I can connect to AS2005, but not to SQL2005. I keep
getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
error. I've not changed anything in terms of settings on my PC, nor have any
settings been changed on the SQL server, though I was able to connect to
SQL2005 for this server last week. Something obviously has changed, but I
have no idea where to look. One of the other SysAdmins has no problems
connecting to the database.
I'm hoping this is just something simple to fix.
regards,
AnatoliAll the below is happening while I'm attempting to connect remotely from my
XP SP2 pc using SSMS.
Further to this, I've found that I can connect to the server in question
remotely using the SA account. I can also, connect to SQL2005 locally with my
network account from within an RDP session.
"Anatoli" wrote:
> Hi,
> Im having trouble connecting to the SQL2005 default instance installed on
> one of my sql servers within my domain. I have a second SQL2005 server that I
> can connect to just fine. Both are in the same OU.
> This particular server, I can connect to AS2005, but not to SQL2005. I keep
> getting the 'Cannot generate SSPI context. (.Net SqlClient Data Provider)'
> error. I've not changed anything in terms of settings on my PC, nor have any
> settings been changed on the SQL server, though I was able to connect to
> SQL2005 for this server last week. Something obviously has changed, but I
> have no idea where to look. One of the other SysAdmins has no problems
> connecting to the database.
> I'm hoping this is just something simple to fix.
> regards,
> Anatoli|||Anatoli,
check these links.
http://support.microsoft.com/kb/811889/
http://msdn2.microsoft.com/en-us/library/ms191153.aspx
http://msdn2.microsoft.com/en-us/library/ms189585.aspx
Hope this helps
Markus|||Markus,
Thanks for your reply. From what I can tell, this problem is specific to my
domain account. That is that I can connect remotely to the SQL server using
the SA account, but I can't connect using my domain account. I tried using
another PC from which one of other admins was able to easily connect to
SQL2005. I don't use a roaming profile, and this was the first time I logged
onto that PC and still I got the same error. Again, when I logged in locally
to the SQL server I didn't have any problems SSMS connecting.
So from what I can tell, there aren't any setting issues on the SQL server
side nor are there any issues from my PC side as I'm able to connect to other
instances of SQL 2005 with my domain account.
Are there any settings associated with the login to cause such an error?
"MarkusB" wrote:
> Anatoli,
> check these links.
> http://support.microsoft.com/kb/811889/
> http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> Hope this helps
> Markus
>|||Turned out to be how the system guys upgraded the server to W2K3, SQL and AS
2005. They blew away the old sql server and installed W2K3, SQL/AS 2005, but
never removed the computer object out of AD. Used the SETSPN.exe utility
determine that there was more than one SPN for that particular server.
regards,
"Anatoli" wrote:
> Markus,
> Thanks for your reply. From what I can tell, this problem is specific to my
> domain account. That is that I can connect remotely to the SQL server using
> the SA account, but I can't connect using my domain account. I tried using
> another PC from which one of other admins was able to easily connect to
> SQL2005. I don't use a roaming profile, and this was the first time I logged
> onto that PC and still I got the same error. Again, when I logged in locally
> to the SQL server I didn't have any problems SSMS connecting.
> So from what I can tell, there aren't any setting issues on the SQL server
> side nor are there any issues from my PC side as I'm able to connect to other
> instances of SQL 2005 with my domain account.
> Are there any settings associated with the login to cause such an error?
> "MarkusB" wrote:
> > Anatoli,
> >
> > check these links.
> > http://support.microsoft.com/kb/811889/
> >
> > http://msdn2.microsoft.com/en-us/library/ms191153.aspx
> > http://msdn2.microsoft.com/en-us/library/ms189585.aspx
> >
> > Hope this helps
> >
> > Markus
> >
> >