Can't start replication agent

Hi,
I am using snapshot replication and want to create pull /
push replication but I always encountered same problem :
Login failed for user . . .
I think I had already set my user as an Administrator but
it didn't work.
Thanks in advance !
Michael Rawi
Michael,
in the subscriber database, right-click the distribution agent and select
properties.
On the security tab, choose to impersonate the SQL Server Agent.
You can change the service accounts to use the same domain user or have the
windows login of the subscriber's agent as a separate login on the
publisher.
HTH,
Paul Ibison
sql

Can't start a job that was created by user A from user B

Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
Johnny
Hi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
Adam J Warne, MCDBA
"Johnny" wrote:

> Hello all,
> I have a job I created with user A, but I need user B to be able to execute
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that the
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> were returned. So it appears that the view is filtering the results by user
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any help.
> Thanks!
> Johnny
>
|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:

Can't start a job that was created by user A from user B

Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
JohnnyHi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
--
Adam J Warne, MCDBA
"Johnny" wrote:

> Hello all,
> I have a job I created with user A, but I need user B to be able to execut
e
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with
an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that th
e
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'.
I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 ro
ws
> were returned. So it appears that the view is filtering the results by use
r
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any hel
p.
> Thanks!
> Johnny
>|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
[vbcol=seagreen]
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
>

Can't start a job that was created by user A from user B

Hello all,
I have a job I created with user A, but I need user B to be able to execute
this job programatically. I've given user B permission to EXECUTE the
"msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
error thrown. The following is the error I get when I run it with user B.
This error does not appear when I run it with user A.
The specified @.job_name ('MyJobName') does not exist.
After doing some research by looking at the system sprocs, I found that the
error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
researched that sproc and then found the system code that is throwing the
error, listed below.
-- Check if the job name is ambiguous
IF ((SELECT COUNT(*)
FROM msdb.dbo.sysjobs_view
WHERE (name = @.job_name)) > 1)
BEGIN
RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
@.name_of_name_parameter)
RETURN(1) -- Failure
END
I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
were returned. So it appears that the view is filtering the results by user
and the job is not found which is causing the error.
Do you guys know of a way I can make this work? I would appreciate any help.
Thanks!
JohnnyHi Johnny,
Only members of the sysadmin fixed role or the jobowner can start a job.
HTH
Adam
--
Adam J Warne, MCDBA
"Johnny" wrote:
> Hello all,
> I have a job I created with user A, but I need user B to be able to execute
> this job programatically. I've given user B permission to EXECUTE the
> "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> error thrown. The following is the error I get when I run it with user B.
> This error does not appear when I run it with user A.
> The specified @.job_name ('MyJobName') does not exist.
> After doing some research by looking at the system sprocs, I found that the
> error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> researched that sproc and then found the system code that is throwing the
> error, listed below.
> -- Check if the job name is ambiguous
> IF ((SELECT COUNT(*)
> FROM msdb.dbo.sysjobs_view
> WHERE (name = @.job_name)) > 1)
> BEGIN
> RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> @.name_of_name_parameter)
> RETURN(1) -- Failure
> END
>
> I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> were returned. So it appears that the view is filtering the results by user
> and the job is not found which is causing the error.
> Do you guys know of a way I can make this work? I would appreciate any help.
> Thanks!
> Johnny
>|||Thanks. I didnt want to do that but I guess I have no choice.
Johnny
"Adam Warne" wrote:
> Hi Johnny,
> Only members of the sysadmin fixed role or the jobowner can start a job.
> HTH
> Adam
> --
> Adam J Warne, MCDBA
>
> "Johnny" wrote:
> > Hello all,
> >
> > I have a job I created with user A, but I need user B to be able to execute
> > this job programatically. I've given user B permission to EXECUTE the
> > "msdb.dbo.sp_start_job" sproc and the user is able to execute it but with an
> > error thrown. The following is the error I get when I run it with user B.
> > This error does not appear when I run it with user A.
> >
> > The specified @.job_name ('MyJobName') does not exist.
> >
> > After doing some research by looking at the system sprocs, I found that the
> > error is thrown from a call made to 'msdb.dbo.sp_verify_job_identifiers'. I
> > researched that sproc and then found the system code that is throwing the
> > error, listed below.
> >
> > -- Check if the job name is ambiguous
> > IF ((SELECT COUNT(*)
> > FROM msdb.dbo.sysjobs_view
> > WHERE (name = @.job_name)) > 1)
> > BEGIN
> > RAISERROR(14293, -1, -1, @.job_name, @.name_of_id_parameter,
> > @.name_of_name_parameter)
> > RETURN(1) -- Failure
> > END
> >
> >
> > I performed a SELECT * query to the sysjobs_view view with user B and 0 rows
> > were returned. So it appears that the view is filtering the results by user
> > and the job is not found which is causing the error.
> >
> > Do you guys know of a way I can make this work? I would appreciate any help.
> > Thanks!
> >
> > Johnny
> >sql

Can't set the owner to the current login

I'm using express edition, compatibility set to 2005.

I'm logged in as DOMAIN\user, using windows authentication.

When I try to set the owner to this login, I get a "login does not exist on the server" error. Setting the owner to sa works fine.

Any fix to this problem ? Also - can I just work with the owner set to sa or can this cause problems in the future ?

Thanks.

If you could supply a little code that reproduces the error we could probably get an answer for you. What objects are you trying to own?

Yes, you can set the owner to sa, but then you have to work with the object as that login. It would be better to have that object owned by someone with only the rights that they absolutely need.

|||

The property that I'm trying to set is the database owner - in the database properties' files page. I need to do this in order to use diagrams, which are not available without a valid owner.

|||I see. Express doesn't allow diagrams.|||

Buck,

Thank you for trying to help.

The diagrams work fine - but the thing is that I have to set the owner to sa in order to work with them. The problem is that although I am logged in as DOMAIN\user, the server claims there is no such login when I try to set the database owner to that login.

|||

u may be login as Domain/User but in the database the user mapped to this login may be different .. check that...

SP_helpLogins 'Domian/Username' -- to get all the users mapped to this login

Madhu

|||

You know what - you're right! I was working on the older Express versions.

http://blogs.msdn.com/vsdata/archive/2004/09/30/236215.aspx

They have indeed put the diagrams back into Express.

Anyway, you seem to have a different issue, then. Have you tried putting the domain\user in the sysadmins group in SQL Server? I don't suggest leaving them there, but that might help you narrow the problem down. You only need to be in the db_owner role, but you can go high and bring the user account to that role later.

What message are you getting in the logs about this?

|||

I'm sorry, but I'm a newbie to sqlserver.

I guess I need to do some more reading before I can try to do these things (like putting the domain\user in the sysadmins group or using SP_helpLogins). I'm using Mannagement Studio Express and I can't find the correct way to do it.

sql

Can't seem to get ASP and SQL2000 to recognize the User IUSR_MachineName

Here is the connection string as in a ASP:
strConnect =3D "Provider=3DSQLOLEDB.1;User = ID=3DIUSER_MachineName;Trusted_Connection=3Dyes;Initial = Catalog=3Dmy_logon;" & _
"Network Library=3Ddbmssocn;Data Source=3DMyServer"
I have IUSR_MachineName as a User in the database and in Security for = Logins for the SQL 2000 SP3 server.
Since I don't know what the password is for the IUSR_MachineName account = I am assuming I could use TrustedConnection=3D"yes"
But this is not working. I keep getting:
Microsoft OLE DB Provider for SQL Server (0x80040E09)
SELECT permission denied on object 'Users', database 'my_logon', owner = 'dbo'.
In fact if I just use:
strConnect =3D "Provider=3DSQLOLEDB.1;Trusted_Connection=3Dyes;Initial = Catalog=3Dmy_logon;" & _
"Network Library=3Ddbmssocn;Data Source=3DMyServer"
I get the same error. The only way I can connect using ASP is using the = sa account or my Administrator account with the password. What am I = doing wrong and how can I get the account to be used to be the = IUSR_MachineName account given that IIS 5 (Windows 2000 Server SP3) = controls the password and I know not what it is? Thanks.
-- George Hester
__________________________________>>
Since I don't know what the password is for the IUSR_MachineName account I
am assuming I could use TrustedConnection="yes"
No, this won't work... you can't have a trusted connection *and* specify the
userid. You will need to do one of the following things:
(a) use a SQL Server user in your connection string.
(b) if you want to use a trusted connection, you will need to set up the
passwords correctly. The IUSR account on your web server is *only* on your
web server. The SQL Server machine has no idea who IUSR_webserver is, so
even if you add that user to SQL Server, the passwords won't synchronize.
In Windows 2000, I believe there was a setting in IIS to disable automatic
password synchronization for the IUSR account, and override the password.
Otherwise, you will have to change the password in password in
Administrative Tools / Computer Management / Local Users and Groups / Users.
Once the web server has a password for IUSR_webserver that you know, you can
do one of two things:
(i) use a connection string with *only* trusted connection=yes (no userid
information - see a sample at http://www.aspfaq.com/2126) and make sure that
windows authentication is disabled
(ii) add the same username/password as a SQL Server user, and include the
user id and password in the connection string (and remove the trusted
connection bit).
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Hi Aaron. Ok I see it won't work as I was hoping. Too bad I can't just =send the IIS generated password to SQL. That would make life so much =easier.
But one thing I am noticing. If I add my Windows logon account =MyDomain\Administrator to the logons for the SQL Server and for the =databases then I have for the logon of a database say Northwind =MyDomain\Administrator. I also have BUILTIN\Administrators for logon to =the SQL Server and in the databases.
If I go to Query Analyzer and choose SQL Authentication and type in =MyDomain\Administrator and my Windows 2000 SP3 Administrator password I =cannot connect. But if I choose Windows authentication then the account =which is used to logon to the SQL Server is MyDomain\Administrator.
This is confusing to me. Why when I try to login using Query Analyzer =using SQL authentication and the Login name MyDomain\Administrator I =cannot connect? But if I use Windows authentication the login name =shows as MyDomain\Administrator? This doesn't make sense to me.
It seems to me that all the Users that I have in my Users in Windows =2000 SP3 if I add them to SQL Server as it gives me the capability to, =then I cannot use those accounts to login to SQL 2000 SP3 Server. =Unless I have signed into Windows 2000 using one of those accounts. If =I have not signed into Windows 2000 SP3 using one of those accounts then =they are worthless to sign into SQL 2000 SP3. Thanks.
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:#57kO8dwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> >>
> Since I don't know what the password is for the IUSR_MachineName =account I
> am assuming I could use TrustedConnection=3D"yes"
> >>
> > No, this won't work... you can't have a trusted connection *and* =specify the
> userid. You will need to do one of the following things:
> > (a) use a SQL Server user in your connection string.
> > (b) if you want to use a trusted connection, you will need to set up =the
> passwords correctly. The IUSR account on your web server is *only* on =your
> web server. The SQL Server machine has no idea who IUSR_webserver is, =so
> even if you add that user to SQL Server, the passwords won't =synchronize.
> In Windows 2000, I believe there was a setting in IIS to disable =automatic
> password synchronization for the IUSR account, and override the =password.
> Otherwise, you will have to change the password in password in
> Administrative Tools / Computer Management / Local Users and Groups / =Users.
> > Once the web server has a password for IUSR_webserver that you know, =you can
> do one of two things:
> > (i) use a connection string with *only* trusted connection=3Dyes (no =userid
> information - see a sample at http://www.aspfaq.com/2126) and make =sure that
> windows authentication is disabled
> > (ii) add the same username/password as a SQL Server user, and include =the
> user id and password in the connection string (and remove the trusted
> connection bit).
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||On Sat, 13 Dec 2003 20:35:04 -0500, "George Hester"
<hesterloli@.hotmail.com> wrote:
>Hi Aaron. Ok I see it won't work as I was hoping. Too bad I can't just send the IIS generated password to SQL. That would make life so much easier.
>But one thing I am noticing. If I add my Windows logon account MyDomain\Administrator to the logons for the SQL Server and for the databases then I have for the logon of a database say Northwind MyDomain\Administrator. I also have BUILTIN\Administrators for logon to the SQL Server and in the databases.
>If I go to Query Analyzer and choose SQL Authentication and type in MyDomain\Administrator and my Windows 2000 SP3 Administrator password I cannot connect. But if I choose Windows authentication then the account which is used to logon to the SQL Server is MyDomain\Administrator.
>This is confusing to me. Why when I try to login using Query Analyzer using SQL authentication and the Login name MyDomain\Administrator I cannot connect? But if I use Windows authentication the login name shows as MyDomain\Administrator? This doesn't make sense to me.
>It seems to me that all the Users that I have in my Users in Windows 2000 SP3 if I add them to SQL Server as it gives me the capability to, then I cannot use those accounts to login to SQL 2000 SP3 Server. Unless I have signed into Windows 2000 using one of those accounts. If I have not signed into Windows 2000 SP3 using one of those accounts then they are worthless to sign into SQL 2000 SP3. Thanks.
Hi George,
You can achieve what you want if you change the security attributes on
your website to disallow Everyone and the anonymous user, and allow a
specific domain group, where that domain group includes the people you
have given access to SQL Server.
This will make IIS prompt the browser for authentication information. If
your users are using Internet Explorer and are logged into the domain,
then authentication will be transparent, otherwise they will be prompted
to enter their username and password.
They will then be authenticated in IIS as themselves, instead of the
anonymous user, and the secure connection to SQL Server will also be as
themselves.
cheers,
Ross.
--
Ross McKay, WebAware Pty Ltd
"Words can only hurt if you try to read them. Don't play their game" - Zoolander|||>> This is confusing to me. Why when I try to login using Query Analyzer
using SQL authentication and the Login name MyDomain\Administrator I cannot
connect?
Because this is not a SQL user! This is a Windows user! If you are logged
in as MyDomain\Administrator, use Windows Authentication. Otherwise, use a
SQL user account.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||> You can achieve what you want if you change the security attributes on
> your website to disallow Everyone and the anonymous user, and allow a
> specific domain group, where that domain group includes the people you
> have given access to SQL Server.
> This will make IIS prompt the browser for authentication information. If
> your users are using Internet Explorer and are logged into the domain,
> then authentication will be transparent, otherwise they will be prompted
> to enter their username and password.
> They will then be authenticated in IIS as themselves, instead of the
> anonymous user, and the secure connection to SQL Server will also be as
> themselves.
Great addition Ross.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||Aha finally. I got it from here:
http://support.microsoft.com/default.aspx?scid=3Dkb;en-us;247931&Product=3D=
sql
To use the IUSR_MachineName account and SQLOLEDB (note the missing .1) =I have to have "Integrated Security=3DSSPI" in the connection string. I =also have to have in SQL 2000 SP3 MyDomain\IUSR_MachineName have =db_datareader and db_datawriter access to the my_logon database. The =account must also have db_datareader and db_datawriter permissions to =the tempdb database. Also the account must be set up with Windows =Authentication which makes sense.
So the connection string is:
strConnect =3D "Provider=3DSQLOLEDB;Integrated Security=3DSSPI;Initial =Catalog=3Dmy_logon;" & _
"Network Library=3Ddbmssocn;Data Source=3DMySQLServer"
Now this article says "You must use one of the following two IIS =authentication methods:"
Actually I wanted to use the first method. Looks easier. But it was =not correct. I removed the Anonymous access and left only Basic =Authentication as the article suggests. I was returned a Domain logon =when I tried to access the web application. That I did not want. Also =the error was the AddHeader was insufficient information. Well that was =easy to fix. Just put back in the Anonymous account whose password is =handled by IIS.
That seems to have done it.
I can connect. Now to just finish with this article:
http://support.microsoft.com/?scid=3Dkb;en-us;299987
whew!!
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:#57kO8dwDHA.1764@.TK2MSFTNGP10.phx.gbl...
> >>
> Since I don't know what the password is for the IUSR_MachineName =account I
> am assuming I could use TrustedConnection=3D"yes"
> >>
> > No, this won't work... you can't have a trusted connection *and* =specify the
> userid. You will need to do one of the following things:
> > (a) use a SQL Server user in your connection string.
> > (b) if you want to use a trusted connection, you will need to set up =the
> passwords correctly. The IUSR account on your web server is *only* on =your
> web server. The SQL Server machine has no idea who IUSR_webserver is, =so
> even if you add that user to SQL Server, the passwords won't =synchronize.
> In Windows 2000, I believe there was a setting in IIS to disable =automatic
> password synchronization for the IUSR account, and override the =password.
> Otherwise, you will have to change the password in password in
> Administrative Tools / Computer Management / Local Users and Groups / =Users.
> > Once the web server has a password for IUSR_webserver that you know, =you can
> do one of two things:
> > (i) use a connection string with *only* trusted connection=3Dyes (no =userid
> information - see a sample at http://www.aspfaq.com/2126) and make =sure that
> windows authentication is disabled
> > (ii) add the same username/password as a SQL Server user, and include =the
> user id and password in the connection string (and remove the trusted
> connection bit).
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||Well I don't see why. SQL Manager clearly shows that =MyDomain\Administrator has login permissions. Well never mind. I got =it fixed. Thanks anyway.
-- George Hester
__________________________________
"Aaron Bertrand [MVP]" <aaron@.TRASHaspfaq.com> wrote in message =news:ezC#ycewDHA.1756@.TK2MSFTNGP09.phx.gbl...
> >> This is confusing to me. Why when I try to login using Query =Analyzer
> using SQL authentication and the Login name MyDomain\Administrator I =cannot
> connect?
> > Because this is not a SQL user! This is a Windows user! If you are =logged
> in as MyDomain\Administrator, use Windows Authentication. Otherwise, =use a
> SQL user account.
> > -- > Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
> >|||>> I have to have "Integrated Security=SSPI" in the connection string.
Yep, in my first reply:
http://www.aspfaq.com/2126
You can see this:
<snip>
Using Windows Authentication:
<%
cst = "Provider=SQLOLEDB.1;Data Source=<server/ip>;" & _
"Initial Catalog=<dbname>;Integrated Security=SSPI"
set conn = CreateObject("ADODB.Connection")
conn.open cst
%>
</snip>

can't see DB on SQL 2005 with SQL management studio

I am having a strange issue with SQL Management studio express. I can
log via the front end, but I do not see the DB for which this user is
"owner"
This is not the odd part. The odd part is that if I log in through a
3rd party front end such as EMS sql manager lite I do see the database
I own, and can manipulate it as I please. Can anyone suggest a reason
for this. Here are details of the setup just in case. The DB server
only has one DB other then the default system DB's. The owner of the db
I am having issue with has full permissions on the DB, but is not a
member of ANY server roles. There is a firewall on the machine but it
is allowing tcp connections on 1433. I have not set any connection
restrictions. The only major security change done on the server was to
use:
use master
Revoke View any database from public
go
AND
use *db I am working with*
Exec Sp_changedbowner ' *user that will own the db I am working with* '
Hi
Have you logged out/in since changing the owner of the database? Have you
tried to create a new database as that login, and can you see it? Have you
applied SP1?
John
"pr0f1t" wrote:

> I am having a strange issue with SQL Management studio express. I can
> log via the front end, but I do not see the DB for which this user is
> "owner"
> This is not the odd part. The odd part is that if I log in through a
> 3rd party front end such as EMS sql manager lite I do see the database
> I own, and can manipulate it as I please. Can anyone suggest a reason
> for this. Here are details of the setup just in case. The DB server
> only has one DB other then the default system DB's. The owner of the db
> I am having issue with has full permissions on the DB, but is not a
> member of ANY server roles. There is a firewall on the machine but it
> is allowing tcp connections on 1433. I have not set any connection
> restrictions. The only major security change done on the server was to
> use:
> use master
> Revoke View any database from public
> go
> AND
> use *db I am working with*
> Exec Sp_changedbowner ' *user that will own the db I am working with* '
>
|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you logged out/in since changing the owner of the database? Have you
> tried to create a new database as that login, and can you see it? Have you
> applied SP1?
> John
> "pr0f1t" wrote:
|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
|||Hi
That sounds like the change of ownership has not been reflected in the other
database. For the new database did you create the database as the login or
change the database to be owned by the login?
If you log in as a sysadm you should be able to see that database?
Try changing the owner again to a different login and then change it back.
If you run SELECT * FROM master.sys.databases what does it return?
Try regranting the VIEW ALL DATABASES to public and then just deny it to
specific logins.
What version of SQL 2005 are you using?
John
"pr0f1t" wrote:

> that is a fantastic suggestion. I don't knwo why I did not try this
> first. Yes the new DB is visible if I make this user owner. So why is
> the origional DB not visible if this user is owner of that as well? Any
> thoughts
>
> John Bell wrote:
>
|||*dbname*5NULL0xC1F615C4866765479D8B0AD5FD9FDEAA2006-10-31
14:53:43.06080SQL_Latin1_General_CP1_CI_AS0MULTI_USER0000ONLINE0000OFF03SIMPLE1TORN_PAGE_DETECTION1100000000000000000000009063F0BE-B2B1-4A45-9036-8775AAB1B47A00NOTHING0
is the result of SELECT * FROM master.sys.databases
I am running SQL Server 9.0.2047. I tried to change the ownership of
the DB but it only results in errors pretaining to object and schema
ownershipo, but I cannot seem to change the ownership to another user.
Ifs there a way to do this with TSQL? I have one user that essentially
needs to hve ownership of the DB, and access via a front end
porefereably Microsoft SQL managment studio express.
John Bell wrote:
|||Hi
Can you post the exact error number and message that occurs when you try to
change the owner? I assume you are using sp_changedbowner to do this?
Try creating a new user and changing the schema ownership to them
John
"pr0f1t" wrote:

> *dbname*5NULL0xC1F615C4866765479D8B0AD5FD9FDEAA2006-10-31
> 14:53:43.06080SQL_Latin1_General_CP1_CI_AS0MULTI_USER0000ONLINE0000OFF03SIMPLE1TORN_PAGE_DETECTION1100000000000000000000009063F0BE-B2B1-4A45-9036-8775AAB1B47A00NOTHING0
>
> is the result of SELECT * FROM master.sys.databases
> I am running SQL Server 9.0.2047. I tried to change the ownership of
> the DB but it only results in errors pretaining to object and schema
> ownershipo, but I cannot seem to change the ownership to another user.
> Ifs there a way to do this with TSQL? I have one user that essentially
> needs to hve ownership of the DB, and access via a front end
> porefereably Microsoft SQL managment studio express.
>
> John Bell wrote:
>

can't see DB on SQL 2005 with SQL management studio

I am having a strange issue with SQL Management studio express. I can
log via the front end, but I do not see the DB for which this user is
"owner"
This is not the odd part. The odd part is that if I log in through a
3rd party front end such as EMS sql manager lite I do see the database
I own, and can manipulate it as I please. Can anyone suggest a reason
for this. Here are details of the setup just in case. The DB server
only has one DB other then the default system DB's. The owner of the db
I am having issue with has full permissions on the DB, but is not a
member of ANY server roles. There is a firewall on the machine but it
is allowing tcp connections on 1433. I have not set any connection
restrictions. The only major security change done on the server was to
use:
use master
Revoke View any database from public
go
AND
use *db I am working with*
Exec Sp_changedbowner ' *user that will own the db I am working with* 'Hi
Have you logged out/in since changing the owner of the database? Have you
tried to create a new database as that login, and can you see it? Have you
applied SP1?
John
"pr0f1t" wrote:

> I am having a strange issue with SQL Management studio express. I can
> log via the front end, but I do not see the DB for which this user is
> "owner"
> This is not the odd part. The odd part is that if I log in through a
> 3rd party front end such as EMS sql manager lite I do see the database
> I own, and can manipulate it as I please. Can anyone suggest a reason
> for this. Here are details of the setup just in case. The DB server
> only has one DB other then the default system DB's. The owner of the db
> I am having issue with has full permissions on the DB, but is not a
> member of ANY server roles. There is a firewall on the machine but it
> is allowing tcp connections on 1433. I have not set any connection
> restrictions. The only major security change done on the server was to
> use:
> use master
> Revoke View any database from public
> go
> AND
> use *db I am working with*
> Exec Sp_changedbowner ' *user that will own the db I am working with* '
>|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
John Bell wrote:[vbcol=seagreen]
> Hi
> Have you logged out/in since changing the owner of the database? Have you
> tried to create a new database as that login, and can you see it? Have you
> applied SP1?
> John
> "pr0f1t" wrote:
>|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts|||Hi
That sounds like the change of ownership has not been reflected in the other
database. For the new database did you create the database as the login or
change the database to be owned by the login?
If you log in as a sysadm you should be able to see that database?
Try changing the owner again to a different login and then change it back.
If you run SELECT * FROM master.sys.databases what does it return?
Try regranting the VIEW ALL DATABASES to public and then just deny it to
specific logins.
What version of SQL 2005 are you using?
John
"pr0f1t" wrote:

> that is a fantastic suggestion. I don't knwo why I did not try this
> first. Yes the new DB is visible if I make this user owner. So why is
> the origional DB not visible if this user is owner of that as well? Any
> thoughts
>
> John Bell wrote:
>|||*dbname* 5 NULL 0xC1F615C4866765479D8B0A
D5FD9FDEAA 2006-10-31
14:53:43. 060 80 SQL_Latin1_General_CP1_CI_AS 0 MU
LTI_USER 0 0 0 0 ONLINE 0 0
0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECTIO
N 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
is the result of SELECT * FROM master.sys.databases
I am running SQL Server 9.0.2047. I tried to change the ownership of
the DB but it only results in errors pretaining to object and schema
ownershipo, but I cannot seem to change the ownership to another user.
Ifs there a way to do this with TSQL? I have one user that essentially
needs to hve ownership of the DB, and access via a front end
porefereably Microsoft SQL managment studio express.
John Bell wrote:|||Hi
Can you post the exact error number and message that occurs when you try to
change the owner? I assume you are using sp_changedbowner to do this?
Try creating a new user and changing the schema ownership to them
John
"pr0f1t" wrote:

> *dbname* 5 NULL 0xC1F615C4866765479D8B0A
D5FD9FDEAA 2006-10-31
> 14:53:43. 060 80 SQL_Latin1_General_CP1_CI_AS 0 MU
LTI_USER 0 0 0 0 ONLINE 0
0 0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECT
ION 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
>
> is the result of SELECT * FROM master.sys.databases
> I am running SQL Server 9.0.2047. I tried to change the ownership of
> the DB but it only results in errors pretaining to object and schema
> ownershipo, but I cannot seem to change the ownership to another user.
> Ifs there a way to do this with TSQL? I have one user that essentially
> needs to hve ownership of the DB, and access via a front end
> porefereably Microsoft SQL managment studio express.
>
> John Bell wrote:
>

can't see DB on SQL 2005 with SQL management studio

I am having a strange issue with SQL Management studio express. I can
log via the front end, but I do not see the DB for which this user is
"owner"
This is not the odd part. The odd part is that if I log in through a
3rd party front end such as EMS sql manager lite I do see the database
I own, and can manipulate it as I please. Can anyone suggest a reason
for this. Here are details of the setup just in case. The DB server
only has one DB other then the default system DB's. The owner of the db
I am having issue with has full permissions on the DB, but is not a
member of ANY server roles. There is a firewall on the machine but it
is allowing tcp connections on 1433. I have not set any connection
restrictions. The only major security change done on the server was to
use:
use master
Revoke View any database from public
go
AND
use *db I am working with*
Exec Sp_changedbowner ' *user that will own the db I am working with* 'Hi
Have you logged out/in since changing the owner of the database? Have you
tried to create a new database as that login, and can you see it? Have you
applied SP1?
John
"pr0f1t" wrote:
> I am having a strange issue with SQL Management studio express. I can
> log via the front end, but I do not see the DB for which this user is
> "owner"
> This is not the odd part. The odd part is that if I log in through a
> 3rd party front end such as EMS sql manager lite I do see the database
> I own, and can manipulate it as I please. Can anyone suggest a reason
> for this. Here are details of the setup just in case. The DB server
> only has one DB other then the default system DB's. The owner of the db
> I am having issue with has full permissions on the DB, but is not a
> member of ANY server roles. There is a firewall on the machine but it
> is allowing tcp connections on 1433. I have not set any connection
> restrictions. The only major security change done on the server was to
> use:
> use master
> Revoke View any database from public
> go
> AND
> use *db I am working with*
> Exec Sp_changedbowner ' *user that will own the db I am working with* '
>|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts
John Bell wrote:
> Hi
> Have you logged out/in since changing the owner of the database? Have you
> tried to create a new database as that login, and can you see it? Have you
> applied SP1?
> John
> "pr0f1t" wrote:
> > I am having a strange issue with SQL Management studio express. I can
> > log via the front end, but I do not see the DB for which this user is
> > "owner"
> > This is not the odd part. The odd part is that if I log in through a
> > 3rd party front end such as EMS sql manager lite I do see the database
> > I own, and can manipulate it as I please. Can anyone suggest a reason
> > for this. Here are details of the setup just in case. The DB server
> > only has one DB other then the default system DB's. The owner of the db
> > I am having issue with has full permissions on the DB, but is not a
> > member of ANY server roles. There is a firewall on the machine but it
> > is allowing tcp connections on 1433. I have not set any connection
> > restrictions. The only major security change done on the server was to
> > use:
> >
> > use master
> > Revoke View any database from public
> > go
> >
> > AND
> >
> > use *db I am working with*
> > Exec Sp_changedbowner ' *user that will own the db I am working with* '
> >
> >|||that is a fantastic suggestion. I don't knwo why I did not try this
first. Yes the new DB is visible if I make this user owner. So why is
the origional DB not visible if this user is owner of that as well? Any
thoughts|||Hi
That sounds like the change of ownership has not been reflected in the other
database. For the new database did you create the database as the login or
change the database to be owned by the login?
If you log in as a sysadm you should be able to see that database?
Try changing the owner again to a different login and then change it back.
If you run SELECT * FROM master.sys.databases what does it return?
Try regranting the VIEW ALL DATABASES to public and then just deny it to
specific logins.
What version of SQL 2005 are you using?
John
"pr0f1t" wrote:
> that is a fantastic suggestion. I don't knwo why I did not try this
> first. Yes the new DB is visible if I make this user owner. So why is
> the origional DB not visible if this user is owner of that as well? Any
> thoughts
>
> John Bell wrote:
> > Hi
> >
> > Have you logged out/in since changing the owner of the database? Have you
> > tried to create a new database as that login, and can you see it? Have you
> > applied SP1?
> >
> > John
> >
> > "pr0f1t" wrote:
> >
> > > I am having a strange issue with SQL Management studio express. I can
> > > log via the front end, but I do not see the DB for which this user is
> > > "owner"
> > > This is not the odd part. The odd part is that if I log in through a
> > > 3rd party front end such as EMS sql manager lite I do see the database
> > > I own, and can manipulate it as I please. Can anyone suggest a reason
> > > for this. Here are details of the setup just in case. The DB server
> > > only has one DB other then the default system DB's. The owner of the db
> > > I am having issue with has full permissions on the DB, but is not a
> > > member of ANY server roles. There is a firewall on the machine but it
> > > is allowing tcp connections on 1433. I have not set any connection
> > > restrictions. The only major security change done on the server was to
> > > use:
> > >
> > > use master
> > > Revoke View any database from public
> > > go
> > >
> > > AND
> > >
> > > use *db I am working with*
> > > Exec Sp_changedbowner ' *user that will own the db I am working with* '
> > >
> > >
>|||*dbname* 5 NULL 0xC1F615C4866765479D8B0AD5FD9FDEAA 2006-10-31
14:53:43.060 80 SQL_Latin1_General_CP1_CI_AS 0 MULTI_USER 0 0 0 0 ONLINE 0 0 0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECTION 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
is the result of SELECT * FROM master.sys.databases
I am running SQL Server 9.0.2047. I tried to change the ownership of
the DB but it only results in errors pretaining to object and schema
ownershipo, but I cannot seem to change the ownership to another user.
Ifs there a way to do this with TSQL? I have one user that essentially
needs to hve ownership of the DB, and access via a front end
porefereably Microsoft SQL managment studio express.
John Bell wrote:|||Hi
Can you post the exact error number and message that occurs when you try to
change the owner? I assume you are using sp_changedbowner to do this?
Try creating a new user and changing the schema ownership to them
John
"pr0f1t" wrote:
> *dbname* 5 NULL 0xC1F615C4866765479D8B0AD5FD9FDEAA 2006-10-31
> 14:53:43.060 80 SQL_Latin1_General_CP1_CI_AS 0 MULTI_USER 0 0 0 0 ONLINE 0 0 0 0 OFF 0 3 SIMPLE 1 TORN_PAGE_DETECTION 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9063F0BE-B2B1-4A45-9036-8775AAB1B47A 0 0 NOTHING 0
>
> is the result of SELECT * FROM master.sys.databases
> I am running SQL Server 9.0.2047. I tried to change the ownership of
> the DB but it only results in errors pretaining to object and schema
> ownershipo, but I cannot seem to change the ownership to another user.
> Ifs there a way to do this with TSQL? I have one user that essentially
> needs to hve ownership of the DB, and access via a front end
> porefereably Microsoft SQL managment studio express.
>
> John Bell wrote:
>

Cant see added columns in ASPNETDB.mdf

In developing a VWDE project I added 2 columns to the User table in the ASPNETDB.mdf database. I can see the columns in the Data Definition and I can see the values I added when I Show Table Data but I cannot access them with a SQLDataSource control? The SQLDataSource shows all of the columns in that table except the ones I added. Any suggestions? Thanks.Have you saved the changes to the table before you want to see them in the SqlDataSource?|||

Thank you for responding!

I have saved it, gone in and out of the application over several days and every time, when I look at it in the database explorer window, it shows the added columns and the added data but the SqlDataSource only shows the original columns. I deleted the first SqlDataSource and put in a new one and that didn't help. I know you can add tables to ASPNETDB.mdf but is there something that won't let you add columns to the tables used in the Membership tables (like users)?

Can't remove user from role

I have a user in a database role that I cannot remove from the role.
If I go into the user's properties and deselect the role, click OK,
then go back in, the role is still checked.
I've tried to remove them via sp_droprolemember without success.
I am able to add and drop the user from other roles, though, and I'm
able to add/drop other users to the same role.
How do I drop them from the role?
Using: SQL Server 2005 Enterprise
What error message did you get when you tried to remove it from the role?
Linchi
"cbtechlists@.gmail.com" wrote:

> I have a user in a database role that I cannot remove from the role.
> If I go into the user's properties and deselect the role, click OK,
> then go back in, the role is still checked.
> I've tried to remove them via sp_droprolemember without success.
> I am able to add and drop the user from other roles, though, and I'm
> able to add/drop other users to the same role.
> How do I drop them from the role?
> Using: SQL Server 2005 Enterprise
>
|||Hi Linchi:
I don't get an error. It appears to work successfully. But when I look
at the user's roles again, it's still there.
On Feb 12, 12:03Xpm, Linchi Shea
<LinchiS...@.discussions.microsoft.com> wrote:
> What error message did you get when you tried to remove it from the role?
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
>
>
> - Show quoted text -
|||How did you verify whether it's still there in the role? If you are using a
GUI tool, could this be a case of the GUI interface not being refreshed? I
know this may be too obvious, but...
Linchi
"cbtechlists@.gmail.com" wrote:

> Hi Linchi:
> I don't get an error. It appears to work successfully. But when I look
> at the user's roles again, it's still there.
>
> On Feb 12, 12:03 pm, Linchi Shea
> <LinchiS...@.discussions.microsoft.com> wrote:
>
|||If I use sp_helpuser 'theuser' I don't see the role listed.
If I open the properties of the user, the role is listed. I've
refreshed with the same results.
Weird
On Feb 12, 2:26Xpm, Linchi Shea <LinchiS...@.discussions.microsoft.com>
wrote:
> How did you verify whether it's still there in the role? If you are using a
> GUI tool, could this be a case of the GUI interface not being refreshed? I
> know this may be too obvious, but...
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
>
>
>
>
>
> - Show quoted text -

Can't remove user from role

I have a user in a database role that I cannot remove from the role.
If I go into the user's properties and deselect the role, click OK,
then go back in, the role is still checked.
I've tried to remove them via sp_droprolemember without success.
I am able to add and drop the user from other roles, though, and I'm
able to add/drop other users to the same role.
How do I drop them from the role?
Using: SQL Server 2005 EnterpriseWhat error message did you get when you tried to remove it from the role?
Linchi
"cbtechlists@.gmail.com" wrote:
> I have a user in a database role that I cannot remove from the role.
> If I go into the user's properties and deselect the role, click OK,
> then go back in, the role is still checked.
> I've tried to remove them via sp_droprolemember without success.
> I am able to add and drop the user from other roles, though, and I'm
> able to add/drop other users to the same role.
> How do I drop them from the role?
> Using: SQL Server 2005 Enterprise
>|||Hi Linchi:
I don't get an error. It appears to work successfully. But when I look
at the user's roles again, it's still there.
On Feb 12, 12:03=A0pm, Linchi Shea
<LinchiS...@.discussions.microsoft.com> wrote:
> What error message did you get when you tried to remove it from the role?
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
> > I have a user in a database role that I cannot remove from the role.
> > If I go into the user's properties and deselect the role, click OK,
> > then go back in, the role is still checked.
> > I've tried to remove them via sp_droprolemember without success.
> > I am able to add and drop the user from other roles, though, and I'm
> > able to add/drop other users to the same role.
> > How do I drop them from the role?
> > Using: SQL Server 2005 Enterprise- Hide quoted text -
> - Show quoted text -|||How did you verify whether it's still there in the role? If you are using a
GUI tool, could this be a case of the GUI interface not being refreshed? I
know this may be too obvious, but...
Linchi
"cbtechlists@.gmail.com" wrote:
> Hi Linchi:
> I don't get an error. It appears to work successfully. But when I look
> at the user's roles again, it's still there.
>
> On Feb 12, 12:03 pm, Linchi Shea
> <LinchiS...@.discussions.microsoft.com> wrote:
> > What error message did you get when you tried to remove it from the role?
> >
> > Linchi
> >
> >
> >
> > "cbtechli...@.gmail.com" wrote:
> > > I have a user in a database role that I cannot remove from the role.
> > > If I go into the user's properties and deselect the role, click OK,
> > > then go back in, the role is still checked.
> >
> > > I've tried to remove them via sp_droprolemember without success.
> >
> > > I am able to add and drop the user from other roles, though, and I'm
> > > able to add/drop other users to the same role.
> >
> > > How do I drop them from the role?
> >
> > > Using: SQL Server 2005 Enterprise- Hide quoted text -
> >
> > - Show quoted text -
>|||If I use sp_helpuser 'theuser' I don't see the role listed.
If I open the properties of the user, the role is listed. I've
refreshed with the same results.
Weird
On Feb 12, 2:26=A0pm, Linchi Shea <LinchiS...@.discussions.microsoft.com>
wrote:
> How did you verify whether it's still there in the role? If you are using =a
> GUI tool, could this be a case of the GUI interface not being refreshed? I=
> know this may be too obvious, but...
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
> > Hi Linchi:
> > I don't get an error. It appears to work successfully. But when I look
> > at the user's roles again, it's still there.
> > On Feb 12, 12:03 pm, Linchi Shea
> > <LinchiS...@.discussions.microsoft.com> wrote:
> > > What error message did you get when you tried to remove it from the ro=le?
> > > Linchi
> > > "cbtechli...@.gmail.com" wrote:
> > > > I have a user in a database role that I cannot remove from the role.=
> > > > If I go into the user's properties and deselect the role, click OK,
> > > > then go back in, the role is still checked.
> > > > I've tried to remove them via sp_droprolemember without success.
> > > > I am able to add and drop the user from other roles, though, and I'm=
> > > > able to add/drop other users to the same role.
> > > > How do I drop them from the role?
> > > > Using: SQL Server 2005 Enterprise- Hide quoted text -
> > > - Show quoted text -- Hide quoted text -
> - Show quoted text -

Can't register SSIS server in SMS...need permissions help.

I have a user who can't register the SSIS server in SMS. What permissions do I need to give him to allow this ... without making him sysadmin of course?

Check out the article by Kirk Haselden @. http://sqljunkies.com/WebLog/knight_reign/archive/2006/01/05/17769.aspx

Thanks,
Loonysan

|||

Yes, I found this online.

Unfortunately, after all this I'm still getting an error.

Could not get proxy data for proxy_id = 1

When I set up the credential, what kind of account should the "identity" be? SQL or Windows? What kind of permission should the "identity" have?

Cant pass 0 in stored procedure parameter

Hi
I have an if clause in my code to add the final parameter value to send to the database.

If Page.User.IsInRole("MICMS") Then
cmdCheckUser.Parameters.Add("@.C_ID", 0)
Else
cmdCheckUser.Parameters.Add("@.C_ID", Session("C_ID"))
End If

If the user is in the role, the error is triggered saying that @.C_IDis expected by the stored procedure. If i then change the value from 0to 10, the stored procedure works fine.
Is there any reason that the stored procedure is failing when the value 0 is used and not when any other value is used?
Thanking you in advance.Because the parameters.add is overridden based on what is passed (look at them when you hit the left parens). Since you are passing a numerical value of a low number, it thinks that it is the sqldbtype. You will need to cast the value to a string cStr(YOURVALUEHERE).
Nick

Can't open reports with Intranet user

Hi,
I made some reports and I deployed them on my local report server. I want
someone in the Intranet to be able to view them. I did set up the role to
make the intranet group to be able to browse my reports. They can view the
list of the report when they access it from http://server/ReportServer But
they just can't view it when they click on a report. It says they don't have
permissions to open ReportViewer.aspx.
I wonder why it is the problem.Ok I found the problem. The file ReportViewer.aspx didn't gave the
authorization to my Intranet group.

Can't manage SQL

I have a SQL Server running on a new W2k3 Server, and a user that received
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
Nuno
Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:

> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>
|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
[vbcol=seagreen]
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:

Can't manage SQL

I have a SQL Server running on a new W2k3 Server, and a user that received
the Sys Admin roles at this SQL Server. However, this user can't access this
SQL Server using the Service Manager nor stop/pause this server. The others
operations, suck as creating a new DB is ok for this group. Any help?
the error that i get is "error 5 (acess denied)"
thanks
NunoThe starting and stopping of a Server Service has nothing
to do with SQL and everything to do with the W2k3 roles.
So the problem here is your user does not have access
rights to stop the service as the W2k3 role will not let
them.
Have a chat to your server guys.
Peter
"Action speaks louder than words but not nearly as often"
Mark Twain
>--Original Message--
>I have a SQL Server running on a new W2k3 Server, and a
user that received
>the Sys Admin roles at this SQL Server. However, this
user can't access this
>SQL Server using the Service Manager nor stop/pause this
server. The others
>operations, suck as creating a new DB is ok for this
group. Any help?
>the error that i get is "error 5 (acess denied)"
>thanks
>Nuno
>.
>|||Hi,
To start any of the windows service user should be in Administrator or Power
user group. A login with SYSADMIN role can do
all the stuffs inside the SQL Server layer only not in Operating system side.
Note:
But the SQL Server Trusted users who fall in Admin group or power users
group can start and stop SQL server service.
Thanks
Hari
MCDBA
"Nuno" wrote:
> I have a SQL Server running on a new W2k3 Server, and a user that received
> the Sys Admin roles at this SQL Server. However, this user can't access this
> SQL Server using the Service Manager nor stop/pause this server. The others
> operations, suck as creating a new DB is ok for this group. Any help?
> the error that i get is "error 5 (acess denied)"
> thanks
> Nuno
>|||Without giving users total admin control to access (stop/start services) i
believe you can add the users to the print operators group. This would
achieve the results you are looking for.
"Hari Prasad" wrote:
> Hi,
> To start any of the windows service user should be in Administrator or Power
> user group. A login with SYSADMIN role can do
> all the stuffs inside the SQL Server layer only not in Operating system side.
> Note:
> But the SQL Server Trusted users who fall in Admin group or power users
> group can start and stop SQL server service.
> Thanks
> Hari
> MCDBA
> "Nuno" wrote:
> > I have a SQL Server running on a new W2k3 Server, and a user that received
> > the Sys Admin roles at this SQL Server. However, this user can't access this
> > SQL Server using the Service Manager nor stop/pause this server. The others
> > operations, suck as creating a new DB is ok for this group. Any help?
> >
> > the error that i get is "error 5 (acess denied)"
> >
> > thanks
> >
> > Nuno
> >

Can't make a new Login

Hi,
I have this problem:
When I create a new Login with a "SQL server authentication".
And if I change some User Mapping and Server Roles it gives me the follow
message "Create failed for User 'win2kadmin "
Server Name: SERVER\SERVER
Error Number: 15023
Severity: 16
State: 1
Line Number: 1
I will be gratful if you can help me,
--
Thanks ,
PeterThat error means the user, group, or role already exists. You will need to
drop the current user before creating the new one.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Pedro" <Pedro@.discussions.microsoft.com> wrote in message
news:34092E0F-DBB2-4DD4-BFE7-27E323E7A606@.microsoft.com...
> Hi,
> I have this problem:
> When I create a new Login with a "SQL server authentication".
> And if I change some User Mapping and Server Roles it gives me the follow
> message "Create failed for User 'win2kadmin "
> Server Name: SERVER\SERVER
> Error Number: 15023
> Severity: 16
> State: 1
> Line Number: 1
> I will be gratful if you can help me,
> --
> Thanks ,
> Peter

Can't login with windows user

Why I can't login to a SQL database with windows username and password (both
in OLE DB and ODBC).
If I try with trusted connection (or windows authentication) with the same
user works, but if I write by hand user name (domain\user) and password I
get "Error in initilizing provider". With SQL users works.
Hi,
For trusted connection you are not supposed to specify the user name and
password.
A single login to Operating system will give you access to SQL Server as
well. All you need is to click the "Windows Authentication" and click OK.
This will allow you to access the SQl Server with the credentials of
currently logged in OS user.
User name and password needs to be provided only for SQL server based
logins.
Thanks
Hari
MCDBA
"Sorin Sandu" <ssandu@.bizland.ro.invalid> wrote in message
news:O8x4qMSSEHA.3812@.TK2MSFTNGP11.phx.gbl...
> Why I can't login to a SQL database with windows username and password
(both
> in OLE DB and ODBC).
> If I try with trusted connection (or windows authentication) with the same
> user works, but if I write by hand user name (domain\user) and password I
> get "Error in initilizing provider". With SQL users works.
>
|||But I don't want to access the SQl Server with the credentials of
currently logged in OS user. I need another windows user. Windows not SQL
|||Hi,
We cant enter the user name for the windows based user. A single login to OS
will allow allow to login to sql server.
But you could try this:-
1. Map the network (network mapping) to the SQL server using the Windows
user you need to connect to sql server (This user should have rights in sql
server)
2. Now using query analyzer try to connect.
This uses the mapped users security context to login inside sql server
Thanks
Hari
MCDBA
"Sorin Sandu" <ssandu@.bizland.ro.invalid> wrote in message
news:OZcYjreSEHA.644@.tk2msftngp13.phx.gbl...
> But I don't want to access the SQl Server with the credentials of
> currently logged in OS user. I need another windows user. Windows not SQL
>
|||Hi
Please what do you mean by map the network (network mapping) ?
|||Mapping a network drive is to create a namesake, say "J" drive which is
actually pointing to a share across your network, like \\shared1\sqlfiles.
To do so, open Windows explorer, go to the Tools menu, you'll find "Map
network drive" as the 1st option. That option gives you the drive 'letter'
you want to choose, as well as the "folder" which is the network share. You
will of course have to be using a domain account, and that should have
necessary permissions to access that shared folder.
Hope that helps!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

Can't login with windows user

Why I can't login to a SQL database with windows username and password (both
in OLE DB and ODBC).
If I try with trusted connection (or windows authentication) with the same
user works, but if I write by hand user name (domain\user) and password I
get "Error in initilizing provider". With SQL users works.Hi,
For trusted connection you are not supposed to specify the user name and
password.
A single login to Operating system will give you access to SQL Server as
well. All you need is to click the "Windows Authentication" and click OK.
This will allow you to access the SQl Server with the credentials of
currently logged in OS user.
User name and password needs to be provided only for SQL server based
logins.
Thanks
Hari
MCDBA
"Sorin Sandu" <ssandu@.bizland.ro.invalid> wrote in message
news:O8x4qMSSEHA.3812@.TK2MSFTNGP11.phx.gbl...
> Why I can't login to a SQL database with windows username and password
(both
> in OLE DB and ODBC).
> If I try with trusted connection (or windows authentication) with the same
> user works, but if I write by hand user name (domain\user) and password I
> get "Error in initilizing provider". With SQL users works.
>|||But I don't want to access the SQl Server with the credentials of
currently logged in OS user. I need another windows user. Windows not SQL|||Hi,
We cant enter the user name for the windows based user. A single login to OS
will allow allow to login to sql server.
But you could try this:-
1. Map the network (network mapping) to the SQL server using the Windows
user you need to connect to sql server (This user should have rights in sql
server)
2. Now using query analyzer try to connect.
This uses the mapped users security context to login inside sql server
Thanks
Hari
MCDBA
"Sorin Sandu" <ssandu@.bizland.ro.invalid> wrote in message
news:OZcYjreSEHA.644@.tk2msftngp13.phx.gbl...
> But I don't want to access the SQl Server with the credentials of
> currently logged in OS user. I need another windows user. Windows not SQL
>|||Hi
Please what do you mean by map the network (network mapping) ?|||Mapping a network drive is to create a namesake, say "J" drive which is
actually pointing to a share across your network, like \\shared1\sqlfiles.
To do so, open Windows explorer, go to the Tools menu, you'll find "Map
network drive" as the 1st option. That option gives you the drive 'letter'
you want to choose, as well as the "folder" which is the network share. You
will of course have to be using a domain account, and that should have
necessary permissions to access that shared folder.
Hope that helps!
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.