Sql Cannot connect: servers

Showing posts with label servers. Show all posts

Thursday, March 29, 2012

Cannot Export Data from SQL Server 2005

I have two servers running SQL Server 2005 64 bit with all the available
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttri
butes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChan
ged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
at
Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils
.GetLocaleID(ConnectionManager connectionManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.Loa
dState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set
_ConnectionManager(ConnectionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo info
,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Propert
ies()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!Hi Luis
"Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
>I have two servers running SQL Server 2005 64 bit with all the available
> patches, running on Windows 2003 64 bits fully patched.
> On both servers I get the same error everytime I use this sequence to
> export
> data:
> 1) Right click DB and choose Tasks/Export Data
> 2) I select the same server as the datasource
> 3) When choosing the destination, the moment I select "Flat File" or
> "Microsoft Excel" I get the same error:
> ===================================
> An error occurred which the SQL Server Integration Services Wizard was not
> prepared to handle. (SQL Server Import and Export Wizard)
> ===================================
> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> SignatureStruct& signature, IntPtr declaringType)
> at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> SignatureStruct signature, RuntimeTypeHandle declaringType)
> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAtt
ributes)
> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes)
> at
> Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexCh
anged(Object
> sender, EventArgs e)
> at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> at System.Windows.Forms.ComboBox.WndProc(Message& m)
> at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&
> m)
> at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
> ===================================
> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> at
> Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUti
ls.GetLocaleID(ConnectionManager
> connectionManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.L
oadState(ConnectionManager
> connManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.s
et_ConnectionManager(ConnectionManager
> value)
> at
> Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> info,
> Boolean bDest, WizardInputs inputs, WizardPage page)
> ===================================
> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at
> Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Prope
rties()
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> =================================
> So I cannot export data from these servers, I have tried everything and
> installed all of the components and started all services to no avail.
> I have even asked several Microsoft technicians and nobody seems to have a
> clue and it's exactly the same behavior in both servers.
> Please Help!
Have you tried to export data from a workstation?
Are you running SP2 or higher?
John|||Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:

> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>|||Hi Luis
"Luis Jahn" wrote:

> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studi
o
> from one server (acting as client) to the other server. Every time I get t
he
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 an
d
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much mon
ey
> to upgrade it's absurd you cannot even export a single excel worksheet fro
m
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was create
d
at the same time as yours http://tinyurl.com/24w8jh !
John

Cannot Export Data from SQL Server 2005

I have two servers running SQL Server 2005 64 bit with all the available
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
--
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
at
Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager connectionManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo info,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
--
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!Hi Luis
"Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
>I have two servers running SQL Server 2005 64 bit with all the available
> patches, running on Windows 2003 64 bits fully patched.
> On both servers I get the same error everytime I use this sequence to
> export
> data:
> 1) Right click DB and choose Tasks/Export Data
> 2) I select the same server as the datasource
> 3) When choosing the destination, the moment I select "Flat File" or
> "Microsoft Excel" I get the same error:
> ===================================> An error occurred which the SQL Server Integration Services Wizard was not
> prepared to handle. (SQL Server Import and Export Wizard)
> ===================================> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> SignatureStruct& signature, IntPtr declaringType)
> at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> SignatureStruct signature, RuntimeTypeHandle declaringType)
> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes)
> at
> Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object
> sender, EventArgs e)
> at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> at System.Windows.Forms.ComboBox.WndProc(Message& m)
> at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&
> m)
> at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
> ===================================> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> at
> Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager
> connectionManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager
> connManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager
> value)
> at
> Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> info,
> Boolean bDest, WizardInputs inputs, WizardPage page)
> ===================================> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at
> Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> =================================> So I cannot export data from these servers, I have tried everything and
> installed all of the components and started all services to no avail.
> I have even asked several Microsoft technicians and nobody seems to have a
> clue and it's exactly the same behavior in both servers.
> Please Help!
Have you tried to export data from a workstation?
Are you running SP2 or higher?
John|||Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:
> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> >I have two servers running SQL Server 2005 64 bit with all the available
> > patches, running on Windows 2003 64 bits fully patched.
> >
> > On both servers I get the same error everytime I use this sequence to
> > export
> > data:
> > 1) Right click DB and choose Tasks/Export Data
> > 2) I select the same server as the datasource
> > 3) When choosing the destination, the moment I select "Flat File" or
> > "Microsoft Excel" I get the same error:
> >
> > ===================================> >
> > An error occurred which the SQL Server Integration Services Wizard was not
> > prepared to handle. (SQL Server Import and Export Wizard)
> >
> > ===================================> >
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > --
> > Program Location:
> >
> > at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> > SignatureStruct& signature, IntPtr declaringType)
> > at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> > SignatureStruct signature, RuntimeTypeHandle declaringType)
> > at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> > invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> > at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> > Binder
> > binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> > at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> > Binder binder, Object[] args, CultureInfo culture, Object[]
> > activationAttributes)
> > at
> > Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object
> > sender, EventArgs e)
> > at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> > at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> > at System.Windows.Forms.ComboBox.WndProc(Message& m)
> > at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message&
> > m)
> > at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
> > at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> > IntPtr wparam, IntPtr lparam)
> >
> > ===================================> >
> > Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> >
> > --
> > Program Location:
> >
> > at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager
> > connectionManager)
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager
> > connManager)
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager
> > value)
> > at
> > Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> > info,
> > Boolean bDest, WizardInputs inputs, WizardPage page)
> >
> > ===================================> >
> > Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> >
> > --
> > Program Location:
> > at
> > Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
> > at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> > =================================> >
> > So I cannot export data from these servers, I have tried everything and
> > installed all of the components and started all services to no avail.
> >
> > I have even asked several Microsoft technicians and nobody seems to have a
> > clue and it's exactly the same behavior in both servers.
> >
> > Please Help!
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>|||Hi Luis
"Luis Jahn" wrote:
> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studio
> from one server (acting as client) to the other server. Every time I get the
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much money
> to upgrade it's absurd you cannot even export a single excel worksheet from
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was created
at the same time as yours http://tinyurl.com/24w8jh !
John

Tuesday, March 27, 2012

cannot drop transactional subscription

My publisher server crashed and will not be coming back. I have to turn one
of the subscribing servers into the new publisher, but it still thinks it's
subscriber to the publisher that crashed.
Documentation says you can only drop the subscriptions from the publisher?
Now what?
JD,
running sp_removedbreplication should remove any remaining references.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Why do you say the subscriber cum publisher still thinks it is the
subscriber? What is the error message you are getting?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"JD" <JD@.discussions.microsoft.com> wrote in message
news:66F31D84-0CEA-49C0-8A5D-970821275954@.microsoft.com...
> My publisher server crashed and will not be coming back. I have to turn
one
> of the subscribing servers into the new publisher, but it still thinks
it's
> subscriber to the publisher that crashed.
> Documentation says you can only drop the subscriptions from the
publisher?
> Now what?
sql

Thursday, March 22, 2012

Cannot delete users in SQL 2005?

Hi,

Running multiple SQL 2000 servers and on each can easily go under Enterprise Manager>>ServerXYZ>>Security>>Logins>>Delete and delete user regardless users DB membership etc...now installed SQL 2005 (MS SQL Server Management Studio) and trying to do the same (attached to server running SQL 2000) and I cannot do it. Each time I try it, I am getting:

TITLE: Microsoft SQL Server Management Studio

Drop failed for Login 'testdelete'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3033.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Drop+Login&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Login 'testdelete' is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login. (Microsoft SQL Server, Error: 15175)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=15175&LinkId=20476

BUTTONS:

OK

If I go and manually remove user from all databases and then try to delete it only then I can delete such user...this is not the solution for me as we have some servers where users can be associated up to different 300+ databases.

I would like to move from 2000 and start using 2005 tools exclusively and this is only reason I cannot.

Any fix, suggestion or solution is appreciated. Thanks.

I believe the error is by default as you can see that user is mapped/aliased to other databases, if you are using linked servers then thsi is expected. As a matter of access can you try revoking the permissions for that user and then drop it.|||

Thanks for your reply.

Yes I know what the message is meaning but what I do not understand is how I can just go to any user setup with access to multiple databases on same server (not linked) and select "Delete" using SQL 2000 Enterprise Manager and it drops it w/o any issues but when I go to the same server and user with same setup under SQL 2005 Server Managment Studio it tells me that user is associated to other databases and it cannot delete it w/o me first revoking all the access just then to drop it (that works)...this is lot more complex and requires extra steps?

|||

The issue is not so much that the login has mapped users, but that the mapped users own something in a database. In SQL Server 2005, we made security enhancements that require every object to be owned by some security principal. A user can no longer simply relinquish ownership. Instead, ownership must be positively taken by some other principal. Once all the users mapped to the login are no longer owners of anything, you should be able to drop the login without error.

This sounds like a pain point for you. If you could file a suggestion to make this easier at http://connect.microsoft.com/sqlserver, that would help. The development team gives additional weight to defect reports and feature requests submitted by customers when we are prioritizing future work.

Hope this helps,
Steve

Cannot delete users in SQL 2005?

Hi,

TITLE: Microsoft SQL Server Management Studio

Drop failed for Login 'testdelete'. (Microsoft.SqlServer.Smo)

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Login 'testdelete' is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login. (Microsoft SQL Server, Error: 15175)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.0760&EvtSrc=MSSQLServer&EvtID=15175&LinkId=20476

BUTTONS:

I would like to move from 2000 and start using 2005 tools exclusively and this is only reason I cannot.

Any fix, suggestion or solution is appreciated. Thanks.

Thanks for your reply.

|||

Hope this helps,
Steve

Cannot delete remote server

Trying to delete remote server 'DVA'

- When I go to delete the 'DVA' from the list of remote servers I get
- Error 15190: There are still remote logins for the server 'DVA'

I execute the following statement to list remote logins

- execute sp_helpRemoteLogin

the output returns

SERVER | LOCAL | REMOTE | OPTIONS
T1 | Distributor_admin | distributor_admin | trusted
T1 | Distributor_admin | sa | trusted

Fair enough I go to delete those remote logins using

- execute sp_dropremotelogin 'DVA' ,'distributor_admin', 'distributor_admin'
- execute sp_dropremotelogin 'DVA' ,'distributor_admin', 'sa'

but.. get the following error messages

There is no remote user 'Distributor_admin' and 'sa' mapped to the local user 'distributor_admin' from the remote server 'DVA'

Don't understand why it is not finding those logins and how to resolve?It almost sounds like a publication is still active on the server. Is that true.

Can you drop the publication(s) and then check to sede if the remote server is still listed?

Tuesday, March 20, 2012

cannot delete duplicated records

the servers i have is like that:
SERV-A is publisher,
SERV-B is subscribor to SERV-A
SERV-C is subscribor to SERV-B
I have sqlserver which the database on it is configured as publisher and
subscribor at the same time, I have duplicate record in a specific table on
that server only(SERV-B), when i tried to delete these records it give the
following message "cannot insert dublicate keyrow in object
msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement has
been terminated".
why this message appear and how i can delete these records?
thanks in advance.
Samir R. Ibrahim
run the merge agent on the publisher and subscriber/publisher. After it has
completed check the conflict viewer on both the publisher and
publisher/subscriber.
Hopefully the problem row will be in one of these tables and you can delete
it there.
"Samir R. Ibrahim" <samir.ibrahim@.wilcopm.com> wrote in message
news:OvWvIw3KEHA.556@.TK2MSFTNGP10.phx.gbl...
> the servers i have is like that:
> SERV-A is publisher,
> SERV-B is subscribor to SERV-A
> SERV-C is subscribor to SERV-B
> I have sqlserver which the database on it is configured as publisher and
> subscribor at the same time, I have duplicate record in a specific table
on
> that server only(SERV-B), when i tried to delete these records it give the
> following message "cannot insert dublicate keyrow in object
> msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement
has
> been terminated".
> why this message appear and how i can delete these records?
> thanks in advance.
> Samir R. Ibrahim
>
>

cannot delete dupliacted records.

the servers i have is like that:
SERV-A is publisher,
SERV-B is subscribor to SERV-A
SERV-C is subscribor to SERV-B
I have sqlserver which the database on it is configured as publisher and
subscribor at the same time, I have duplicate record in a specific table on
that server only(SERV-B), when i tried to delete these records it give the
following message "cannot insert dublicate keyrow in object
msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement has
been terminated".
why this message appear and how i can delete these records?
thanks in advance.
Samir R. Ibrahim
>
> the servers i have is like that:
> SERV-A is publisher,
> SERV-B is subscribor to SERV-A
> SERV-C is subscribor to SERV-B
> I have sqlserver which the database on it is configured as publisher and
> subscribor at the same time, I have duplicate record in a specific table
on
> that server only(SERV-B), when i tried to delete these records it give the
> following message "cannot insert dublicate keyrow in object
> msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement
has
> been terminated".
> why this message appear and how i can delete these records?
> thanks in advance.
> Samir R. Ibrahim
Hi Samir,
This information might help:
INF: Understanding Merge Replication Conflict Detection and Resolution
http://support.microsoft.com/?id=315514
Regards,
Eric Crdenas
SQL Server senior support professional

cannot delete dupliacted records.

the servers i have is like that:
SERV-A is publisher,
SERV-B is subscribor to SERV-A
SERV-C is subscribor to SERV-B
I have sqlserver which the database on it is configured as publisher and
subscribor at the same time, I have duplicate record in a specific table on
that server only(SERV-B), when i tried to delete these records it give the
following message "cannot insert dublicate keyrow in object
msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement has
been terminated".
why this message appear and how i can delete these records?
thanks in advance.
Samir R. Ibrahim>
> the servers i have is like that:
> SERV-A is publisher,
> SERV-B is subscribor to SERV-A
> SERV-C is subscribor to SERV-B
> I have sqlserver which the database on it is configured as publisher and
> subscribor at the same time, I have duplicate record in a specific table
on
> that server only(SERV-B), when i tried to delete these records it give the
> following message "cannot insert dublicate keyrow in object
> msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement
has
> been terminated".
> why this message appear and how i can delete these records?
> thanks in advance.
> Samir R. Ibrahim
--
Hi Samir,
This information might help:
INF: Understanding Merge Replication Conflict Detection and Resolution
http://support.microsoft.com/?id=315514
Regards,
Eric Crdenas
SQL Server senior support professional

cannot delete dupliacted records.

the servers i have is like that:
SERV-A is publisher,
SERV-B is subscribor to SERV-A
SERV-C is subscribor to SERV-B
I have sqlserver which the database on it is configured as publisher and
subscribor at the same time, I have duplicate record in a specific table on
that server only(SERV-B), when i tried to delete these records it give the
following message "cannot insert dublicate keyrow in object
msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement has
been terminated".
why this message appear and how i can delete these records?
thanks in advance.
Samir R. Ibrahim>
> the servers i have is like that:
> SERV-A is publisher,
> SERV-B is subscribor to SERV-A
> SERV-C is subscribor to SERV-B
> I have sqlserver which the database on it is configured as publisher and
> subscribor at the same time, I have duplicate record in a specific table
on
> that server only(SERV-B), when i tried to delete these records it give the
> following message "cannot insert dublicate keyrow in object
> msmerge-tombstone with unique index ucimsmerge_tombstone" "the statement
has
> been terminated".
> why this message appear and how i can delete these records?
> thanks in advance.
> Samir R. Ibrahim
--
Hi Samir,
This information might help:
INF: Understanding Merge Replication Conflict Detection and Resolution
http://support.microsoft.com/?id=315514
Regards,
--
Eric Cárdenas
SQL Server senior support professional

Saturday, February 25, 2012

Cannot connect via Linked Server

We have two servers, each with named instances of SQL Server 2000 SP3a installed. Server1\Instance1 has a linked server to Server2\Instance2. The linked server is using the SQLOLEODB provider. This linked server is setup with remote login and a correct
password. We get an error #17: SQL Server does not exist or access denied. We also get the same behaviour while trying an OPENROWSET query from the Server1\Instance1 Query Analyzer. All other SQL Server instances we have installed (on other machines)
can connect to Server2\Instance2 with a SQLOLEDB linked server, no problems.
As far as I can tell, this error is only happening when using the SQL Server. I can connect to the remote (Server2\Instance2) server using osql from Server1, and I can even connect to Server2\Instance2 by using a SQLOLEDB connection from a desktop app (f
or example, I can test the connection successfully in a UDL using SQLOLEDB to the remote server from Server1).
We are only using named pipes. I have verified that all client and all server network utilities are set exclusively to named pipes. This is true. I have also performed a network trace on the Server1 server. It does not even attempt to contact the Serv
er2 machine. I have also network traced a different SQL Server instance on another machine that can connect to Server2\Instance2 and it's network trace shows a very clear, immediate connection to the Server2.
What other steps can I take to troubleshoot this problem? I think that I have hit all the common trouble points in setting up a linked server.
Thanks,
Frank
Update: We noticed that there was an additional NIC card on the Server1 server that had an APIPA IP address. We have disabled this NIC and now the network trace is showing some communication between Server1 and Server2.
Basically, the trace shows Server1 attempts to connect using SMB to set the session up on Server2. Server2 responds with an NT error 22, STATUS_MORE_PROCESSING_REQUIRED, then a few frames later, it tries to open the IPC$ pipe on Server2. Server2 respond
s with an NT error 34, STATUS_ACCESS_DENIED. So why is SMB not allowing connections to the IPC$ pipe? I can log in to the Server1 machine under the same account as SQL Server is running as and issue a successful "net use \\Server2\IPC$" without a proble
m. The network trace requests from Server1 for the net use look similar to those generated by SQL Server linked server. Why does one get an access denied and the other does not?
Thanks,
Frank
|||Hi Frank,
I learned you are failed to create linked Server between Server1\Instance1
and Server2\Instance2. The error "SQL Server does not exist or access
denied." occurred.
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
2. Please check to see if UDP port 1434 is enabled.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Yuan, I have completed the following steps for troubleshooting from your post. My comments are indented below each of your suggestions:
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
I have checked the Server & Client network utilities: named pipes is default and the only protocol. That was stated in my original post.
2. Please check to see if UDP port 1434 is enabled.
Yes, port 1434 UDP is listening on the Server2 machine.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
Adding the linked server is not the problem. I can do it either through Enterprise Manager or the stored procedure. It is when I try to connect to the linked server (for example, when EM queries for table names from the linked server) that I get
Error #17 SQL Server does not exist or access denied, as stated in my original post.
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
I have been monitoring the event log (all application, security and system) for any errors on either system and there is nothing.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
I have tried to create an alias with the same results. No connectivity; access denied.
I have hit most of these normal troubleshooting steps. I don't usually jump to a network trace before trying things like this. The SMB network trace for opening the named pipe shows an access denied error from the Server2. What other issues might cause
this?
Thanks,
Frank
|||Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>X<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/default...b;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Yuan, we have tried creating a SQL Server without using the OLEDB provider and this failed in the same manner as the prior failures. Both the openquery and the four part fully qualified name queries failed with Error #17, SQL Server does not exist or acc
ess denied.
The MDAC is 2.7SP1 on Server1, 2.8 on Server2...
Any help at this point would be greatly appreciated...
Thanks,
Frank
-- "Yuan Shao" wrote: --
Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>?X<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/default...b;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Hi Frank,
Thanks for your feedback. After reviewing our discussion in detail, I
noticed you test the connection successfully in a UDL using SQLOLEDB to the
remote server (server2/instance2) from Server1. However, you still got the
error "SQL Server does not exist or access denied." using linked server
I would like you to check if this is a permission problem. Please try to
create a linked server with sa login and check to see if the same error
persists. I have attached a linkedserver.zip file with my notification to
help describe the configuration of linked server using sa login.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
|||Yuan, we have tried connecting to the linked server using the sa password and it still results in the original failure: Error 17, SQL Server does not exist or access denied. It seems like it is the named pipes connectivity shutting the door down rather t
han SQL Server, although I cannot verify this as neither SQL Server nor the operating system are logging this (despite having all failure logging turned on both the OS local security policy and in SQL Server). Any other ideas?
Thanks,
Frank
|||Have you tried a connection method other than named pipes. Try making TcpIP and secondary connection method and setting up an alias using IP.
Are both servers on the same segment?
Sometimes netbios names are not passed across segments.
Have you tried rebooting the server1 since disabling the NIC. Sometimes it needs to rebroadcast its existance on the NIC.
Thanks
Jeff
|||Hello Frank,
Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/default...=sz;en-us;top.
If this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*Subject Line
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Thanks for using MSDN Newsgroups.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
| Thread-Topic: Cannot connect via Linked Server
| thread-index: AcQh0Df+wj3plzMnQ3+eAqcmfTrgkg==
| X-WN-Post: microsoft.public.sqlserver.connect
| From: "=?Utf-8?B?RnJhbmsgSm9uZXM=?=" <frank@.bogusfiosincfake.com>
| References: <99E987D2-0636-4917-8627-8E1A87789198@.microsoft.com>
<4B4AE818-15A4-4C50-97DC-7370D8DC8D49@.microsoft.com>
<3tFzedKHEHA.612@.cpmsftngxa06.phx.gbl>
| Subject: RE: Cannot connect via Linked Server
| Date: Tue, 13 Apr 2004 20:26:04 -0700
| Lines: 4
| Message-ID: <50E78236-79B1-4D3F-9BFE-CB02692DB966@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:40978
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Yuan, we have tried connecting to the linked server using the sa password
and it still results in the original failure: Error 17, SQL Server does not
exist or access denied. It seems like it is the named pipes connectivity
shutting the door down rather than SQL Server, although I cannot verify
this as neither SQL Server nor the operating system are logging this
(despite having all failure logging turned on both the OS local security
policy and in SQL Server). Any other ideas?
Thanks,
Frank
|

Cannot connect via Linked Server

We have two servers, each with named instances of SQL Server 2000 SP3a insta
lled. Server1\Instance1 has a linked server to Server2\Instance2. The link
ed server is using the SQLOLEODB provider. This linked server is setup with
remote login and a correct
password. We get an error #17: SQL Server does not exist or access denied.
We also get the same behaviour while trying an OPENROWSET query from the Se
rver1\Instance1 Query Analyzer. All other SQL Server instances we have inst
alled (on other machines)
can connect to Server2\Instance2 with a SQLOLEDB linked server, no problems.
As far as I can tell, this error is only happening when using the SQL Server
. I can connect to the remote (Server2\Instance2) server using osql from Se
rver1, and I can even connect to Server2\Instance2 by using a SQLOLEDB conne
ction from a desktop app (f
or example, I can test the connection successfully in a UDL using SQLOLEDB t
o the remote server from Server1).
We are only using named pipes. I have verified that all client and all serv
er network utilities are set exclusively to named pipes. This is true. I h
ave also performed a network trace on the Server1 server. It does not even
attempt to contact the Serv
er2 machine. I have also network traced a different SQL Server instance on
another machine that can connect to Server2\Instance2 and it's network trace
shows a very clear, immediate connection to the Server2.
What other steps can I take to troubleshoot this problem? I think that I ha
ve hit all the common trouble points in setting up a linked server.
Thanks,
FrankUpdate: We noticed that there was an additional NIC card on the Server1 serv
er that had an APIPA IP address. We have disabled this NIC and now the netw
ork trace is showing some communication between Server1 and Server2.
Basically, the trace shows Server1 attempts to connect using SMB to set the
session up on Server2. Server2 responds with an NT error 22, STATUS_MORE_PR
OCESSING_REQUIRED, then a few frames later, it tries to open the IPC$ pipe o
n Server2. Server2 respond
s with an NT error 34, STATUS_ACCESS_DENIED. So why is SMB not allowing con
nections to the IPC$ pipe? I can log in to the Server1 machine under the sa
me account as SQL Server is running as and issue a successful "net use \\Ser
ver2\IPC$" without a proble
m. The network trace requests from Server1 for the net use look similar to
those generated by SQL Server linked server. Why does one get an access den
ied and the other does not?
Thanks,
Frank|||Hi Frank,
I learned you are failed to create linked Server between Server1\Instance1
and Server2\Instance2. The error "SQL Server does not exist or access
denied." occurred.
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
2. Please check to see if UDP port 1434 is enabled.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
Also, such issues tend to be complex and take up extensive research time.
I'd like to set your expectations that it may take a while for us to help
you narrow down the problem and we may eventually redirect you to PSS to
continue working with a dedicated Support Professional. If this is
critical, I'd recommend contacting PSS and opening a Support incident
troubleshoot this further. If you need any help in this regard, please let
me know.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Yuan, I have completed the following steps for troubleshooting from your
post. My comments are indented below each of your suggestions:
1. Please check the Server Network Utility for named pipes and make sure it
is the default value.
\\.\pipe\MSSQL$ Instance2\sql\query
I have checked the Server & Client network utilities: named pipes is default
and the only protocol. That was stated in my original post.
2. Please check to see if UDP port 1434 is enabled.
Yes, port 1434 UDP is listening on the Server2 machine.
3. Please try to add the linked Server using sp_addlinkedserver in QA
(Query Analyzer). What's the result? If there is any error occurring,
please provide the detailed error message.
For more information regarding sp_addlinkedserver, please refer to the
article on SQL Server Books Online.
Topic: "sp_addlinkedserver"
Adding the linked server is not the problem. I can do it either through Ent
erprise Manager or the stored procedure. It is when I try to connect to the
linked server (for example, when EM queries for table names from the linked
server) that I get
Error #17 SQL Server does not exist or access denied, as stated in my origin
al post.
4. Please check the application/system log on both Servers and see if there
is any error information when the "linked Server" error occurred.
I have been monitoring the event log (all application, security and system)
for any errors on either system and there is nothing.
5. Please try to create an alias for Server2\Instance2 and then create the
linked Server. Does the same problem still persist?
I have tried to create an alias with the same results. No connectivity; acc
ess denied.
I have hit most of these normal troubleshooting steps. I don't usually jump
to a network trace before trying things like this. The SMB network trace f
or opening the named pipe shows an access denied error from the Server2. Wh
at other issues might cause
this?
Thanks,
Frank|||Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>_<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/defaul...kb;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Yuan, we have tried creating a SQL Server without using the OLEDB provider a
nd this failed in the same manner as the prior failures. Both the openquery
and the four part fully qualified name queries failed with Error #17, SQL S
erver does not exist or acc
ess denied.
The MDAC is 2.7SP1 on Server1, 2.8 on Server2...
Any help at this point would be greatly appreciated...
Thanks,
Frank
-- "Yuan Shao" wrote: --
Hi Frank,
This issue is very strange. Please try the following steps to see if they
are helpful.
1. Try to create a new linked server using SQL Server directly but not OLE
DB provider for SQL Server. In the meantime, please specify a SQL account
in the general tab to connect to Server2\instance2 server. After creating
this linked server, please try to perform the following sql statements. It
is best to grant the admin permission of server2\instance2 to this test SQL
account.
Select * from OPENQUERY(<Linked Server Name>, 'SQL statements')
Select * from <Linked server Name>?_<Table Name>
Does the same error message "SQL Server does not exist or access denied"
still persist? Is there any other error message occurring? It is
appreciated you can provide the completely error message.
2. Please use MDAC checker on your Server1 and provide the result.
HOW TO: Check for MDAC Version
http://support.microsoft.com/defaul...kb;EN-US;301202
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Hi Frank,
Thanks for your feedback. After reviewing our discussion in detail, I
noticed you test the connection successfully in a UDL using SQLOLEDB to the
remote server (server2/instance2) from Server1. However, you still got the
error "SQL Server does not exist or access denied." using linked server
I would like you to check if this is a permission problem. Please try to
create a linked server with sa login and check to see if the same error
persists. I have attached a linkedserver.zip file with my notification to
help describe the configuration of linked server using sa login.
I am looking forward to hearing from you soon.
Regards,
Michael Shao
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.|||Yuan, we have tried connecting to the linked server using the sa password an
d it still results in the original failure: Error 17, SQL Server does not ex
ist or access denied. It seems like it is the named pipes connectivity shut
ting the door down rather t
han SQL Server, although I cannot verify this as neither SQL Server nor the
operating system are logging this (despite having all failure logging turned
on both the OS local security policy and in SQL Server). Any other ideas?
Thanks,
Frank|||Have you tried a connection method other than named pipes. Try making TcpIP
and secondary connection method and setting up an alias using IP.
Are both servers on the same segment?
Sometimes netbios names are not passed across segments.
Have you tried rebooting the server1 since disabling the NIC. Sometimes it
needs to rebroadcast its existance on the NIC.
Thanks
Jeff|||Hello Frank,
Looking at the nature of this issue, it would require intensive
troubleshooting which would be done quickly and effectively with direct
assistance from a Microsoft Support Professional through Microsoft Product
Support Services. You can contact Microsoft Product Support directly to
discuss additional support options you may have available, by contacting us
at 1-(800)936-5800 or by choosing one of the options listed at
http://support.microsoft.com/defaul...d=sz;en-us;top.
If this is not an urgent issue and your would like us to create an incident
for you and have Microsoft Customer Service Representative contact you
directly, please send email to (remove "online." from this no Spam email
address): mailto:dscommhf@.online.microsoft.com with the following
information,
*Include "Followup: <Tomcat IssueID>" in the email Subject.
*Location of the post
*Subject Line
*First Name, Last Name
*MSDN Subscriber ID
*Company name (if any)
*Phone number
*e-mail address
Thanks for using MSDN Newsgroups.
Vikrant Dalwale
Microsoft SQL Server Support Professional
This posting is provided "AS IS" with no warranties, and confers no rights.
Get secure !! For info, please visit http://www.microsoft.com/security.
Please reply to Newsgroups only.
| Thread-Topic: Cannot connect via Linked Server
| thread-index: AcQh0Df+wj3plzMnQ3+eAqcmfTrgkg==
| X-WN-Post: microsoft.public.sqlserver.connect
| From: "examnotes" <frank@.bogusfiosincfake.com>
| References: <99E987D2-0636-4917-8627-8E1A87789198@.microsoft.com>
<4B4AE818-15A4-4C50-97DC-7370D8DC8D49@.microsoft.com>
<3tFzedKHEHA.612@.cpmsftngxa06.phx.gbl>
| Subject: RE: Cannot connect via Linked Server
| Date: Tue, 13 Apr 2004 20:26:04 -0700
| Lines: 4
| Message-ID: <50E78236-79B1-4D3F-9BFE-CB02692DB966@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.connect
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.sqlserver.connect:40978
| NNTP-Posting-Host: tk2msftcmty1.phx.gbl 10.40.1.180
| X-Tomcat-NG: microsoft.public.sqlserver.connect
|
| Yuan, we have tried connecting to the linked server using the sa password
and it still results in the original failure: Error 17, SQL Server does not
exist or access denied. It seems like it is the named pipes connectivity
shutting the door down rather than SQL Server, although I cannot verify
this as neither SQL Server nor the operating system are logging this
(despite having all failure logging turned on both the OS local security
policy and in SQL Server). Any other ideas?
Thanks,
Frank
|

Cannot connect to subscriber

Setup:
- SQL2000 SP3 running on Windows2000 servers.
I have a merge replication running between three identical servers. Two of
the servers, the publisher and subscriber1, receive data from different
sources and are synced every day at 4am. Subscriber2 is a query server only
and is updated by the publisher at 5am.
Replication has been running flawlessly since we upgraded everything nearly
a year ago. This morning the merge agent for Subscriber1 failed with the
following error (XXXX is the server name):
"The process could not connect to Subscriber 'XXXX'.
(Source: XXXX (Agent); Error number: 20084)"
"Cannot generate SSPI context
(Source: XXXX (Data source); Error number: 11004)"
Subscriber2 succeeded. Nothing has changed on the servers, and the logon
credential are the same for each.
I'm at a loss here. Anyone have any idea what might be happening and how to
fix it?
Thanks,
John Steen
There are some patches which seem to be causing this problem. The first
thing I would do is try to connect to the problem machine using SQL
Authentication. This might indicate that someone has changed the server from
mixed authentication to windows. Then try Windows - do you get the SSPI
error there too?
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
"John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> Setup:
> - SQL2000 SP3 running on Windows2000 servers.
> I have a merge replication running between three identical servers. Two
of
> the servers, the publisher and subscriber1, receive data from different
> sources and are synced every day at 4am. Subscriber2 is a query server
only
> and is updated by the publisher at 5am.
> Replication has been running flawlessly since we upgraded everything
nearly
> a year ago. This morning the merge agent for Subscriber1 failed with the
> following error (XXXX is the server name):
> "The process could not connect to Subscriber 'XXXX'.
> (Source: XXXX (Agent); Error number: 20084)"
> "Cannot generate SSPI context
> (Source: XXXX (Data source); Error number: 11004)"
> Subscriber2 succeeded. Nothing has changed on the servers, and the logon
> credential are the same for each.
> I'm at a loss here. Anyone have any idea what might be happening and how
to
> fix it?
> Thanks,
> John Steen
>
|||Thanks for getting back to me so quickly, Hilary.
All three servers are using mixed authentication and identical credentials,
and there have been no patches or updates applied. I ran the merge agent for
Subscriber1 this morning manually and it succeeded. I did the same thing for
Subscriber2 but it failed. A second attempt succeeded. So it doesn't seem
to be an authentication issue.
We have a BU Exec SQL agent that does a differential backup at the same time
the merge agents run, so I'm going to to change the time that the agents run
to see if there's a conflict of some sort. If not, then I'll push it off to
our telecom people.
Thanks,
John
John Steen
remove (nospam) from e-mail address to send me a message
"Hilary Cotter" wrote:

> There are some patches which seem to be causing this problem. The first
> thing I would do is try to connect to the problem machine using SQL
> Authentication. This might indicate that someone has changed the server from
> mixed authentication to windows. Then try Windows - do you get the SSPI
> error there too?
> --
> 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
> "John Steen" <moderndads(nospam)@.hotmail.com> wrote in message
> news:ABA30CE3-CA41-481E-9195-35482227D318@.microsoft.com...
> of
> only
> nearly
> to
>
>

Sunday, February 19, 2012

Cannot connect to SQL Server

I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
The two servers are indentical, but if the two clients can connect S1, they
cant' connect to S2 ""Access denied or SQL Server does not exist" (but S2
can connect S1).
- I have checked the Server Network Utility and ClientNetwork Utility : all
is correct
- I have tried with the firewall unactivated : no change...
- The version of SQL 2000 on the two servers are the same.
- The network is a wire LAN.
Can anyone tell me where else to look or what else to try?
Many thanks in advance
Henri (Paris)
So you can connect:
C1 -> S1
C2 -> S1
S2 -> S1
but cannot connect:
C1 -> S2
C2 -> S2
Some things to check:
Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
not started, or you have the name wrong because it's a named instance such
as S2\MSDN, or it is not accepting any connections on the protocol you are
using.
If you can connect from S2 to S2, then I would double-check the firewall. I
see that you said you tried turning off the firewall, but the Windows
firewall that is turned on in SP2 causes most of these problems.
What protocol are you using? If TCP/IP, try connecting using the TCP address
and port number, such as 120.24.118.17,1433. It's possible you have a
problem resolving the computer name. That would cause this error.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>
|||Is the Browser service running on S2?
Did you see the whitepaper on my blog?
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>
|||Is the SQL Browser service running on S2?
Did you read
http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html ?
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:7F6297AB-2D3D-41FF-932D-A0971C0188F4@.microsoft.com...
> So you can connect:
> C1 -> S1
> C2 -> S1
> S2 -> S1
> but cannot connect:
> C1 -> S2
> C2 -> S2
> Some things to check:
> Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
> not started, or you have the name wrong because it's a named instance such
> as S2\MSDN, or it is not accepting any connections on the protocol you are
> using.
> If you can connect from S2 to S2, then I would double-check the firewall.
> I see that you said you tried turning off the firewall, but the Windows
> firewall that is turned on in SP2 causes most of these problems.
> What protocol are you using? If TCP/IP, try connecting using the TCP
> address and port number, such as 120.24.118.17,1433. It's possible you
> have a problem resolving the computer name. That would cause this error.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Henri" <foucauld@.wanadoo.fr> wrote in message
> news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>

Cannot connect to SQL Server

I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
The two servers are indentical, but if the two clients can connect S1, they
cant' connect to S2 ""Access denied or SQL Server does not exist" (but S2
can connect S1).
- I have checked the Server Network Utility and ClientNetwork Utility : all
is correct
- I have tried with the firewall unactivated : no change...
- The version of SQL 2000 on the two servers are the same.
- The network is a wire LAN.
Can anyone tell me where else to look or what else to try?
Many thanks in advance
Henri (Paris)So you can connect:
C1 -> S1
C2 -> S1
S2 -> S1
but cannot connect:
C1 -> S2
C2 -> S2
Some things to check:
Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
not started, or you have the name wrong because it's a named instance such
as S2\MSDN, or it is not accepting any connections on the protocol you are
using.
If you can connect from S2 to S2, then I would double-check the firewall. I
see that you said you tried turning off the firewall, but the Windows
firewall that is turned on in SP2 causes most of these problems.
What protocol are you using? If TCP/IP, try connecting using the TCP address
and port number, such as 120.24.118.17,1433. It's possible you have a
problem resolving the computer name. That would cause this error.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>|||Is the Browser service running on S2?
Did you see the whitepaper on my blog?
http://betav.com/blog/billva/2006/0..._connected.html
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Henri" <foucauld@.wanadoo.fr> wrote in message
news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>I have almost the same problem than Clive (cf 18/07). I have 2 servers S1,
>S2 (windows XP Pro, SP2), and 2 clients C1 and C2 (Windows XP Pro, SP2).
> The two servers are indentical, but if the two clients can connect S1,
> they cant' connect to S2 ""Access denied or SQL Server does not exist"
> (but S2 can connect S1).
> - I have checked the Server Network Utility and ClientNetwork Utility :
> all is correct
> - I have tried with the firewall unactivated : no change...
> - The version of SQL 2000 on the two servers are the same.
> - The network is a wire LAN.
> Can anyone tell me where else to look or what else to try?
> Many thanks in advance
> Henri (Paris)
>|||Is the SQL Browser service running on S2?
Did you read
http://betav.com/blog/billva/2006/0..._connected.html ?
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
www.hitchhikerguides.net
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:7F6297AB-2D3D-41FF-932D-A0971C0188F4@.microsoft.com...
> So you can connect:
> C1 -> S1
> C2 -> S1
> S2 -> S1
> but cannot connect:
> C1 -> S2
> C2 -> S2
> Some things to check:
> Can you connect from S2 to S2? If this fails, I suspect the SQL Server is
> not started, or you have the name wrong because it's a named instance such
> as S2\MSDN, or it is not accepting any connections on the protocol you are
> using.
> If you can connect from S2 to S2, then I would double-check the firewall.
> I see that you said you tried turning off the firewall, but the Windows
> firewall that is turned on in SP2 causes most of these problems.
> What protocol are you using? If TCP/IP, try connecting using the TCP
> address and port number, such as 120.24.118.17,1433. It's possible you
> have a problem resolving the computer name. That would cause this error.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Henri" <foucauld@.wanadoo.fr> wrote in message
> news:%23ZoxT3gyHHA.1188@.TK2MSFTNGP04.phx.gbl...
>

Thursday, February 16, 2012

cannot connect to server through ssms - cannot generate sspi context

Hi,

I have gone through so many kb articles to understanding the problem, but no luck as yet.

Here is the situation:

I have two dev servers : Server A and Server B. Both are set up in an identical fashion. Windows 2003 sp2, Sql Server 2005 sp1 Developer Edition, both are on the same domain, Both have all the three protocols enabled: Shared Memory, Tcpip, and Named Pipes in that order. I can ping both servers, and telnet using the default port. Both have only default instances. Both use the same domain user account for sql service. Both have the error in the log saying that spn could not be registered so authentication may fall back to NTLM.

Here is the issue: When I try to register Server A specifying tcp-ip connection, I am successful and I can see that the authentication is NTLM - is as expected. since the spn registration did not happen and since the sqlservice account is not a domain admin, the authentication used NTLM over tcp-ip. However, I try to register Server B specifying tcpip, I get a cannot generate sspi context error. Why did the authentication not fall back to NTLM as in Server A? From what I read in the KB articles, I asked our network admin to check up the spn, but he assures me that spn were never manually registered.

Can somebody throw more light on this issue?

Thanks

KRSE

http://blogs.msdn.com/sql_protocols/archive/2006/12/02/understanding-kerberos-and-ntlm-authentication-in-sql-server-connections.aspx

If you look at number 6 in the above team blog, it should shed some light on the problem.

Hope that helps.

John

P.S. If this addresses your problem, please mark your question as answered.

Tuesday, February 14, 2012

Cannot connect to remote distributor -- linked server error

I have 2 servers: #1 -- SQL 2005 SP1 publisher ; #2 -- SQL 2005 SP2 subscriber

originally I had #1 as pub and dist but dist but killing my CPU so I was in the process of moving the dist to #2... Got it all configured and when I tried to add #2 as a dist for #1 it fails when I get to the administrative password screen... It give me an error about how it cannot connect with the given password but under that is says linked server failed.

Since it mentioned linked server I tried to connect via the previous linked server to #2 and it failed... I cannot connect to #2 anymore from #1. I can login directly to #2 and I can use osql to connect to #2 but linked server does not work. I tried all drivers and many configurations...

Any ideas?

Some updates...

I can put the distributor locally on #1 and create both push and pull subscriptions to #2.

Sunday, February 12, 2012

Cannot connect to Local after change domain password

I have a Developer copy of Sql Server on my XP workstation, which I use to
access the Domain server's Sql Data and a local (name of my workstation) set
of practice data in a seperate sql server registration.
If I change my password on the domain, I can no longer connect to the local
server.
I'm running mixed mode on both with the sa login and a non-blank password.
I uninstalled my local copy of sql server, deleted the registry files I
could find, re-installed sql to a different drive partition, and then it
immediately showed the domain server registration but logon failure to the
local server registration.
I then changed my domain password back to what it used to be and everything
works fine. Problem is, my domain password is compromised and I need to
change it.
How do I clear all the real data about my install or get it to accept my new
authentication?
Bob Graham
My problem seems to have gone away after changing my network password back
to the same new one a second time.
As though it took several 'hits' to get sql to recognize the password
change.
Bob
"Bob Graham" <rvgtech@.pacbell.net> wrote in message
news:Io8ce.2370$zu.852@.newssvr13.news.prodigy.com. ..
> I have a Developer copy of Sql Server on my XP workstation, which I use
to
> access the Domain server's Sql Data and a local (name of my workstation)
set
> of practice data in a seperate sql server registration.
> If I change my password on the domain, I can no longer connect to the
local
> server.
> I'm running mixed mode on both with the sa login and a non-blank password.
> I uninstalled my local copy of sql server, deleted the registry files I
> could find, re-installed sql to a different drive partition, and then it
> immediately showed the domain server registration but logon failure to the
> local server registration.
> I then changed my domain password back to what it used to be and
everything
> works fine. Problem is, my domain password is compromised and I need to
> change it.
> How do I clear all the real data about my install or get it to accept my
new
> authentication?
> Bob Graham
>

Friday, February 10, 2012

Cannot connect to 2000 from 2005 via linked server

Interesting issue.. I think

I have 2 linked servers on my dev 2005 instance (sp1-win 2003). My 2005 instance shares the physical server with a 2000 instance. This linked server works fine. The second linked server is on a separate server running sql 2000 sp3. I cannot connect to this server at all. I can connect the other way -- from the 2000 to the 2005. I have tried all kinds of combinations of security and options but nothing works. The only resolutions I have found referenced installing Management Studio on the 2000 server or creating an ODBC connection from the 2005 instance. Any ideas?

Here is the error I get:

OLE DB provider "SQLNCLI" for linked server "ALLFLDB6" returned message "Login timeout expired".

OLE DB provider "SQLNCLI" for linked server "ALLFLDB6" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".

Msg 10061, Level 16, State 1, Line 0

TCP Provider: No connection could be made because the target machine actively refused it.

To make sure I understand, you got box A running Win2K3 SP1 that has a SQL2K5 instance (inst1) and a SQL2K instance (inst2). You've got another box B that has a SQLK2K5 instance (inst3). Inst1 has linked server entries for inst2 and inst3. Inst3 has linked server entries for inst1. The problem is that from inst1 connecting to inst3 isn't working.

What is the OS of box B? It sounds like you may have a firewall running on box B preventing connectivity. Also, is the TCP protocol enabled on inst3?

Here's a link to a bunch of connectivity troubleshooting tips:
http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx

Hope this helps,
Vaughn

|||

Close.... but not right...

Box 1 -- Windows 2003 SP1, SQL 2005 SP1 (inst2) and SQL 2000 SP3 (inst1)

Box 2 -- Windows 2003 SP1, SQL 2000 SP3 (inst3)

So inst2 has a linked server to inst1 and inst3. It can talk to inst1 with no problem but gets the error posted above when talking to inst3. Inst3 can talk to inst1 and inst2 with no issues. also inst1 can talk to inst3 with no issues. It does it every day so I know it has nothing to do with the physical servers (hopefully).

|||

I solved the issue.. at least on a temporary basis. I created an ODBC connection using the SQL 2000 driver. It is not that fast but I am only selecting from a table with only a couple hundred records...

If anything else comes up please let me know.

Thursday, March 29, 2012

Cannot Export Data from SQL Server 2005

Cannot Export Data from SQL Server 2005

Cannot Export Data from SQL Server 2005

Tuesday, March 27, 2012

cannot drop transactional subscription

Thursday, March 22, 2012

Cannot delete users in SQL 2005?

Cannot delete users in SQL 2005?

Cannot delete remote server

Tuesday, March 20, 2012

cannot delete duplicated records

cannot delete dupliacted records.

cannot delete dupliacted records.

cannot delete dupliacted records.

Saturday, February 25, 2012

Cannot connect via Linked Server

Cannot connect via Linked Server

Cannot connect to subscriber

Sunday, February 19, 2012

Cannot connect to SQL Server

Cannot connect to SQL Server

Thursday, February 16, 2012

cannot connect to server through ssms - cannot generate sspi context

Tuesday, February 14, 2012

Cannot connect to remote distributor -- linked server error

Sunday, February 12, 2012

Cannot connect to Local after change domain password

Friday, February 10, 2012

Cannot connect to 2000 from 2005 via linked server

Sql Cannot connect

Blog Archive

About Me