Re: Can't view merge agent properties (trying again)

From: MSDN-Managed (MSDN-Managed_at_nospam.nospam)
Date: 12/23/04 

Date: Thu, 23 Dec 2004 12:30:36 -0500

In the List of Actions for the Snapshot Agent History I see this repeated:

#Actions: 110
Last Action Message of Session: A snapshot of 26 article(s) was generated.
Start Time: Vaires for each record in that list
Time of Last Action: Again, varies
Duration (secs): Varies - I see a range of: 00:00:50 to 00:01:23
Delivery Rate (cmds/sec): 0.0000
# Trans: 1
# Cmds: 0

As for the "Logins" information you provided:

before I came here and posted my question a month or so ago ... I was
playing around with the users under "Logins".

* I had added the login id: computername\IUSR_computername
* I went to the Server Roles tab and checked the check box for EVERY Server
Role
* I went to the Database Access tab and checked the "permit" checkbox for
every single database listed.
*Also, for each database I "permitted", I went to the list box below it and
checked every signle Database role you could .. for every database.

computername\IUSR_computername was a super-duper user! He had every single
checkbox I could check, checked!

So, just now, I went to computername\Administrator Login ID (because it's
.\Administrator that is the user for the SQLSERVERAGENT Service) - and
that's what step 3 of your instructions suggest.
And I right-clicked and selected properties.

Then, per step 4, I went to the Database Access tab. I found the Name of
the database and I clicked the "Permit" checkbox next to the name of the
database I currently have set up for replication. As soon as you click the
permit tab, it automatically fills in the name of the Login ID .. in this
case, it filled in "Administrator". Well, I went into the edit box and
changed it to: computername\ISUR_computername. It complained of invalid
characters .. so I changed it to IUSR_computername. It then presented this
MessageBox:

Microsoft SQL-DMO
Error 21002: [SQL-DMO]User 'IUSR_COMPUTERNAME' already exists.

So, that's probably because of the ISUR_computername Login I had previously
set up .. the 'super-duper' one.

So, I just left it as 'Administrator' as the user for the database (after
checking permit).

Anyhow, maybe I misunderstood the directions .. because there were parts
that were vauge and could be easily misunderstood .... but as you can see, I
have given a whole boat-load of rights to many different users/logins.

Still...the issue exists. This is why I posted here to the newsgroups in
the first place. I'm not someone that posts to newsgroups for every inane
question they can think of. I've thouroughly tried every thing I can think
of ... including google searches on newsgroups and the microsoft websites.
Nothing. And I still have this issue.

What next?
William Campbell

"Michael Cheng [MSFT]" <v-mingqc@online.microsoft.com> wrote in message
news:Sm9HDwL6EHA.3696@cpmsftngxa10.phx.gbl...
> Hi William,
>
> Thanks for the detailed information!!
>
> Expand the Agent, go to Snapshot Agent, right click the Publication name,
> select Agent History.
> In the Pop-up Snapshot Agent History, check the Actions and it's status.
> Any information there? Paste them here for further troubleshooting.
>
> Secondly, please make sure the account for Merge Agent has full
> permissions. In SQL CE Books Online, we could find the following
> information about how to
>
> =========
> 1. On the computer running SQL Server, start SQL Server Enterprise
Manager:
> On the Start menu, point to Programs, Microsoft SQL Server, and then click
> Enterprise Manager.
> 2. In the console tree, expand Microsoft SQL Servers, SQL Server Group,
the
> computer containing the publication, and Security; and then click Logins.
> 3. In the details pane, right-click the user ID under which the Merge
Agent
> executes, and then click Properties. The user ID of the Merge Agent
depends
> on how you configured IIS and SQL Server authentication.
>
> IIS authentication mode SQL Server authentication mode Must grant database
> access to
> Anonymous access Windows authentication computername\IUSR_computername
or
> the configured IIS anonymous user account.
> 4. Click the Database Access tab, and then select the Permit check box for
> the database.
> =========
>
> Thank you for your patience and corporation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
>
> Sincerely yours,
>
> Michael Cheng
>
> Online Partner Support Specialist
> Partner Support Group
> Microsoft Global Technical Support Center
> ---------------------------------------------------------------
> Get Secure! - http://www.microsoft.com/security
>
> This posting is provided "as is" with no warranties and confers no rights.
> Please reply to newsgroups only, many thanks!
>

Relevant Pages

  • Re: System Administrator Implied Permissions
    ... > sa login, it assigns it the System Administrator fixed ... > Now, given this, why does SQL Server ... in each database is always a member of the public and db_owner roles. ... Other sysadmin role members have the exact same ...
    (microsoft.public.sqlserver.security)
  • Re: No db access after publishing web site
    ... GRANT UPDATE TO ... If I detach and attach this database on a different PC (according that PC ... Cannot open database "pago" requested by the login. ... Are you detaching/attaching the SQL Server Express database correctly ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: cannot login to the db after...
    ... Jasper Smith (SQL Server MVP) ... I have created a new database, "db_1", using the "sa" ... I then created a new login, "sqluser1" and gave ...
    (microsoft.public.sqlserver.security)
  • Re: Database security design with ASP.net and form-based authentication
    ... Since you already have forms-based security, why not use a single SQL login ... for all database access? ... data entry, guest/view only, admin, report viewer. ... so I'm using SQL Server authentication. ...
    (microsoft.public.sqlserver.security)
  • RE: SQL Server Errorlog login Failure
    ... the login error. ... If your replication agents are proper, ... agent startup account etc to resolve it. ... ||I have an Windows account that runs all my SQL Server ...
    (microsoft.public.sqlserver.replication)