I had entered this post, at home, without using the managed newsgroup
account - because I expected that someone would no what's going on.
After a couple of days, it looks like no one has any idea what I'm talking
about - should I re-post this under my managed newsgroup account that I have
with the MSDN Universal subscription? Because I kind of need a response.
[quoted text, click to view] "William Campbell" <NO_SPAM_AT_WILLIAM_CAMPBELL> wrote in message
news:%23XOobfp1EHA.2316@TK2MSFTNGP15.phx.gbl...
> In Enterprise Manager (EM), if you go to: [Replication Monitor ->
Agents ->
> Merge Agents] you'll see a list of Merge Agents to the right.
>
> I'd like to be able to select one of the items, right-click, and select
> "Agent Properties".
>
> When I do this, I get a dialog box that appears. The title of the dialog
is
> "Connect to SQL Server". It's looking for "Connection Information" and it
> wants a Login name and Password.
>
> Well, my SQL Server uses the sa user. So, I tried the sa user and it's
> password. Nope!
> The SQL Server Agent runs under a windows account. I tried that ID and
it's
> password. Nope!
>
> The other strange thing about this is that my friend doesn't have this
> problem on his laptop/SQL Server. He can view the agent properties no
> problem. One difference we can detect is that his SQL Server uses a
Windows
> Account and mine uses sa. Not sure if that makes a difference.
>
> I also went to [Security -> Logins] and added a new login and gave him
every
> available permission I could find (using the SQL Server Login Properties
> Tabbed Dialg). I tried logging on with this guy. Nope!
>
> So, sa doesn't work. The SQL Server Agent windows ID doesn't work. The
new
> Login guy didn't work. Ummm. What exactly is it looking for? But for
some
> reason, if I enter the ID and password I get the same MsgBox:
>
> ---------------------------
> SQL Server Enterprise Manager
> ---------------------------
> A connection could not be established to XXXX [3023].
>
> Reason: SQL Server does not exist or access denied.
> ConnectionOpen (Connect())..
>
> Please verify SQL Server is running and check your SQL Server registration
> properties (by right-clicking on the XXXX [3023] node) and try again.
>
> Thanks in advance,
> William Campbell
>
>