Hi!
I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
my domain account (HIK\Tommy) wich is a member of the Administrators group on
my computer and there is a corresponding Windows login account with sysadmin
permissions in SQL Server.
I can do most things with that account, BUT when I try to create a diagram
to a database. SQL does not like the owner of the database (my domain
account)
This is the error message that show up:
"Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or ALTER AUTHORIZATION statement to set the
database owner to a valid login, then add the database diagram support
objects."
Again when I try to run a job that is owned by my domain account (HIK\Tommy)
Following message arise:
"The job failed. Unable to determine if the owner (HIK\Tommy) of job
MaintenancePlan2 has server access (reason: Could not obtain information
about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
(Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
3621))."
I would be very grateful if you could come up with some suggestions.
Regards
TommyThis might be due to a mismatch between the 'dbo' user mapping and the
actual database owner. You can correct this with sp_changedbowner:
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> Hi!
> I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> my domain account (HIK\Tommy) wich is a member of the Administrators group
> on
> my computer and there is a corresponding Windows login account with
> sysadmin
> permissions in SQL Server.
> I can do most things with that account, BUT when I try to create a diagram
> to a database. SQL does not like the owner of the database (my domain
> account)
> This is the error message that show up:
> "Database diagram support objects cannot be installed because this
> database
> does not have a valid owner. To continue, first use the Files page of the
> Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> database owner to a valid login, then add the database diagram support
> objects."
> Again when I try to run a job that is owned by my domain account
> (HIK\Tommy)
> Following message arise:
> "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> MaintenancePlan2 has server access (reason: Could not obtain information
> about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> 3621))."
> I would be very grateful if you could come up with some suggestions.
> Regards
> Tommy|||Thanks for your suggestion but it does not work.
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
doesn't change anything.
On the other hand it 's possible to change user to sa and everything works
OK, so it's my domain name that is the trouble. Have never had this problem i
SQL Server 2K.
/Tommy
"Dan Guzman" wrote:
> This might be due to a mismatch between the 'dbo' user mapping and the
> actual database owner. You can correct this with sp_changedbowner:
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> > Hi!
> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> > my domain account (HIK\Tommy) wich is a member of the Administrators group
> > on
> > my computer and there is a corresponding Windows login account with
> > sysadmin
> > permissions in SQL Server.
> >
> > I can do most things with that account, BUT when I try to create a diagram
> > to a database. SQL does not like the owner of the database (my domain
> > account)
> >
> > This is the error message that show up:
> > "Database diagram support objects cannot be installed because this
> > database
> > does not have a valid owner. To continue, first use the Files page of the
> > Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> > database owner to a valid login, then add the database diagram support
> > objects."
> >
> > Again when I try to run a job that is owned by my domain account
> > (HIK\Tommy)
> >
> > Following message arise:
> >
> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> > MaintenancePlan2 has server access (reason: Could not obtain information
> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> > (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> > 3621))."
> >
> > I would be very grateful if you could come up with some suggestions.
> >
> > Regards
> > Tommy
>
>|||My apologies but I misread your post. I guess I should a finished my coffee
first :-)
For your first issue, the database needs to be in 90 compatibility mode in
order to create diagrams.
Regarding your second problem, run the SQL Server Configuration utility to
make sure the SQL Agent isn't running under the Network Service account.
Use a domain account.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> Thanks for your suggestion but it does not work.
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> doesn't change anything.
> On the other hand it 's possible to change user to sa and everything works
> OK, so it's my domain name that is the trouble. Have never had this
> problem i
> SQL Server 2K.
> /Tommy
> "Dan Guzman" wrote:
>> This might be due to a mismatch between the 'dbo' user mapping and the
>> actual database owner. You can correct this with sp_changedbowner:
>> USE MyDatabase
>> EXEC sp_changedbowner 'HIK\Tommy'
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> > Hi!
>> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
>> > with
>> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> > group
>> > on
>> > my computer and there is a corresponding Windows login account with
>> > sysadmin
>> > permissions in SQL Server.
>> >
>> > I can do most things with that account, BUT when I try to create a
>> > diagram
>> > to a database. SQL does not like the owner of the database (my domain
>> > account)
>> >
>> > This is the error message that show up:
>> > "Database diagram support objects cannot be installed because this
>> > database
>> > does not have a valid owner. To continue, first use the Files page of
>> > the
>> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
>> > the
>> > database owner to a valid login, then add the database diagram support
>> > objects."
>> >
>> > Again when I try to run a job that is owned by my domain account
>> > (HIK\Tommy)
>> >
>> > Following message arise:
>> >
>> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
>> > MaintenancePlan2 has server access (reason: Could not obtain
>> > information
>> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> > 42000]
>> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> > (Error
>> > 3621))."
>> >
>> > I would be very grateful if you could come up with some suggestions.
>> >
>> > Regards
>> > Tommy
>>|||Using a domain account for the Agent and SQL Server service solves the
problem with recognizeing job owner as my domain login (HIK\Tommy), but it
still don't like my domain login as database owner when trying to create a
diagram.
My administrator don't want me to use a domain account for services for
security reasons so, I'm going to use a workaround, e.g. use sa as owner
until this bug (?) is fixed.
Thank's anyway
Tommy
"Dan Guzman" wrote:
> My apologies but I misread your post. I guess I should a finished my coffee
> first :-)
> For your first issue, the database needs to be in 90 compatibility mode in
> order to create diagrams.
> Regarding your second problem, run the SQL Server Configuration utility to
> make sure the SQL Agent isn't running under the Network Service account.
> Use a domain account.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> > Thanks for your suggestion but it does not work.
> >
> > USE MyDatabase
> > EXEC sp_changedbowner 'HIK\Tommy'
> >
> > doesn't change anything.
> >
> > On the other hand it 's possible to change user to sa and everything works
> > OK, so it's my domain name that is the trouble. Have never had this
> > problem i
> > SQL Server 2K.
> >
> > /Tommy
> >
> > "Dan Guzman" wrote:
> >
> >> This might be due to a mismatch between the 'dbo' user mapping and the
> >> actual database owner. You can correct this with sp_changedbowner:
> >>
> >> USE MyDatabase
> >> EXEC sp_changedbowner 'HIK\Tommy'
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> >> > Hi!
> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
> >> > with
> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
> >> > group
> >> > on
> >> > my computer and there is a corresponding Windows login account with
> >> > sysadmin
> >> > permissions in SQL Server.
> >> >
> >> > I can do most things with that account, BUT when I try to create a
> >> > diagram
> >> > to a database. SQL does not like the owner of the database (my domain
> >> > account)
> >> >
> >> > This is the error message that show up:
> >> > "Database diagram support objects cannot be installed because this
> >> > database
> >> > does not have a valid owner. To continue, first use the Files page of
> >> > the
> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
> >> > the
> >> > database owner to a valid login, then add the database diagram support
> >> > objects."
> >> >
> >> > Again when I try to run a job that is owned by my domain account
> >> > (HIK\Tommy)
> >> >
> >> > Following message arise:
> >> >
> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> >> > MaintenancePlan2 has server access (reason: Could not obtain
> >> > information
> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
> >> > 42000]
> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
> >> > (Error
> >> > 3621))."
> >> >
> >> > I would be very grateful if you could come up with some suggestions.
> >> >
> >> > Regards
> >> > Tommy
> >>
> >>
> >>
>
>|||> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
The Books Online (Setting up Windows Accounts) states that it is best is to
use minimally privileged accounts for services. If you don't want to use a
low privilege domain user, you can use a (minimally privileged) local
Windows user account. I don't think this a a bug, it's just that SQL 2005
is more secure out-of-the-box so additional configuration work is needed to
loosen up security according to your organization's security policies.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:ED165CD9-5A84-4D4F-AC22-BF57C87A1A16@.microsoft.com...
> Using a domain account for the Agent and SQL Server service solves the
> problem with recognizeing job owner as my domain login (HIK\Tommy), but it
> still don't like my domain login as database owner when trying to create a
> diagram.
> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
> Thank's anyway
> Tommy
> "Dan Guzman" wrote:
>> My apologies but I misread your post. I guess I should a finished my
>> coffee
>> first :-)
>> For your first issue, the database needs to be in 90 compatibility mode
>> in
>> order to create diagrams.
>> Regarding your second problem, run the SQL Server Configuration utility
>> to
>> make sure the SQL Agent isn't running under the Network Service account.
>> Use a domain account.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
>> > Thanks for your suggestion but it does not work.
>> >
>> > USE MyDatabase
>> > EXEC sp_changedbowner 'HIK\Tommy'
>> >
>> > doesn't change anything.
>> >
>> > On the other hand it 's possible to change user to sa and everything
>> > works
>> > OK, so it's my domain name that is the trouble. Have never had this
>> > problem i
>> > SQL Server 2K.
>> >
>> > /Tommy
>> >
>> > "Dan Guzman" wrote:
>> >
>> >> This might be due to a mismatch between the 'dbo' user mapping and the
>> >> actual database owner. You can correct this with sp_changedbowner:
>> >>
>> >> USE MyDatabase
>> >> EXEC sp_changedbowner 'HIK\Tommy'
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Dan Guzman
>> >> SQL Server MVP
>> >>
>> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> >> > Hi!
>> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging
>> >> > in
>> >> > with
>> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> >> > group
>> >> > on
>> >> > my computer and there is a corresponding Windows login account with
>> >> > sysadmin
>> >> > permissions in SQL Server.
>> >> >
>> >> > I can do most things with that account, BUT when I try to create a
>> >> > diagram
>> >> > to a database. SQL does not like the owner of the database (my
>> >> > domain
>> >> > account)
>> >> >
>> >> > This is the error message that show up:
>> >> > "Database diagram support objects cannot be installed because this
>> >> > database
>> >> > does not have a valid owner. To continue, first use the Files page
>> >> > of
>> >> > the
>> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to
>> >> > set
>> >> > the
>> >> > database owner to a valid login, then add the database diagram
>> >> > support
>> >> > objects."
>> >> >
>> >> > Again when I try to run a job that is owned by my domain account
>> >> > (HIK\Tommy)
>> >> >
>> >> > Following message arise:
>> >> >
>> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of
>> >> > job
>> >> > MaintenancePlan2 has server access (reason: Could not obtain
>> >> > information
>> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> >> > 42000]
>> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> >> > (Error
>> >> > 3621))."
>> >> >
>> >> > I would be very grateful if you could come up with some suggestions.
>> >> >
>> >> > Regards
>> >> > Tommy
>> >>
>> >>
>> >>
>>
Showing posts with label wich. Show all posts
Showing posts with label wich. Show all posts
Sunday, March 11, 2012
Tuesday, February 14, 2012
Cannot connect to MSDE on SBS 2003
My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the isa server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?
Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
Cannot connect to MSDE on SBS 2003
My client has installed e scanner program wich is suposed til run on a MSDE
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
database. The program has to run on a reasently installed SBS 2003 server.
The server is installed with only standard features, the ISA server is not
installed. Clients are running in a standard 2003 domain.
The program is working fine on the server but clients cannot connect. I test
from Excel to make the test as basic as possible. The primary client is a
terminal server 2000 but trying from XP machines do not make any difference.
I get the following error fra Excel:
Connection failed:
SQLState: '01000'
SQL Server Error: 2
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Con
nect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL server does not
exist or
acces is denied.
To your infomation, the msde is the latest build and updates. The MDAC is
updatet on the terminalserver.
I suspect the SBS 2003 has shut down something somewhere but I have no clue
where to look. I am a total norvice in SQL.
I have checked the port 1433 an it is not "LISTENING" (nor 1434 if thats the
port) Shall it be Listening and if so, how do I get it to listen?Michael,
I had this exact problem on one of my SBS 2003 machines running MSDE.
Often 3rd party backup software like Veritas Backup Exec, attaches to
SQL/MSDE and modifies settings. Sometimes all communication protocols
are disabled.
To fix this, on the server run 'svrnetcn' and make sure that at least
one protocol is enabled. As you checked port 1433 I assume you want to
use TCP/IP, so ensure that at least TCP is in the 'Enabled Protocols'
section.
You also need to confirm that SQL is configured to communicate via this
protocol on the client machines. To do this, run 'cliconfg' on the
client machines. You will see a similar configuration tool to the
server. Make sure the 'Enabled Protocols' match the server, ie
confirm/add TCP.
Good luck, Al.
*** Sent via Developersdex http://www.codecomments.com ***
Subscribe to:
Posts (Atom)