I have a problem getting connected to an instance of MSDE remotely. I can
register the instance in Enterprise Manager, and work with it locally on the
machine it is installed on but cannot get connected remotely. I get the
famous SQL Server does not exist or access is denied.
It is a named instance.
The security mode is set to SQL.
Network Protocols are enabled.
netstat tells me that it is listening on the correct port.
I'm logging in remotely as sa with the correct password.
Any help here would be appreciated.
Also for some reason the name of the server doesn't show up in the list in
Enterprise manager on the remote machine when trying to register the server.
I typed in the name of the server, the sa login and password, but still the
same error. Server doesn't exist or access is denied.
"jdehne" wrote:
> I have a problem getting connected to an instance of MSDE remotely. I can
> register the instance in Enterprise Manager, and work with it locally on the
> machine it is installed on but cannot get connected remotely. I get the
> famous SQL Server does not exist or access is denied.
> It is a named instance.
> The security mode is set to SQL.
> Network Protocols are enabled.
> netstat tells me that it is listening on the correct port.
> I'm logging in remotely as sa with the correct password.
> Any help here would be appreciated.
|||I have also tried adding the alias with the same port as MSDE is configured.
"jdehne" wrote:
[vbcol=seagreen]
> Also for some reason the name of the server doesn't show up in the list in
> Enterprise manager on the remote machine when trying to register the server.
> I typed in the name of the server, the sa login and password, but still the
> same error. Server doesn't exist or access is denied.
> "jdehne" wrote:
|||i have also noticed that when running osql -L on the remote machine the MSDE
instance does not show up.
"jdehne" wrote:
[vbcol=seagreen]
> I have also tried adding the alias with the same port as MSDE is configured.
> "jdehne" wrote:
|||Am Mon, 17 Oct 2005 15:06:03 -0700 schrieb jdehne:
[vbcol=seagreen]
> i have also noticed that when running osql -L on the remote machine the MSDE
> instance does not show up.
> "jdehne" wrote:
I can only guess:
a) TCP is enabled on the server but not on the client
b) connect doesn't work with servername but with server-IP
c) MDAC's are different versions
bye,
Helmut
|||hi,
jdehne wrote:
> i have also noticed that when running osql -L on the remote machine
> the MSDE instance does not show up.
try having a look at http://support.microsoft.com/kb/841251/en-us ,
http://support.microsoft.com/kb/841249/en-us
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I managed to figure it out. SP2 Secruity center was blocking the port and I
had add the sqlserver.exe to the list of programs that can get through the
firewall.
"Andrea Montanari" wrote:
> hi,
> jdehne wrote:
> try having a look at http://support.microsoft.com/kb/841251/en-us ,
> http://support.microsoft.com/kb/841249/en-us
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Tuesday, March 27, 2012
Sunday, March 25, 2012
Cant find SMSS
After installing the evaluation edition of MSSQL Enterprise 2005 I can not find SSMS. I know I installed the client tools upon installation. It's not showing up on in the menu, where is the location for the executable file.
Is SSMS even distriubted with the evaluation edition?
If not, is it possible to download it from somwhere...
Did you get any warnings while setup cheked your computer configuration?
Did you specify client tools installation during setup?
P.S. This question suits http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=95&SiteID=1 forum better.
|||SSMS is part of the evaluation edition. To see a report of what's installed go to Add/Remove Programs, select the entry for "Microsoft SQL Server 2005", select "Change", then select "Report". Under "Common Components" you'll want to see something like this:
Workstation Components
[Version: 9.00.1399.06 Edition: Evaluation Edition Patch level: 9.00.1399.06 Language: English (United States)]
If you see this and still don't think you have SSMS installed, close the report. On the "Change" dialog you should see an entry for Workstation Components, select it and press "Next". This will launch the component in maintenance mode. Just follow the dialogs. When you get to the feature tree be sure to select Management Tools under the Client Components node.
SSMS is installed to %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlwb.exe
|||Thanks for your reply::I got the evauation to work when I downloaded the DVD image and burnt it to disk, and did a fresh install...
I'm now in the process of converting my MySQL talbles over to MSSQL... weeee fun... SSIS takes some of the headake away!|||Excellent!
Thursday, March 22, 2012
can't find Enterprise Manager and Query Analyzer after setup
I downloaded the trial version of sql server 2005. but after installation, I couldnt find the Enterprise Manager and Query Analyzer. Any idea about that? Thanks.
Hi zhishan,
I believe those services can be configured from control panel (turn windows features on or off). Check the boxes next to enterprise manager services and query analyzer, then ok, and windows wil configure and update for those services.
|||Thanks djartsinc - do you know where on the control panel has the function? I spent a long time trying to find, but couldn't...|||Which Edition of SQL Server 2005 do you download? If it is SQL Server 2005 Express, such tool is not included. Please try SQL Server 2005 Expree with Advanced Services, which includes tools. You can get it from the same download website as SQL Server 2005 Express.
Tuesday, March 20, 2012
Cant enable database for full-text searching
When trying to create a new full-text catalogue for a database through enterprise manager the following error is generated:
The Microsoft Search service cannot be administered under the present user account
When attempting to enable a database for full-text searching by running the stored procedure "sp_fulltext_database" the following error message is recieved:
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user account
The user account that the SQL service is running under has full administrative rights (including the privileges such as log on locally/as a batch/as a service etc - the SQL BUILTIN\Adminstrators login also exists) and the MSSQL and MS Search services have been stopped and started to ensure that the system account does have control of the MS Search service.
Although the text of the error message refers to user rights, line 46 of the stored procedure refers to the DBCC CALLFULLTEXT function and so it appears that the process is actually falling over when trying to drop catalogues.
The server was upgraded from SQL Server 6.5 to SQL Server 2000 and the Full-Text Search component was selected. However it was noticed that the folders Config, Projects and GatherLogs were not present under the following directory:
C:\Program files\Microsoft SQL Server\MSSQL\FTData\SQL Server\
(It was attempted to reinstall the Full-Text Search component from the SQL 2000 CD but as the component was already installed this wasnt possible)
The relevant config files, including the schema.txt, were then copied to the above location and it was ensured that the schema.txt file was the same in both the above location and the MSSQL\Binn folder (and on the SQL 2000 CD). But this has had no effect.
It has also been noticed that there is no registry key relating to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SQLFTSearch\Setup\Schema
However we have another server (which was a SQL 2000 install, as opposed to an upgrade) which also doesnt have this registry entry and that server isnt experiencing any problems with full-text search/indexing.
Can anyone suggest any other possible fixes before we resort to reinstalling SQL server?
Thanks,
ElaineHave you tried to run the stored procedure or sp_fulltext_database using query analyzer ?|||I'd be looking at the following closely ( assuming you may not have checked these out already ):
www.microsoft.com/technet
www.sqlmag.com
I'd be checking technet first as it sounds awfully like a upgrade "undocumented" type problem.
Apart from that, sounds like you have done everyting else right.
Try setting the SQL Server account to run under a domain account, but make sure you set the startup account to be the same in the Server Properties tab in EM as the account you use when you alter the startup account in Services. This is for the benefit of the Full Text service.
Post back if probs.
J.|||Thanks for your suggestions
...but we resorted to reinstalling SQL which has worked, so it appears that there might be problems with the full-text feature if you've upgraded to sql 2000 from 6.5 (as opposed to a straight 2000 install).
(we retained the databases by detaching them and copying the .mdf/.ldf files to another location. Then once the new install of SQL 2000 was complete we re-attached the databases - NB. the detach/attach method doesn't cover DTS packages. Also if specific users are created for a DB after reattaching you might need to delete them from the DB user section, then recreate them in the security logins section)
The Microsoft Search service cannot be administered under the present user account
When attempting to enable a database for full-text searching by running the stored procedure "sp_fulltext_database" the following error message is recieved:
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user account
The user account that the SQL service is running under has full administrative rights (including the privileges such as log on locally/as a batch/as a service etc - the SQL BUILTIN\Adminstrators login also exists) and the MSSQL and MS Search services have been stopped and started to ensure that the system account does have control of the MS Search service.
Although the text of the error message refers to user rights, line 46 of the stored procedure refers to the DBCC CALLFULLTEXT function and so it appears that the process is actually falling over when trying to drop catalogues.
The server was upgraded from SQL Server 6.5 to SQL Server 2000 and the Full-Text Search component was selected. However it was noticed that the folders Config, Projects and GatherLogs were not present under the following directory:
C:\Program files\Microsoft SQL Server\MSSQL\FTData\SQL Server\
(It was attempted to reinstall the Full-Text Search component from the SQL 2000 CD but as the component was already installed this wasnt possible)
The relevant config files, including the schema.txt, were then copied to the above location and it was ensured that the schema.txt file was the same in both the above location and the MSSQL\Binn folder (and on the SQL 2000 CD). But this has had no effect.
It has also been noticed that there is no registry key relating to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SQLFTSearch\Setup\Schema
However we have another server (which was a SQL 2000 install, as opposed to an upgrade) which also doesnt have this registry entry and that server isnt experiencing any problems with full-text search/indexing.
Can anyone suggest any other possible fixes before we resort to reinstalling SQL server?
Thanks,
ElaineHave you tried to run the stored procedure or sp_fulltext_database using query analyzer ?|||I'd be looking at the following closely ( assuming you may not have checked these out already ):
www.microsoft.com/technet
www.sqlmag.com
I'd be checking technet first as it sounds awfully like a upgrade "undocumented" type problem.
Apart from that, sounds like you have done everyting else right.
Try setting the SQL Server account to run under a domain account, but make sure you set the startup account to be the same in the Server Properties tab in EM as the account you use when you alter the startup account in Services. This is for the benefit of the Full Text service.
Post back if probs.
J.|||Thanks for your suggestions
...but we resorted to reinstalling SQL which has worked, so it appears that there might be problems with the full-text feature if you've upgraded to sql 2000 from 6.5 (as opposed to a straight 2000 install).
(we retained the databases by detaching them and copying the .mdf/.ldf files to another location. Then once the new install of SQL 2000 was complete we re-attached the databases - NB. the detach/attach method doesn't cover DTS packages. Also if specific users are created for a DB after reattaching you might need to delete them from the DB user section, then recreate them in the security logins section)
Monday, March 19, 2012
Can't disable publishing
SQL Server will not allow me to disable publishing; it just gets hung up and freezes. I have tried using the wizard in Enterprise Manager and I have also tried running sp_dropsubscription and sp_droppublication in Query Analyzer. I found Hilary's past p
ost on a similar problem that says to run the following code (below). What does this code do? I was wondering if it would help my problem. Or what if I just changed replInfo = 0? I just want to disable the publication. Thank you.
CREATE TABLE [MSdistributiondbs] (
[name] [sysname] NOT NULL ,
[min_distretention] [int] NOT NULL ,
[max_distretention] [int] NOT NULL ,
[history_retention] [int] NOT NULL
) ON [PRIMARY]
GO
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> CREATE TABLE [MSdistributiondbs] (
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
|||I stopped the Log Reader agent and tried to drop the publication again, and it worked. Thank you so much.
-- Hilary Cotter wrote: --
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
ost on a similar problem that says to run the following code (below). What does this code do? I was wondering if it would help my problem. Or what if I just changed replInfo = 0? I just want to disable the publication. Thank you.
CREATE TABLE [MSdistributiondbs] (
[name] [sysname] NOT NULL ,
[min_distretention] [int] NOT NULL ,
[max_distretention] [int] NOT NULL ,
[history_retention] [int] NOT NULL
) ON [PRIMARY]
GO
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> CREATE TABLE [MSdistributiondbs] (
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
|||I stopped the Log Reader agent and tried to drop the publication again, and it worked. Thank you so much.
-- Hilary Cotter wrote: --
this code was specific to someone who was disabling publishing on a database
which had been restored from another server where it was being published.
When you restore a published database from another server, some replication
objects are not restored and others are.
In this case this table was not restored and to disable publishing you need
to create it.
You are experienceing locking which indicates other factors at work. Try to
disable it again and wait till you get a response.
If you don't stop SQL Server agent and try again, or make sure all log
reader, distribution agents, and merge agents using this database are
stopped.
"Andrea Worley" <k_Rage@.hotmail.com> wrote in message
news:5180D4E7-0CE9-4B44-BE56-5CE5B82129A1@.microsoft.com...
> SQL Server will not allow me to disable publishing; it just gets hung up
and freezes. I have tried using the wizard in Enterprise Manager and I have
also tried running sp_dropsubscription and sp_droppublication in Query
Analyzer. I found Hilary's past post on a similar problem that says to run
the following code (below). What does this code do? I was wondering if it
would help my problem. Or what if I just changed replInfo = 0? I just want
to disable the publication. Thank you.
> [name] [sysname] NOT NULL ,
> [min_distretention] [int] NOT NULL ,
> [max_distretention] [int] NOT NULL ,
> [history_retention] [int] NOT NULL
> ) ON [PRIMARY]
> GO
>
Sunday, March 11, 2012
Cant delete user table
I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
The type and xtype in sysobjects are both U. They show up in object browser
under user tables. When I try to delete them I get the following message:
You tried to delete one or more system objects. They were not deleted.
Anyone have any ideas as to what is going on here and how I can delete these?
Can you mention the name of these tables?
Thanks
GYK
"Lyle" wrote:
> I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> The type and xtype in sysobjects are both U. They show up in object browser
> under user tables. When I try to delete them I get the following message:
> You tried to delete one or more system objects. They were not deleted.
> Anyone have any ideas as to what is going on here and how I can delete these?
|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detai l
conflict_pubInvHist_Head_Det_Invoice_History_Heade r
conflict_PubInvoice_Head_Det_Invoice_History_Detai l
conflict_PubInvoice_Head_Det_Invoice_History_Heade r
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detai l
conflict_pubInvHist_Head_Det_Invoice_History_Heade r
conflict_PubInvoice_Head_Det_Invoice_History_Detai l
conflict_PubInvoice_Head_Det_Invoice_History_Heade r
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detai l
conflict_pubInvHist_Head_Det_Invoice_History_Heade r
conflict_PubInvoice_Head_Det_Invoice_History_Detai l
conflict_PubInvoice_Head_Det_Invoice_History_Heade r
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
The type and xtype in sysobjects are both U. They show up in object browser
under user tables. When I try to delete them I get the following message:
You tried to delete one or more system objects. They were not deleted.
Anyone have any ideas as to what is going on here and how I can delete these?
Can you mention the name of these tables?
Thanks
GYK
"Lyle" wrote:
> I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> The type and xtype in sysobjects are both U. They show up in object browser
> under user tables. When I try to delete them I get the following message:
> You tried to delete one or more system objects. They were not deleted.
> Anyone have any ideas as to what is going on here and how I can delete these?
|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detai l
conflict_pubInvHist_Head_Det_Invoice_History_Heade r
conflict_PubInvoice_Head_Det_Invoice_History_Detai l
conflict_PubInvoice_Head_Det_Invoice_History_Heade r
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detai l
conflict_pubInvHist_Head_Det_Invoice_History_Heade r
conflict_PubInvoice_Head_Det_Invoice_History_Detai l
conflict_PubInvoice_Head_Det_Invoice_History_Heade r
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detai l
conflict_pubInvHist_Head_Det_Invoice_History_Heade r
conflict_PubInvoice_Head_Det_Invoice_History_Detai l
conflict_PubInvoice_Head_Det_Invoice_History_Heade r
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
Cant delete user table
I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
The type and xtype in sysobjects are both U. They show up in object browser
under user tables. When I try to delete them I get the following message:
You tried to delete one or more system objects. They were not deleted.
Anyone have any ideas as to what is going on here and how I can delete these?Can you mention the name of these tables?
Thanks
GYK
"Lyle" wrote:
> I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> The type and xtype in sysobjects are both U. They show up in object browser
> under user tables. When I try to delete them I get the following message:
> You tried to delete one or more system objects. They were not deleted.
> Anyone have any ideas as to what is going on here and how I can delete these?|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detail
conflict_pubInvHist_Head_Det_Invoice_History_Header
conflict_PubInvoice_Head_Det_Invoice_History_Detail
conflict_PubInvoice_Head_Det_Invoice_History_Header
Lyle
"GYK" wrote:
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
> > I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> > The type and xtype in sysobjects are both U. They show up in object browser
> > under user tables. When I try to delete them I get the following message:
> >
> > You tried to delete one or more system objects. They were not deleted.
> >
> > Anyone have any ideas as to what is going on here and how I can delete these?|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detail
conflict_pubInvHist_Head_Det_Invoice_History_Header
conflict_PubInvoice_Head_Det_Invoice_History_Detail
conflict_PubInvoice_Head_Det_Invoice_History_Header
Lyle
"GYK" wrote:
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
> > I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> > The type and xtype in sysobjects are both U. They show up in object browser
> > under user tables. When I try to delete them I get the following message:
> >
> > You tried to delete one or more system objects. They were not deleted.
> >
> > Anyone have any ideas as to what is going on here and how I can delete these?|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detail
conflict_pubInvHist_Head_Det_Invoice_History_Header
conflict_PubInvoice_Head_Det_Invoice_History_Detail
conflict_PubInvoice_Head_Det_Invoice_History_Header
Lyle
"GYK" wrote:
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
> > I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> > The type and xtype in sysobjects are both U. They show up in object browser
> > under user tables. When I try to delete them I get the following message:
> >
> > You tried to delete one or more system objects. They were not deleted.
> >
> > Anyone have any ideas as to what is going on here and how I can delete these?
The type and xtype in sysobjects are both U. They show up in object browser
under user tables. When I try to delete them I get the following message:
You tried to delete one or more system objects. They were not deleted.
Anyone have any ideas as to what is going on here and how I can delete these?Can you mention the name of these tables?
Thanks
GYK
"Lyle" wrote:
> I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> The type and xtype in sysobjects are both U. They show up in object browser
> under user tables. When I try to delete them I get the following message:
> You tried to delete one or more system objects. They were not deleted.
> Anyone have any ideas as to what is going on here and how I can delete these?|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detail
conflict_pubInvHist_Head_Det_Invoice_History_Header
conflict_PubInvoice_Head_Det_Invoice_History_Detail
conflict_PubInvoice_Head_Det_Invoice_History_Header
Lyle
"GYK" wrote:
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
> > I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> > The type and xtype in sysobjects are both U. They show up in object browser
> > under user tables. When I try to delete them I get the following message:
> >
> > You tried to delete one or more system objects. They were not deleted.
> >
> > Anyone have any ideas as to what is going on here and how I can delete these?|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detail
conflict_pubInvHist_Head_Det_Invoice_History_Header
conflict_PubInvoice_Head_Det_Invoice_History_Detail
conflict_PubInvoice_Head_Det_Invoice_History_Header
Lyle
"GYK" wrote:
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
> > I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> > The type and xtype in sysobjects are both U. They show up in object browser
> > under user tables. When I try to delete them I get the following message:
> >
> > You tried to delete one or more system objects. They were not deleted.
> >
> > Anyone have any ideas as to what is going on here and how I can delete these?|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_History_Detail
conflict_pubInvHist_Head_Det_Invoice_History_Header
conflict_PubInvoice_Head_Det_Invoice_History_Detail
conflict_PubInvoice_Head_Det_Invoice_History_Header
Lyle
"GYK" wrote:
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
> > I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> > The type and xtype in sysobjects are both U. They show up in object browser
> > under user tables. When I try to delete them I get the following message:
> >
> > You tried to delete one or more system objects. They were not deleted.
> >
> > Anyone have any ideas as to what is going on here and how I can delete these?
Cant delete user table
I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
The type and xtype in sysobjects are both U. They show up in object browser
under user tables. When I try to delete them I get the following message:
You tried to delete one or more system objects. They were not deleted.
Anyone have any ideas as to what is going on here and how I can delete these
?Can you mention the name of these tables?
Thanks
GYK
"Lyle" wrote:
[vbcol=seagreen]
> I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> The type and xtype in sysobjects are both U. They show up in object brows
er
> under user tables. When I try to delete them I get the following message:
> You tried to delete one or more system objects. They were not deleted.
> Anyone have any ideas as to what is going on here and how I can delete these?[/vbc
ol]|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_His
tory_Detail
conflict_pubInvHist_Head_Det_Invoice_His
tory_Header
conflict_PubInvoice_Head_Det_Invoice_His
tory_Detail
conflict_PubInvoice_Head_Det_Invoice_His
tory_Header
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
>|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_His
tory_Detail
conflict_pubInvHist_Head_Det_Invoice_His
tory_Header
conflict_PubInvoice_Head_Det_Invoice_His
tory_Detail
conflict_PubInvoice_Head_Det_Invoice_His
tory_Header
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
>|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_His
tory_Detail
conflict_pubInvHist_Head_Det_Invoice_His
tory_Header
conflict_PubInvoice_Head_Det_Invoice_His
tory_Detail
conflict_PubInvoice_Head_Det_Invoice_His
tory_Header
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
>
The type and xtype in sysobjects are both U. They show up in object browser
under user tables. When I try to delete them I get the following message:
You tried to delete one or more system objects. They were not deleted.
Anyone have any ideas as to what is going on here and how I can delete these
?Can you mention the name of these tables?
Thanks
GYK
"Lyle" wrote:
[vbcol=seagreen]
> I have 4 user tables that show up in Enterprise Manager as SYSTEM tables.
> The type and xtype in sysobjects are both U. They show up in object brows
er
> under user tables. When I try to delete them I get the following message:
> You tried to delete one or more system objects. They were not deleted.
> Anyone have any ideas as to what is going on here and how I can delete these?[/vbc
ol]|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_His
tory_Detail
conflict_pubInvHist_Head_Det_Invoice_His
tory_Header
conflict_PubInvoice_Head_Det_Invoice_His
tory_Detail
conflict_PubInvoice_Head_Det_Invoice_His
tory_Header
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
>|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_His
tory_Detail
conflict_pubInvHist_Head_Det_Invoice_His
tory_Header
conflict_PubInvoice_Head_Det_Invoice_His
tory_Detail
conflict_PubInvoice_Head_Det_Invoice_His
tory_Header
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
>|||Yes, the table names are:
conflict_pubInvHist_Head_Det_Invoice_His
tory_Detail
conflict_pubInvHist_Head_Det_Invoice_His
tory_Header
conflict_PubInvoice_Head_Det_Invoice_His
tory_Detail
conflict_PubInvoice_Head_Det_Invoice_His
tory_Header
Lyle
"GYK" wrote:
[vbcol=seagreen]
> Can you mention the name of these tables?
> Thanks
> GYK
> "Lyle" wrote:
>
Saturday, February 25, 2012
Can't create a secondary index on a bit column
I am trying to create a secondary index on mult. columns
and one of them is a bit (I know you should not but that
is what they want). Using Enterprise Manager this does not
work, I get the following error:
Primary key or index cannot be created on column '<0s>'
because its data type is 'bit'.
If I use Query Analyzer it works fine.
My question is: Is this a bug in Enterprise Manager that
it does not let me or a bug in Query Analyzer that it does
let me?
Thanks.Don't know where is wrong. But you can check with QA's execution plan if
you have adequate data set -- use a situation that the new index is suitable
and run a query to see whether ther index is used. Or you can also sysindex
and sysindexkeys to look at.
Quentin
"Amy" <anonymous@.discussions.microsoft.com> wrote in message
news:030c01c3daf1$218abda0$a601280a@.phx.gbl...
There are some (using your word 'bugs') with EM
It does work with QA so be happy.
Note: You are right that it's a bad idea to have index on 'bit' column.
"Amy" <anonymous@.discussions.microsoft.com> wrote in message
news:030c01c3daf1$218abda0$a601280a@.phx.gbl...
and one of them is a bit (I know you should not but that
is what they want). Using Enterprise Manager this does not
work, I get the following error:
Primary key or index cannot be created on column '<0s>'
because its data type is 'bit'.
If I use Query Analyzer it works fine.
My question is: Is this a bug in Enterprise Manager that
it does not let me or a bug in Query Analyzer that it does
let me?
Thanks.Don't know where is wrong. But you can check with QA's execution plan if
you have adequate data set -- use a situation that the new index is suitable
and run a query to see whether ther index is used. Or you can also sysindex
and sysindexkeys to look at.
Quentin
"Amy" <anonymous@.discussions.microsoft.com> wrote in message
news:030c01c3daf1$218abda0$a601280a@.phx.gbl...
quote:|||Amy
> I am trying to create a secondary index on mult. columns
> and one of them is a bit (I know you should not but that
> is what they want). Using Enterprise Manager this does not
> work, I get the following error:
> Primary key or index cannot be created on column '<0s>'
> because its data type is 'bit'.
> If I use Query Analyzer it works fine.
> My question is: Is this a bug in Enterprise Manager that
> it does not let me or a bug in Query Analyzer that it does
> let me?
> Thanks.
There are some (using your word 'bugs') with EM
It does work with QA so be happy.
Note: You are right that it's a bad idea to have index on 'bit' column.
"Amy" <anonymous@.discussions.microsoft.com> wrote in message
news:030c01c3daf1$218abda0$a601280a@.phx.gbl...
quote:
> I am trying to create a secondary index on mult. columns
> and one of them is a bit (I know you should not but that
> is what they want). Using Enterprise Manager this does not
> work, I get the following error:
> Primary key or index cannot be created on column '<0s>'
> because its data type is 'bit'.
> If I use Query Analyzer it works fine.
> My question is: Is this a bug in Enterprise Manager that
> it does not let me or a bug in Query Analyzer that it does
> let me?
> Thanks.
Friday, February 24, 2012
Can't connect via Enterprise Manager
Hi All,
We have a MSDE on a W2K server installed. It is running fine and the
application can access it without a problem. We have another server on that
same subnet that has an SQL 2000 server installed. When trying to connect to
the MSDE via the Enterprise Manager, only the local SQL shows up and we
cannot connect to the MSDE instance.
When we go to the ODBC on the MSDE box we see both SQL - the local and the
remote one. On the ODBC on the other server we only see the local one.
Does anybody have an idea what is going on?
Thanks,
Claus
Hi Claus,
Most likely network protocols not enabled. Run svrnetcn.exe and check which
protocols (eg tcp) are enabled. By default, none are.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:%234wb4E1oEHA.4044@.TK2MSFTNGP10.phx.gbl...
> Hi All,
> We have a MSDE on a W2K server installed. It is running fine and the
> application can access it without a problem. We have another server on
that
> same subnet that has an SQL 2000 server installed. When trying to connect
to
> the MSDE via the Enterprise Manager, only the local SQL shows up and we
> cannot connect to the MSDE instance.
> When we go to the ODBC on the MSDE box we see both SQL - the local and the
> remote one. On the ODBC on the other server we only see the local one.
> Does anybody have an idea what is going on?
> Thanks,
> Claus
>
|||Hi Greg,
Thanks for the answer. I double checked and both protocols (tcp and named
pipe) are enabled.
Claus
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:%23LcQb96oEHA.1160@.tk2msftngp13.phx.gbl...
> Hi Claus,
> Most likely network protocols not enabled. Run svrnetcn.exe and check
which[vbcol=seagreen]
> protocols (eg tcp) are enabled. By default, none are.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:%234wb4E1oEHA.4044@.TK2MSFTNGP10.phx.gbl...
> that
connect[vbcol=seagreen]
> to
the
>
|||Claus,
Have you checked the firewall settings on the second server? If it has
the TCP port used by MSDE blocked you won't be able to connect.
Ron Allen
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:%23WJfzS9oEHA.3460@.tk2msftngp13.phx.gbl...
> Hi Greg,
> Thanks for the answer. I double checked and both protocols (tcp and named
> pipe) are enabled.
> Claus
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:%23LcQb96oEHA.1160@.tk2msftngp13.phx.gbl...
> which
> connect
> the
>
|||Hi Claus,
I might need more inputs to trouble shoot this issue. Before this, you
could try Re- registering the MSDE Server in your Enterprise Manager.
Please use the Register SQL Server Wizard. For the sake of Clarity, I am
outling the steps here.
In the Enterprise Manager, If the MSDE Server is already
Registered, then Select Server, Right Click on the Server and Select Delete
SQL Server Registration.
1. In the Enterprise Manager, Start Register SQL Server Wizard. (Right
Click on SQL Server Group, Select New SQL Server Registration)
2. In the 'Select a SQL Server' page (second page), In the 'Available
Servers' Text box enter the Computer Name on which the MSDE is installed.
(Hope it is a default instance. If it is a Named Instance then enter
Instance Name also eg: Default Instance on Computer Named Test - TEST,
Named Instance 'Test1' on TEST - TEST\Test1 ). Then click 'ADD' button.
Click Next.
3. In the Next Page Select Authentication Mode.
4. In the Next Page Click Next
5. In the Last Page Select Finish.
After few minutes, You would see a screen which should say
'Server Registration completed' Status 'Registered Successfully'.
If this goes through, You would be able to see the MSDE in your Enterprise
manager. In case it fails, Please mail me the exact Error Message that you
would see in the Status column. We would try and troubleshoot it further.
Thanks,
Soma Sekhara Reddy
|||There is no firewall on that server and I'm in the same subnet trying to
connect.
"Ron Allen" <rallen@._nospam_src-us.com> wrote in message
news:eXZzmPJpEHA.1644@.tk2msftngp13.phx.gbl...
> Claus,
> Have you checked the firewall settings on the second server? If it
has[vbcol=seagreen]
> the TCP port used by MSDE blocked you won't be able to connect.
> Ron Allen
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:%23WJfzS9oEHA.3460@.tk2msftngp13.phx.gbl...
named[vbcol=seagreen]
on[vbcol=seagreen]
we[vbcol=seagreen]
and[vbcol=seagreen]
one.
>
|||Thanks for your answer. This is what I have tried several times. The answer
I get back is "SQL server not running or access denied". I'm trying to
connect with SQL authentication (sa and password). I'm sure about the sa and
password because I use it in the local ODBC connection and the test works
fine.
I know I'm missing something really obvious - just can't put my finger on
it.
Claus
"Soma Sekhara Reddy" <somsredd@.microsoft.com> wrote in message
news:nyon0IQpEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi Claus,
> I might need more inputs to trouble shoot this issue. Before this, you
> could try Re- registering the MSDE Server in your Enterprise Manager.
> Please use the Register SQL Server Wizard. For the sake of Clarity, I am
> outling the steps here.
> In the Enterprise Manager, If the MSDE Server is already
> Registered, then Select Server, Right Click on the Server and Select
Delete
> SQL Server Registration.
> 1. In the Enterprise Manager, Start Register SQL Server Wizard. (Right
> Click on SQL Server Group, Select New SQL Server Registration)
> 2. In the 'Select a SQL Server' page (second page), In the 'Available
> Servers' Text box enter the Computer Name on which the MSDE is installed.
> (Hope it is a default instance. If it is a Named Instance then enter
> Instance Name also eg: Default Instance on Computer Named Test - TEST,
> Named Instance 'Test1' on TEST - TEST\Test1 ). Then click 'ADD' button.
> Click Next.
> 3. In the Next Page Select Authentication Mode.
> 4. In the Next Page Click Next
> 5. In the Last Page Select Finish.
> After few minutes, You would see a screen which should
say
> 'Server Registration completed' Status 'Registered Successfully'.
> If this goes through, You would be able to see the MSDE in your Enterprise
> manager. In case it fails, Please mail me the exact Error Message that
you
> would see in the Status column. We would try and troubleshoot it further.
> Thanks,
> Soma Sekhara Reddy
>
|||Hi Claus,
Please use the 'ODBCPING' command line utility to check the connectivity.
The syntax is
odbcping -Sservername -Uusername -Ppassword
This tool is loaded with SQL Server client utilities and would be available
on your system. Please do not leave any space betweeb -S and servername,
-S is caps (case sensitive).
Thanks,
Soma Sekhara Reddy
We have a MSDE on a W2K server installed. It is running fine and the
application can access it without a problem. We have another server on that
same subnet that has an SQL 2000 server installed. When trying to connect to
the MSDE via the Enterprise Manager, only the local SQL shows up and we
cannot connect to the MSDE instance.
When we go to the ODBC on the MSDE box we see both SQL - the local and the
remote one. On the ODBC on the other server we only see the local one.
Does anybody have an idea what is going on?
Thanks,
Claus
Hi Claus,
Most likely network protocols not enabled. Run svrnetcn.exe and check which
protocols (eg tcp) are enabled. By default, none are.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:%234wb4E1oEHA.4044@.TK2MSFTNGP10.phx.gbl...
> Hi All,
> We have a MSDE on a W2K server installed. It is running fine and the
> application can access it without a problem. We have another server on
that
> same subnet that has an SQL 2000 server installed. When trying to connect
to
> the MSDE via the Enterprise Manager, only the local SQL shows up and we
> cannot connect to the MSDE instance.
> When we go to the ODBC on the MSDE box we see both SQL - the local and the
> remote one. On the ODBC on the other server we only see the local one.
> Does anybody have an idea what is going on?
> Thanks,
> Claus
>
|||Hi Greg,
Thanks for the answer. I double checked and both protocols (tcp and named
pipe) are enabled.
Claus
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:%23LcQb96oEHA.1160@.tk2msftngp13.phx.gbl...
> Hi Claus,
> Most likely network protocols not enabled. Run svrnetcn.exe and check
which[vbcol=seagreen]
> protocols (eg tcp) are enabled. By default, none are.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:%234wb4E1oEHA.4044@.TK2MSFTNGP10.phx.gbl...
> that
connect[vbcol=seagreen]
> to
the
>
|||Claus,
Have you checked the firewall settings on the second server? If it has
the TCP port used by MSDE blocked you won't be able to connect.
Ron Allen
"cjobes" <cjobes@.nova-tech.org> wrote in message
news:%23WJfzS9oEHA.3460@.tk2msftngp13.phx.gbl...
> Hi Greg,
> Thanks for the answer. I double checked and both protocols (tcp and named
> pipe) are enabled.
> Claus
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:%23LcQb96oEHA.1160@.tk2msftngp13.phx.gbl...
> which
> connect
> the
>
|||Hi Claus,
I might need more inputs to trouble shoot this issue. Before this, you
could try Re- registering the MSDE Server in your Enterprise Manager.
Please use the Register SQL Server Wizard. For the sake of Clarity, I am
outling the steps here.
In the Enterprise Manager, If the MSDE Server is already
Registered, then Select Server, Right Click on the Server and Select Delete
SQL Server Registration.
1. In the Enterprise Manager, Start Register SQL Server Wizard. (Right
Click on SQL Server Group, Select New SQL Server Registration)
2. In the 'Select a SQL Server' page (second page), In the 'Available
Servers' Text box enter the Computer Name on which the MSDE is installed.
(Hope it is a default instance. If it is a Named Instance then enter
Instance Name also eg: Default Instance on Computer Named Test - TEST,
Named Instance 'Test1' on TEST - TEST\Test1 ). Then click 'ADD' button.
Click Next.
3. In the Next Page Select Authentication Mode.
4. In the Next Page Click Next
5. In the Last Page Select Finish.
After few minutes, You would see a screen which should say
'Server Registration completed' Status 'Registered Successfully'.
If this goes through, You would be able to see the MSDE in your Enterprise
manager. In case it fails, Please mail me the exact Error Message that you
would see in the Status column. We would try and troubleshoot it further.
Thanks,
Soma Sekhara Reddy
|||There is no firewall on that server and I'm in the same subnet trying to
connect.
"Ron Allen" <rallen@._nospam_src-us.com> wrote in message
news:eXZzmPJpEHA.1644@.tk2msftngp13.phx.gbl...
> Claus,
> Have you checked the firewall settings on the second server? If it
has[vbcol=seagreen]
> the TCP port used by MSDE blocked you won't be able to connect.
> Ron Allen
> "cjobes" <cjobes@.nova-tech.org> wrote in message
> news:%23WJfzS9oEHA.3460@.tk2msftngp13.phx.gbl...
named[vbcol=seagreen]
on[vbcol=seagreen]
we[vbcol=seagreen]
and[vbcol=seagreen]
one.
>
|||Thanks for your answer. This is what I have tried several times. The answer
I get back is "SQL server not running or access denied". I'm trying to
connect with SQL authentication (sa and password). I'm sure about the sa and
password because I use it in the local ODBC connection and the test works
fine.
I know I'm missing something really obvious - just can't put my finger on
it.
Claus
"Soma Sekhara Reddy" <somsredd@.microsoft.com> wrote in message
news:nyon0IQpEHA.3212@.cpmsftngxa06.phx.gbl...
> Hi Claus,
> I might need more inputs to trouble shoot this issue. Before this, you
> could try Re- registering the MSDE Server in your Enterprise Manager.
> Please use the Register SQL Server Wizard. For the sake of Clarity, I am
> outling the steps here.
> In the Enterprise Manager, If the MSDE Server is already
> Registered, then Select Server, Right Click on the Server and Select
Delete
> SQL Server Registration.
> 1. In the Enterprise Manager, Start Register SQL Server Wizard. (Right
> Click on SQL Server Group, Select New SQL Server Registration)
> 2. In the 'Select a SQL Server' page (second page), In the 'Available
> Servers' Text box enter the Computer Name on which the MSDE is installed.
> (Hope it is a default instance. If it is a Named Instance then enter
> Instance Name also eg: Default Instance on Computer Named Test - TEST,
> Named Instance 'Test1' on TEST - TEST\Test1 ). Then click 'ADD' button.
> Click Next.
> 3. In the Next Page Select Authentication Mode.
> 4. In the Next Page Click Next
> 5. In the Last Page Select Finish.
> After few minutes, You would see a screen which should
say
> 'Server Registration completed' Status 'Registered Successfully'.
> If this goes through, You would be able to see the MSDE in your Enterprise
> manager. In case it fails, Please mail me the exact Error Message that
you
> would see in the Status column. We would try and troubleshoot it further.
> Thanks,
> Soma Sekhara Reddy
>
|||Hi Claus,
Please use the 'ODBCPING' command line utility to check the connectivity.
The syntax is
odbcping -Sservername -Uusername -Ppassword
This tool is loaded with SQL Server client utilities and would be available
on your system. Please do not leave any space betweeb -S and servername,
-S is caps (case sensitive).
Thanks,
Soma Sekhara Reddy
Can't connect via Enterprise Manager
I had a similar problem that was due to the server not
using the proper TCP/IP port. I am guessing that one of
your servers is using a different port, (or none at all),
so it can't be seen by clients looking for the default
port number 1433, at least that was the problem in my case.
Check your Windows registry settings for the following
entries, (this is the key for a default instance, but
there are similar key paths for multiple instances):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServ
er\SuperSocketNetLib\Tcp\TcpPort
This value is the port that SQL Server will listen on. In
some cases it does not get set up correctly on the
install. The default is a decimal value of "1433" (if it
was blank then the server was only using shared memory
protocol)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\Su
perSocketNetLib\Tcp\DefaultPort
This value is the port that clients use to communicate
with the server. It normally will also be "1433" (decimal).
If you do change these values you should shut down the
server service first and check the registry again after
the server is running again... I had a heck of a time
getting my server to use port 1433, as it kept switching
to port 2433 after the server started up. (Not sure if
it's necessary, but I also put a "" in the TcpDynamicPorts
variable) to make sure dynamic port assignments is off.
Alternatively, if you do have different port settings and
need to keep them as they are, you can create alias
entries on your clients that will associate the proper
protocols and ports for each server.
HTH,
TK
>--Original Message--
>Hi All,
>We have a MSDE on a W2K server installed. It is running
fine and the
>application can access it without a problem. We have
another server on that
>same subnet that has an SQL 2000 server installed. When
trying to connect to
>the MSDE via the Enterprise Manager, only the local SQL
shows up and we
>cannot connect to the MSDE instance.
>When we go to the ODBC on the MSDE box we see both SQL -
the local and the
>remote one. On the ODBC on the other server we only see
the local one.
>Does anybody have an idea what is going on?
>Thanks,
>Claus
>
>.
>
Thanks for the reply. I finally was able to connect. I still don't have any
idea what the reason was. I rebooted both servers and it worked without
making any changes. No entries in the event logs.
MS never stops surprising me.
thanks again to all of you for your good advise,
Claus
"TK" <anonymous@.discussions.microsoft.com> wrote in message
news:3c9f01c4a58c$61560b90$a301280a@.phx.gbl...[vbcol=seagreen]
> I had a similar problem that was due to the server not
> using the proper TCP/IP port. I am guessing that one of
> your servers is using a different port, (or none at all),
> so it can't be seen by clients looking for the default
> port number 1433, at least that was the problem in my case.
> Check your Windows registry settings for the following
> entries, (this is the key for a default instance, but
> there are similar key paths for multiple instances):
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServ
> er\SuperSocketNetLib\Tcp\TcpPort
> This value is the port that SQL Server will listen on. In
> some cases it does not get set up correctly on the
> install. The default is a decimal value of "1433" (if it
> was blank then the server was only using shared memory
> protocol)
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\Su
> perSocketNetLib\Tcp\DefaultPort
> This value is the port that clients use to communicate
> with the server. It normally will also be "1433" (decimal).
> If you do change these values you should shut down the
> server service first and check the registry again after
> the server is running again... I had a heck of a time
> getting my server to use port 1433, as it kept switching
> to port 2433 after the server started up. (Not sure if
> it's necessary, but I also put a "" in the TcpDynamicPorts
> variable) to make sure dynamic port assignments is off.
> Alternatively, if you do have different port settings and
> need to keep them as they are, you can create alias
> entries on your clients that will associate the proper
> protocols and ports for each server.
> HTH,
> TK
> fine and the
> another server on that
> trying to connect to
> shows up and we
> the local and the
> the local one.
using the proper TCP/IP port. I am guessing that one of
your servers is using a different port, (or none at all),
so it can't be seen by clients looking for the default
port number 1433, at least that was the problem in my case.
Check your Windows registry settings for the following
entries, (this is the key for a default instance, but
there are similar key paths for multiple instances):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServ
er\SuperSocketNetLib\Tcp\TcpPort
This value is the port that SQL Server will listen on. In
some cases it does not get set up correctly on the
install. The default is a decimal value of "1433" (if it
was blank then the server was only using shared memory
protocol)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\Su
perSocketNetLib\Tcp\DefaultPort
This value is the port that clients use to communicate
with the server. It normally will also be "1433" (decimal).
If you do change these values you should shut down the
server service first and check the registry again after
the server is running again... I had a heck of a time
getting my server to use port 1433, as it kept switching
to port 2433 after the server started up. (Not sure if
it's necessary, but I also put a "" in the TcpDynamicPorts
variable) to make sure dynamic port assignments is off.
Alternatively, if you do have different port settings and
need to keep them as they are, you can create alias
entries on your clients that will associate the proper
protocols and ports for each server.
HTH,
TK
>--Original Message--
>Hi All,
>We have a MSDE on a W2K server installed. It is running
fine and the
>application can access it without a problem. We have
another server on that
>same subnet that has an SQL 2000 server installed. When
trying to connect to
>the MSDE via the Enterprise Manager, only the local SQL
shows up and we
>cannot connect to the MSDE instance.
>When we go to the ODBC on the MSDE box we see both SQL -
the local and the
>remote one. On the ODBC on the other server we only see
the local one.
>Does anybody have an idea what is going on?
>Thanks,
>Claus
>
>.
>
Thanks for the reply. I finally was able to connect. I still don't have any
idea what the reason was. I rebooted both servers and it worked without
making any changes. No entries in the event logs.
MS never stops surprising me.
thanks again to all of you for your good advise,
Claus
"TK" <anonymous@.discussions.microsoft.com> wrote in message
news:3c9f01c4a58c$61560b90$a301280a@.phx.gbl...[vbcol=seagreen]
> I had a similar problem that was due to the server not
> using the proper TCP/IP port. I am guessing that one of
> your servers is using a different port, (or none at all),
> so it can't be seen by clients looking for the default
> port number 1433, at least that was the problem in my case.
> Check your Windows registry settings for the following
> entries, (this is the key for a default instance, but
> there are similar key paths for multiple instances):
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServ
> er\SuperSocketNetLib\Tcp\TcpPort
> This value is the port that SQL Server will listen on. In
> some cases it does not get set up correctly on the
> install. The default is a decimal value of "1433" (if it
> was blank then the server was only using shared memory
> protocol)
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Client\Su
> perSocketNetLib\Tcp\DefaultPort
> This value is the port that clients use to communicate
> with the server. It normally will also be "1433" (decimal).
> If you do change these values you should shut down the
> server service first and check the registry again after
> the server is running again... I had a heck of a time
> getting my server to use port 1433, as it kept switching
> to port 2433 after the server started up. (Not sure if
> it's necessary, but I also put a "" in the TcpDynamicPorts
> variable) to make sure dynamic port assignments is off.
> Alternatively, if you do have different port settings and
> need to keep them as they are, you can create alias
> entries on your clients that will associate the proper
> protocols and ports for each server.
> HTH,
> TK
> fine and the
> another server on that
> trying to connect to
> shows up and we
> the local and the
> the local one.
Cant connect via EM after changing sa password?
A client of mine changed his SA password "because it hadn't been changed in a while". :mad: Now nobody can get into Enterprise Manager - opening EM or trying to right-click > Connect on the server yields an error:
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into Query Analyzer, which I thouhght was weird. But no luck with Enterprise Manager. It's just trying to log in as sa without prompting for a pw.
I already tried running sp_Password in Query Analyzer to change the pw back to what it was. Still can't connect to the SQL Server via Enterprise Manager.
What can I do?Did you edit the sql server registration and change the password there?
EDIT: And while I'm Here
Now nobody can get into Enterprise Manager
SCARY
Sorry Rudy|||Unclear from your post: have you tried editing the connection properties, or are you not able to get to that point?
If it won't even let you right-click on the registration to edit the properties, then try dropping the registration and creating a new one.|||Unless BUILTIN\Administrators local group is removed from SQL Server security, you can logon as a local admin or as a member of that group and easily change the SA password.
A connection could not be established to SERVER1.
Reason: login failed for user 'sa'.
Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.
Of course, if I right-click on the SERVER1 node, I get the same message.
My client remembers the password he set; I managed to use it to get into Query Analyzer, which I thouhght was weird. But no luck with Enterprise Manager. It's just trying to log in as sa without prompting for a pw.
I already tried running sp_Password in Query Analyzer to change the pw back to what it was. Still can't connect to the SQL Server via Enterprise Manager.
What can I do?Did you edit the sql server registration and change the password there?
EDIT: And while I'm Here
Now nobody can get into Enterprise Manager
SCARY
Sorry Rudy|||Unclear from your post: have you tried editing the connection properties, or are you not able to get to that point?
If it won't even let you right-click on the registration to edit the properties, then try dropping the registration and creating a new one.|||Unless BUILTIN\Administrators local group is removed from SQL Server security, you can logon as a local admin or as a member of that group and easily change the SA password.
Thursday, February 16, 2012
Can't connect to SQL 2005
Hi,
I just installed MSDE 2005 (or, rather, whatever it's called now) on my
machine. I'm trying to connect to it using Enterprise Manager, but I
keep getting Unable to connect/connection refused messages.
I've tried giving it my machine name, the word (local), localhost,
127.0.0.1, my machine's IP... nothing. I've also tried all those
permutations using cliconfg.exe, with the same results.
I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
running. Also I tried doing an ODBCPING against it, with the following
errors:
SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL
Server
does not exist or access denied.
SQLState: 01000 Native Error: 1326
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Any recommendations on a next step to try?If you're trying to run the EM for 2000, it won't work. Not supported.
"Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
> Hi,
> I just installed MSDE 2005 (or, rather, whatever it's called now) on my
> machine. I'm trying to connect to it using Enterprise Manager, but I
> keep getting Unable to connect/connection refused messages.
> I've tried giving it my machine name, the word (local), localhost,
> 127.0.0.1, my machine's IP... nothing. I've also tried all those
> permutations using cliconfg.exe, with the same results.
> I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
> running. Also I tried doing an ODBCPING against it, with the following
> errors:
> SQLState: 08001 Native Error: 17
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQ
L Server
> does not exist or access denied.
> SQLState: 01000 Native Error: 1326
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionOpen (Connect()).
> Any recommendations on a next step to try?|||Derrick Leggett wrote:
> If you're trying to run the EM for 2000, it won't work. Not supported.
>
> "Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
> news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
>
>
>
What about setting up an ODBC System DSN? Shouldn't this be supported
through the SQL Native Client? I get pretty much the same errors when
trying to do that.
I just installed MSDE 2005 (or, rather, whatever it's called now) on my
machine. I'm trying to connect to it using Enterprise Manager, but I
keep getting Unable to connect/connection refused messages.
I've tried giving it my machine name, the word (local), localhost,
127.0.0.1, my machine's IP... nothing. I've also tried all those
permutations using cliconfg.exe, with the same results.
I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
running. Also I tried doing an ODBCPING against it, with the following
errors:
SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL
Server
does not exist or access denied.
SQLState: 01000 Native Error: 1326
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Any recommendations on a next step to try?If you're trying to run the EM for 2000, it won't work. Not supported.
"Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
> Hi,
> I just installed MSDE 2005 (or, rather, whatever it's called now) on my
> machine. I'm trying to connect to it using Enterprise Manager, but I
> keep getting Unable to connect/connection refused messages.
> I've tried giving it my machine name, the word (local), localhost,
> 127.0.0.1, my machine's IP... nothing. I've also tried all those
> permutations using cliconfg.exe, with the same results.
> I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
> running. Also I tried doing an ODBCPING against it, with the following
> errors:
> SQLState: 08001 Native Error: 17
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQ
L Server
> does not exist or access denied.
> SQLState: 01000 Native Error: 1326
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionOpen (Connect()).
> Any recommendations on a next step to try?|||Derrick Leggett wrote:
> If you're trying to run the EM for 2000, it won't work. Not supported.
>
> "Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
> news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
>
>
>
What about setting up an ODBC System DSN? Shouldn't this be supported
through the SQL Native Client? I get pretty much the same errors when
trying to do that.
Can't connect to SQL 2005
Hi,
I just installed MSDE 2005 (or, rather, whatever it's called now) on my
machine. I'm trying to connect to it using Enterprise Manager, but I
keep getting Unable to connect/connection refused messages.
I've tried giving it my machine name, the word (local), localhost,
127.0.0.1, my machine's IP... nothing. I've also tried all those
permutations using cliconfg.exe, with the same results.
I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
running. Also I tried doing an ODBCPING against it, with the following
errors:
SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
SQLState: 01000 Native Error: 1326
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Any recommendations on a next step to try?
If you're trying to run the EM for 2000, it won't work. Not supported.
"Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
> Hi,
> I just installed MSDE 2005 (or, rather, whatever it's called now) on my
> machine. I'm trying to connect to it using Enterprise Manager, but I
> keep getting Unable to connect/connection refused messages.
> I've tried giving it my machine name, the word (local), localhost,
> 127.0.0.1, my machine's IP... nothing. I've also tried all those
> permutations using cliconfg.exe, with the same results.
> I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
> running. Also I tried doing an ODBCPING against it, with the following
> errors:
> SQLState: 08001 Native Error: 17
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
> does not exist or access denied.
> SQLState: 01000 Native Error: 1326
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionOpen (Connect()).
> Any recommendations on a next step to try?
|||Derrick Leggett wrote:
> If you're trying to run the EM for 2000, it won't work. Not supported.
>
> "Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
> news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
>
>
What about setting up an ODBC System DSN? Shouldn't this be supported
through the SQL Native Client? I get pretty much the same errors when
trying to do that.
I just installed MSDE 2005 (or, rather, whatever it's called now) on my
machine. I'm trying to connect to it using Enterprise Manager, but I
keep getting Unable to connect/connection refused messages.
I've tried giving it my machine name, the word (local), localhost,
127.0.0.1, my machine's IP... nothing. I've also tried all those
permutations using cliconfg.exe, with the same results.
I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
running. Also I tried doing an ODBCPING against it, with the following
errors:
SQLState: 08001 Native Error: 17
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
does not exist or access denied.
SQLState: 01000 Native Error: 1326
Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
ConnectionOpen (Connect()).
Any recommendations on a next step to try?
If you're trying to run the EM for 2000, it won't work. Not supported.
"Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
> Hi,
> I just installed MSDE 2005 (or, rather, whatever it's called now) on my
> machine. I'm trying to connect to it using Enterprise Manager, but I
> keep getting Unable to connect/connection refused messages.
> I've tried giving it my machine name, the word (local), localhost,
> 127.0.0.1, my machine's IP... nothing. I've also tried all those
> permutations using cliconfg.exe, with the same results.
> I ran the SQL Manager plug-in, and it shows that SQL Server is indeed
> running. Also I tried doing an ODBCPING against it, with the following
> errors:
> SQLState: 08001 Native Error: 17
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server
> does not exist or access denied.
> SQLState: 01000 Native Error: 1326
> Info. Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]
> ConnectionOpen (Connect()).
> Any recommendations on a next step to try?
|||Derrick Leggett wrote:
> If you're trying to run the EM for 2000, it won't work. Not supported.
>
> "Scott McNair" <scott.mcnair@.sfmco.takethispartout.com> wrote in message
> news:Xns95D7AB2AE2D3Bsfmco@.207.46.248.16...
>
>
What about setting up an ODBC System DSN? Shouldn't this be supported
through the SQL Native Client? I get pretty much the same errors when
trying to do that.
Cant connect to server !
My project work ok with Asp.net development server, but when i use IIS :
I'm sure i can connect to SQL server by SQL Server Enterprise Manager and my project debug with Asp.net development server ok.
Anyone please help me.
This article should help:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
and if that doesn't then take a look here:
http://blogs.msdn.com/sql_protocols/archive/2007/03/31/named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server.aspx
Sunday, February 12, 2012
Cant connect to db via code, but can from SQL Server.
Having an issue where I can connect to a remote SQL Database server via enterprise manager, however using the exact same db credentials, I can't connect via the .NET SqlConnection object...
Anyone have this error? Did you ever figure it out?
The error I get is: "SQL Server does not exist or access denied."
Again... I'm using the EXACT same user name, password, port number. I've setup an alias in Client Network Utility...
The SQL Server Enterprise is running on the exact same PC as the code I'm trying to execute.
Thanks for any help!Are you using Integrated Security, what does your connection string look like?|||*UGH*...
I hate it when I waste time on such a trivial error. ;)
It was a stupid mistake. In C, C#, C++, you have to escape the escape char. I had forgotten to do that in my con str.
Can't connect to databases through Enterprise Manager
Understand I am not a DBA. I am just the guy who has to
work with this stuff.
We have client software that uses SQL 7 as a database.
Winpak is a door access software made by Northern. It
stores proxy card info, access levels, historys, etc. in
a SQL 7 database. I know the databases are still there
because Winpak connects and I can pull up info.
This started because I noticed whoever set up the primary
and archive databases pointed them both to the same file
name. I backed up the primary and deleted it. Restored
it with the full backup and made sure it was pointed to a
different file name. Everything worked fine and still
showed up in Enterprise Manager. I restarted the computer
later and tried to go back into Enterprise Manager. Tried
to expand 'SQL Server Group' to list all the databases and
I got an error saying, "A connection could not be
established to COMPUTER - Cannot open user default
database '<ID>'. Using master database instead. Please
verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the COMPUTER
node) and try again."
My services were running just fine and when I checked my
registration properties everything looked fine. Redid the
registration properties with no luck. Using NT
authentication and even making a new one. The other
problem is that somebody set this thing up 3 years ago and
I have no idea what the 'sa' password is and I have tried
every simple password I can think of. I am checked out
the knowledge database articles matching my error message
and they didn't realy help cuz I either needed the 'sa'
password or I don't know how to impliment the solution
based on my limited knowledge of SQL. I need to do a
final backup to move all the info to a new machine with
SQL 2000. I am really stuck (and screwed) if I can't get
that info off cuz we just entered in a few hundred more
employees so using an old backup isn't going to save me.
Help would be greatly appreciated
Hi,
It seems the Login ID you are using is defaulted to the database you have
deleted. That is the reason you are getting the error.
How to change the SA Password,
1. Login to Query analyzer using Windows Authentication
2. Execute the beloe command
sp_password null,'passwordsa',sa
(now the password for sa is passwordsa)
How to change the default database of your existing users, which gave error
1. Login to query analyzer as SA
2. execute below statement
sp_defaultdb <loginame>,<new database name>
3. After this you will be able to login using the old id itself.
Thanks
Hari
MCDBA
"Brendan" <anonymous@.discussions.microsoft.com> wrote in message
news:124bf01c41152$811230e0$a501280a@.phx.gbl...
> Understand I am not a DBA. I am just the guy who has to
> work with this stuff.
> We have client software that uses SQL 7 as a database.
> Winpak is a door access software made by Northern. It
> stores proxy card info, access levels, historys, etc. in
> a SQL 7 database. I know the databases are still there
> because Winpak connects and I can pull up info.
> This started because I noticed whoever set up the primary
> and archive databases pointed them both to the same file
> name. I backed up the primary and deleted it. Restored
> it with the full backup and made sure it was pointed to a
> different file name. Everything worked fine and still
> showed up in Enterprise Manager. I restarted the computer
> later and tried to go back into Enterprise Manager. Tried
> to expand 'SQL Server Group' to list all the databases and
> I got an error saying, "A connection could not be
> established to COMPUTER - Cannot open user default
> database '<ID>'. Using master database instead. Please
> verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the COMPUTER
> node) and try again."
> My services were running just fine and when I checked my
> registration properties everything looked fine. Redid the
> registration properties with no luck. Using NT
> authentication and even making a new one. The other
> problem is that somebody set this thing up 3 years ago and
> I have no idea what the 'sa' password is and I have tried
> every simple password I can think of. I am checked out
> the knowledge database articles matching my error message
> and they didn't realy help cuz I either needed the 'sa'
> password or I don't know how to impliment the solution
> based on my limited knowledge of SQL. I need to do a
> final backup to move all the info to a new machine with
> SQL 2000. I am really stuck (and screwed) if I can't get
> that info off cuz we just entered in a few hundred more
> employees so using an old backup isn't going to save me.
> Help would be greatly appreciated
|||Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.
>--Original Message--
>Hi,
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>How to change the SA Password,
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
> sp_password null,'passwordsa',sa
>(now the password for sa is passwordsa)
>How to change the default database of your existing
users, which gave error
>1. Login to query analyzer as SA
>2. execute below statement
> sp_defaultdb <loginame>,<new database name>
>3. After this you will be able to login using the old id
itself.
>Thanks
>Hari
>MCDBA
>
>
>"Brendan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:124bf01c41152$811230e0$a501280a@.phx.gbl...
to
in
there
primary
file
Restored
to a
computer
Tried
and
Please
COMPUTER
my
the
and
tried
message
get
me.
>
>.
>
work with this stuff.
We have client software that uses SQL 7 as a database.
Winpak is a door access software made by Northern. It
stores proxy card info, access levels, historys, etc. in
a SQL 7 database. I know the databases are still there
because Winpak connects and I can pull up info.
This started because I noticed whoever set up the primary
and archive databases pointed them both to the same file
name. I backed up the primary and deleted it. Restored
it with the full backup and made sure it was pointed to a
different file name. Everything worked fine and still
showed up in Enterprise Manager. I restarted the computer
later and tried to go back into Enterprise Manager. Tried
to expand 'SQL Server Group' to list all the databases and
I got an error saying, "A connection could not be
established to COMPUTER - Cannot open user default
database '<ID>'. Using master database instead. Please
verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the COMPUTER
node) and try again."
My services were running just fine and when I checked my
registration properties everything looked fine. Redid the
registration properties with no luck. Using NT
authentication and even making a new one. The other
problem is that somebody set this thing up 3 years ago and
I have no idea what the 'sa' password is and I have tried
every simple password I can think of. I am checked out
the knowledge database articles matching my error message
and they didn't realy help cuz I either needed the 'sa'
password or I don't know how to impliment the solution
based on my limited knowledge of SQL. I need to do a
final backup to move all the info to a new machine with
SQL 2000. I am really stuck (and screwed) if I can't get
that info off cuz we just entered in a few hundred more
employees so using an old backup isn't going to save me.
Help would be greatly appreciated
Hi,
It seems the Login ID you are using is defaulted to the database you have
deleted. That is the reason you are getting the error.
How to change the SA Password,
1. Login to Query analyzer using Windows Authentication
2. Execute the beloe command
sp_password null,'passwordsa',sa
(now the password for sa is passwordsa)
How to change the default database of your existing users, which gave error
1. Login to query analyzer as SA
2. execute below statement
sp_defaultdb <loginame>,<new database name>
3. After this you will be able to login using the old id itself.
Thanks
Hari
MCDBA
"Brendan" <anonymous@.discussions.microsoft.com> wrote in message
news:124bf01c41152$811230e0$a501280a@.phx.gbl...
> Understand I am not a DBA. I am just the guy who has to
> work with this stuff.
> We have client software that uses SQL 7 as a database.
> Winpak is a door access software made by Northern. It
> stores proxy card info, access levels, historys, etc. in
> a SQL 7 database. I know the databases are still there
> because Winpak connects and I can pull up info.
> This started because I noticed whoever set up the primary
> and archive databases pointed them both to the same file
> name. I backed up the primary and deleted it. Restored
> it with the full backup and made sure it was pointed to a
> different file name. Everything worked fine and still
> showed up in Enterprise Manager. I restarted the computer
> later and tried to go back into Enterprise Manager. Tried
> to expand 'SQL Server Group' to list all the databases and
> I got an error saying, "A connection could not be
> established to COMPUTER - Cannot open user default
> database '<ID>'. Using master database instead. Please
> verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the COMPUTER
> node) and try again."
> My services were running just fine and when I checked my
> registration properties everything looked fine. Redid the
> registration properties with no luck. Using NT
> authentication and even making a new one. The other
> problem is that somebody set this thing up 3 years ago and
> I have no idea what the 'sa' password is and I have tried
> every simple password I can think of. I am checked out
> the knowledge database articles matching my error message
> and they didn't realy help cuz I either needed the 'sa'
> password or I don't know how to impliment the solution
> based on my limited knowledge of SQL. I need to do a
> final backup to move all the info to a new machine with
> SQL 2000. I am really stuck (and screwed) if I can't get
> that info off cuz we just entered in a few hundred more
> employees so using an old backup isn't going to save me.
> Help would be greatly appreciated
|||Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.
>--Original Message--
>Hi,
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>How to change the SA Password,
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
> sp_password null,'passwordsa',sa
>(now the password for sa is passwordsa)
>How to change the default database of your existing
users, which gave error
>1. Login to query analyzer as SA
>2. execute below statement
> sp_defaultdb <loginame>,<new database name>
>3. After this you will be able to login using the old id
itself.
>Thanks
>Hari
>MCDBA
>
>
>"Brendan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:124bf01c41152$811230e0$a501280a@.phx.gbl...
to
in
there
primary
file
Restored
to a
computer
Tried
and
Please
COMPUTER
my
the
and
tried
message
get
me.
>
>.
>
Can't connect to databases through Enterprise Manager
Understand I am not a DBA. I am just the guy who has to
work with this stuff.
We have client software that uses SQL 7 as a database.
Winpak is a door access software made by Northern. It
stores proxy card info, access levels, historys, etc. in
a SQL 7 database. I know the databases are still there
because Winpak connects and I can pull up info.
This started because I noticed whoever set up the primary
and archive databases pointed them both to the same file
name. I backed up the primary and deleted it. Restored
it with the full backup and made sure it was pointed to a
different file name. Everything worked fine and still
showed up in Enterprise Manager. I restarted the computer
later and tried to go back into Enterprise Manager. Tried
to expand 'SQL Server Group' to list all the databases and
I got an error saying, "A connection could not be
established to COMPUTER - Cannot open user default
database '<ID>'. Using master database instead. Please
verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the COMPUTER
node) and try again."
My services were running just fine and when I checked my
registration properties everything looked fine. Redid the
registration properties with no luck. Using NT
authentication and even making a new one. The other
problem is that somebody set this thing up 3 years ago and
I have no idea what the 'sa' password is and I have tried
every simple password I can think of. I am checked out
the knowledge database articles matching my error message
and they didn't realy help cuz I either needed the 'sa'
password or I don't know how to impliment the solution
based on my limited knowledge of SQL. I need to do a
final backup to move all the info to a new machine with
SQL 2000. I am really stuck (and screwed) if I can't get
that info off cuz we just entered in a few hundred more
employees so using an old backup isn't going to save me.
Help would be greatly appreciatedHi,
It seems the Login ID you are using is defaulted to the database you have
deleted. That is the reason you are getting the error.
How to change the SA Password,
1. Login to Query analyzer using Windows Authentication
2. Execute the beloe command
sp_password null,'passwordsa',sa
(now the password for sa is passwordsa)
How to change the default database of your existing users, which gave error
1. Login to query analyzer as SA
2. execute below statement
sp_defaultdb <loginame>,<new database name>
3. After this you will be able to login using the old id itself.
Thanks
Hari
MCDBA
"Brendan" <anonymous@.discussions.microsoft.com> wrote in message
news:124bf01c41152$811230e0$a501280a@.phx
.gbl...
> Understand I am not a DBA. I am just the guy who has to
> work with this stuff.
> We have client software that uses SQL 7 as a database.
> Winpak is a door access software made by Northern. It
> stores proxy card info, access levels, historys, etc. in
> a SQL 7 database. I know the databases are still there
> because Winpak connects and I can pull up info.
> This started because I noticed whoever set up the primary
> and archive databases pointed them both to the same file
> name. I backed up the primary and deleted it. Restored
> it with the full backup and made sure it was pointed to a
> different file name. Everything worked fine and still
> showed up in Enterprise Manager. I restarted the computer
> later and tried to go back into Enterprise Manager. Tried
> to expand 'SQL Server Group' to list all the databases and
> I got an error saying, "A connection could not be
> established to COMPUTER - Cannot open user default
> database '<ID>'. Using master database instead. Please
> verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the COMPUTER
> node) and try again."
> My services were running just fine and when I checked my
> registration properties everything looked fine. Redid the
> registration properties with no luck. Using NT
> authentication and even making a new one. The other
> problem is that somebody set this thing up 3 years ago and
> I have no idea what the 'sa' password is and I have tried
> every simple password I can think of. I am checked out
> the knowledge database articles matching my error message
> and they didn't realy help cuz I either needed the 'sa'
> password or I don't know how to impliment the solution
> based on my limited knowledge of SQL. I need to do a
> final backup to move all the info to a new machine with
> SQL 2000. I am really stuck (and screwed) if I can't get
> that info off cuz we just entered in a few hundred more
> employees so using an old backup isn't going to save me.
> Help would be greatly appreciated|||Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.
>--Original Message--
>Hi,
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>How to change the SA Password,
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
> sp_password null,'passwordsa',sa
>(now the password for sa is passwordsa)
>How to change the default database of your existing
users, which gave error
>1. Login to query analyzer as SA
>2. execute below statement
> sp_defaultdb <loginame>,<new database name>
>3. After this you will be able to login using the old id
itself.
>Thanks
>Hari
>MCDBA
>
>
>"Brendan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:124bf01c41152$811230e0$a501280a@.phx
.gbl...
to
in
there
primary
file
Restored
to a
computer
Tried
and
Please
COMPUTER
my
the
and
tried
message
get
me.
>
>.
>
work with this stuff.
We have client software that uses SQL 7 as a database.
Winpak is a door access software made by Northern. It
stores proxy card info, access levels, historys, etc. in
a SQL 7 database. I know the databases are still there
because Winpak connects and I can pull up info.
This started because I noticed whoever set up the primary
and archive databases pointed them both to the same file
name. I backed up the primary and deleted it. Restored
it with the full backup and made sure it was pointed to a
different file name. Everything worked fine and still
showed up in Enterprise Manager. I restarted the computer
later and tried to go back into Enterprise Manager. Tried
to expand 'SQL Server Group' to list all the databases and
I got an error saying, "A connection could not be
established to COMPUTER - Cannot open user default
database '<ID>'. Using master database instead. Please
verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the COMPUTER
node) and try again."
My services were running just fine and when I checked my
registration properties everything looked fine. Redid the
registration properties with no luck. Using NT
authentication and even making a new one. The other
problem is that somebody set this thing up 3 years ago and
I have no idea what the 'sa' password is and I have tried
every simple password I can think of. I am checked out
the knowledge database articles matching my error message
and they didn't realy help cuz I either needed the 'sa'
password or I don't know how to impliment the solution
based on my limited knowledge of SQL. I need to do a
final backup to move all the info to a new machine with
SQL 2000. I am really stuck (and screwed) if I can't get
that info off cuz we just entered in a few hundred more
employees so using an old backup isn't going to save me.
Help would be greatly appreciatedHi,
It seems the Login ID you are using is defaulted to the database you have
deleted. That is the reason you are getting the error.
How to change the SA Password,
1. Login to Query analyzer using Windows Authentication
2. Execute the beloe command
sp_password null,'passwordsa',sa
(now the password for sa is passwordsa)
How to change the default database of your existing users, which gave error
1. Login to query analyzer as SA
2. execute below statement
sp_defaultdb <loginame>,<new database name>
3. After this you will be able to login using the old id itself.
Thanks
Hari
MCDBA
"Brendan" <anonymous@.discussions.microsoft.com> wrote in message
news:124bf01c41152$811230e0$a501280a@.phx
.gbl...
> Understand I am not a DBA. I am just the guy who has to
> work with this stuff.
> We have client software that uses SQL 7 as a database.
> Winpak is a door access software made by Northern. It
> stores proxy card info, access levels, historys, etc. in
> a SQL 7 database. I know the databases are still there
> because Winpak connects and I can pull up info.
> This started because I noticed whoever set up the primary
> and archive databases pointed them both to the same file
> name. I backed up the primary and deleted it. Restored
> it with the full backup and made sure it was pointed to a
> different file name. Everything worked fine and still
> showed up in Enterprise Manager. I restarted the computer
> later and tried to go back into Enterprise Manager. Tried
> to expand 'SQL Server Group' to list all the databases and
> I got an error saying, "A connection could not be
> established to COMPUTER - Cannot open user default
> database '<ID>'. Using master database instead. Please
> verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the COMPUTER
> node) and try again."
> My services were running just fine and when I checked my
> registration properties everything looked fine. Redid the
> registration properties with no luck. Using NT
> authentication and even making a new one. The other
> problem is that somebody set this thing up 3 years ago and
> I have no idea what the 'sa' password is and I have tried
> every simple password I can think of. I am checked out
> the knowledge database articles matching my error message
> and they didn't realy help cuz I either needed the 'sa'
> password or I don't know how to impliment the solution
> based on my limited knowledge of SQL. I need to do a
> final backup to move all the info to a new machine with
> SQL 2000. I am really stuck (and screwed) if I can't get
> that info off cuz we just entered in a few hundred more
> employees so using an old backup isn't going to save me.
> Help would be greatly appreciated|||Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.
>--Original Message--
>Hi,
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>How to change the SA Password,
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
> sp_password null,'passwordsa',sa
>(now the password for sa is passwordsa)
>How to change the default database of your existing
users, which gave error
>1. Login to query analyzer as SA
>2. execute below statement
> sp_defaultdb <loginame>,<new database name>
>3. After this you will be able to login using the old id
itself.
>Thanks
>Hari
>MCDBA
>
>
>"Brendan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:124bf01c41152$811230e0$a501280a@.phx
.gbl...
to
in
there
primary
file
Restored
to a
computer
Tried
and
Please
COMPUTER
my
the
and
tried
message
get
me.
>
>.
>
Friday, February 10, 2012
Can't connect to / see cube
Need some input please.
I have a development domain, with one server running SQL Server 2000 sp
3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
REporting Services.
I used to be able to connect to my databases in Analysis Services, but
today I updated one of them, and now I can't connect to it. I can log
into the server, and see my Foodmart demo base. But I can't see my new
database.
I restored the database from a cab-file, and it restored OK. I can
prosess 2 out of 4 individual cubes. If I right-click the database and
choose "Process the Database", it fails to process. There seems to be a
problem with the database.
Is this why I can't connect to the database / cubes from other
computers? I can log on using http and the right username and password,
and I get to see Foodmart, but not the database / cubes I want to work
with.
Please advise, or at least give a hint on where I can find more info.
Kaisa
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!Two possibilities typically occur:
1) either you have an old version of PTS on your client machine (run
ptslite.exe from the SP3 Analysis Services distribution), or
2) you don't have security rights to the cube, i.e. if you've not included
the everyone role. Foodmart has such a role, and thus you can see it.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kaisa" <kaisaremoveml@.hotmail.com> wrote in message
news:%23QRcNQpuEHA.2804@.TK2MSFTNGP14.phx.gbl...
> Need some input please.
> I have a development domain, with one server running SQL Server 2000 sp
> 3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
> REporting Services.
> I used to be able to connect to my databases in Analysis Services, but
> today I updated one of them, and now I can't connect to it. I can log
> into the server, and see my Foodmart demo base. But I can't see my new
> database.
> I restored the database from a cab-file, and it restored OK. I can
> prosess 2 out of 4 individual cubes. If I right-click the database and
> choose "Process the Database", it fails to process. There seems to be a
> problem with the database.
> Is this why I can't connect to the database / cubes from other
> computers? I can log on using http and the right username and password,
> and I get to see Foodmart, but not the database / cubes I want to work
> with.
> Please advise, or at least give a hint on where I can find more info.
> Kaisa
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!|||"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message news:<O8F#B6ruEHA
.684@.TK2MSFTNGP10.phx.gbl>...
> Two possibilities typically occur:
> 1) either you have an old version of PTS on your client machine (run
> ptslite.exe from the SP3 Analysis Services distribution), or
> 2) you don't have security rights to the cube, i.e. if you've not included
> the everyone role. Foodmart has such a role, and thus you can see it.
> --
Hey Dave!
Thanks a lot! I added the Everyone role and now I can use my database.
I'm so happy right now!
:D
Kaisa M. Lindahl
I have a development domain, with one server running SQL Server 2000 sp
3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
REporting Services.
I used to be able to connect to my databases in Analysis Services, but
today I updated one of them, and now I can't connect to it. I can log
into the server, and see my Foodmart demo base. But I can't see my new
database.
I restored the database from a cab-file, and it restored OK. I can
prosess 2 out of 4 individual cubes. If I right-click the database and
choose "Process the Database", it fails to process. There seems to be a
problem with the database.
Is this why I can't connect to the database / cubes from other
computers? I can log on using http and the right username and password,
and I get to see Foodmart, but not the database / cubes I want to work
with.
Please advise, or at least give a hint on where I can find more info.
Kaisa
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!Two possibilities typically occur:
1) either you have an old version of PTS on your client machine (run
ptslite.exe from the SP3 Analysis Services distribution), or
2) you don't have security rights to the cube, i.e. if you've not included
the everyone role. Foodmart has such a role, and thus you can see it.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kaisa" <kaisaremoveml@.hotmail.com> wrote in message
news:%23QRcNQpuEHA.2804@.TK2MSFTNGP14.phx.gbl...
> Need some input please.
> I have a development domain, with one server running SQL Server 2000 sp
> 3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
> REporting Services.
> I used to be able to connect to my databases in Analysis Services, but
> today I updated one of them, and now I can't connect to it. I can log
> into the server, and see my Foodmart demo base. But I can't see my new
> database.
> I restored the database from a cab-file, and it restored OK. I can
> prosess 2 out of 4 individual cubes. If I right-click the database and
> choose "Process the Database", it fails to process. There seems to be a
> problem with the database.
> Is this why I can't connect to the database / cubes from other
> computers? I can log on using http and the right username and password,
> and I get to see Foodmart, but not the database / cubes I want to work
> with.
> Please advise, or at least give a hint on where I can find more info.
> Kaisa
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!|||"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message news:<O8F#B6ruEHA
.684@.TK2MSFTNGP10.phx.gbl>...
> Two possibilities typically occur:
> 1) either you have an old version of PTS on your client machine (run
> ptslite.exe from the SP3 Analysis Services distribution), or
> 2) you don't have security rights to the cube, i.e. if you've not included
> the everyone role. Foodmart has such a role, and thus you can see it.
> --
Hey Dave!
Thanks a lot! I added the Everyone role and now I can use my database.
I'm so happy right now!
:D
Kaisa M. Lindahl
Can't connect to / see cube
Need some input please.
I have a development domain, with one server running SQL Server 2000 sp
3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
REporting Services.
I used to be able to connect to my databases in Analysis Services, but
today I updated one of them, and now I can't connect to it. I can log
into the server, and see my Foodmart demo base. But I can't see my new
database.
I restored the database from a cab-file, and it restored OK. I can
prosess 2 out of 4 individual cubes. If I right-click the database and
choose "Process the Database", it fails to process. There seems to be a
problem with the database.
Is this why I can't connect to the database / cubes from other
computers? I can log on using http and the right username and password,
and I get to see Foodmart, but not the database / cubes I want to work
with.
Please advise, or at least give a hint on where I can find more info.
Kaisa
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Two possibilities typically occur:
1) either you have an old version of PTS on your client machine (run
ptslite.exe from the SP3 Analysis Services distribution), or
2) you don't have security rights to the cube, i.e. if you've not included
the everyone role. Foodmart has such a role, and thus you can see it.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kaisa" <kaisaremoveml@.hotmail.com> wrote in message
news:%23QRcNQpuEHA.2804@.TK2MSFTNGP14.phx.gbl...
> Need some input please.
> I have a development domain, with one server running SQL Server 2000 sp
> 3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
> REporting Services.
> I used to be able to connect to my databases in Analysis Services, but
> today I updated one of them, and now I can't connect to it. I can log
> into the server, and see my Foodmart demo base. But I can't see my new
> database.
> I restored the database from a cab-file, and it restored OK. I can
> prosess 2 out of 4 individual cubes. If I right-click the database and
> choose "Process the Database", it fails to process. There seems to be a
> problem with the database.
> Is this why I can't connect to the database / cubes from other
> computers? I can log on using http and the right username and password,
> and I get to see Foodmart, but not the database / cubes I want to work
> with.
> Please advise, or at least give a hint on where I can find more info.
> Kaisa
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message news:<O8F#B6ruEHA.684@.TK2MSFTNGP10.phx.gbl>...
> Two possibilities typically occur:
> 1) either you have an old version of PTS on your client machine (run
> ptslite.exe from the SP3 Analysis Services distribution), or
> 2) you don't have security rights to the cube, i.e. if you've not included
> the everyone role. Foodmart has such a role, and thus you can see it.
> --
Hey Dave!
Thanks a lot! I added the Everyone role and now I can use my database.
I'm so happy right now!
:D
Kaisa M. Lindahl
I have a development domain, with one server running SQL Server 2000 sp
3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
REporting Services.
I used to be able to connect to my databases in Analysis Services, but
today I updated one of them, and now I can't connect to it. I can log
into the server, and see my Foodmart demo base. But I can't see my new
database.
I restored the database from a cab-file, and it restored OK. I can
prosess 2 out of 4 individual cubes. If I right-click the database and
choose "Process the Database", it fails to process. There seems to be a
problem with the database.
Is this why I can't connect to the database / cubes from other
computers? I can log on using http and the right username and password,
and I get to see Foodmart, but not the database / cubes I want to work
with.
Please advise, or at least give a hint on where I can find more info.
Kaisa
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
Two possibilities typically occur:
1) either you have an old version of PTS on your client machine (run
ptslite.exe from the SP3 Analysis Services distribution), or
2) you don't have security rights to the cube, i.e. if you've not included
the everyone role. Foodmart has such a role, and thus you can see it.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kaisa" <kaisaremoveml@.hotmail.com> wrote in message
news:%23QRcNQpuEHA.2804@.TK2MSFTNGP14.phx.gbl...
> Need some input please.
> I have a development domain, with one server running SQL Server 2000 sp
> 3 Enterprise edition, Analysis Services Sp 3 Enterprise Edition and
> REporting Services.
> I used to be able to connect to my databases in Analysis Services, but
> today I updated one of them, and now I can't connect to it. I can log
> into the server, and see my Foodmart demo base. But I can't see my new
> database.
> I restored the database from a cab-file, and it restored OK. I can
> prosess 2 out of 4 individual cubes. If I right-click the database and
> choose "Process the Database", it fails to process. There seems to be a
> problem with the database.
> Is this why I can't connect to the database / cubes from other
> computers? I can log on using http and the right username and password,
> and I get to see Foodmart, but not the database / cubes I want to work
> with.
> Please advise, or at least give a hint on where I can find more info.
> Kaisa
>
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
|||"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message news:<O8F#B6ruEHA.684@.TK2MSFTNGP10.phx.gbl>...
> Two possibilities typically occur:
> 1) either you have an old version of PTS on your client machine (run
> ptslite.exe from the SP3 Analysis Services distribution), or
> 2) you don't have security rights to the cube, i.e. if you've not included
> the everyone role. Foodmart has such a role, and thus you can see it.
> --
Hey Dave!
Thanks a lot! I added the Everyone role and now I can use my database.
I'm so happy right now!
:D
Kaisa M. Lindahl
Subscribe to:
Posts (Atom)