LogReader unable to connect to the publisher

I have a SQL2K box acting as Distributor and SQL7 box as a publisher. The
LogReader on the Distributor is unable to connect to the Publisher. I get the
following Msg from the Log Reader:
The process could not execute 'sp_MSadd_repl_commands27hp' on
'SQL2KServerName\InstanceName'
The two servers are on different untrusted domains. I am however able to
connect both ways through QA.
SQL2K box has SP4 and SQL7 box has SP3. Don't want to go to SP4 on SQL7
unless necessary and because it is a production server.
can you uncheck the Administrative Link Password requirement. Connect to
your distributor in EM, select Tools, Replication, Configure Distributor,
Publishers and Subscribers, and click on the Publishers tab. On the problem
publisher click on the browse button to the right of the publisher and you
will find this option at the bottom of the dialog box.
"Adam" <Adam@.discussions.microsoft.com> wrote in message
news:74DD5392-6B69-43B7-A591-4D80901F97D8@.microsoft.com...
>I have a SQL2K box acting as Distributor and SQL7 box as a publisher. The
> LogReader on the Distributor is unable to connect to the Publisher. I get
> the
> following Msg from the Log Reader:
> The process could not execute 'sp_MSadd_repl_commands27hp' on
> 'SQL2KServerName\InstanceName'
> The two servers are on different untrusted domains. I am however able to
> connect both ways through QA.
> SQL2K box has SP4 and SQL7 box has SP3. Don't want to go to SP4 on SQL7
> unless necessary and because it is a production server.
|||Thank you Hiary for the response. It turned out that the Distributor was
unable to resolve Publisher's IP address by name. Somehow, replacing the IP
address in the parameters for the log reader didn't work either. However,
after modifying the host file (for IP to name lookup) for distributor
resolved the problem.
-A
"Hilary Cotter" wrote:

> can you uncheck the Administrative Link Password requirement. Connect to
> your distributor in EM, select Tools, Replication, Configure Distributor,
> Publishers and Subscribers, and click on the Publishers tab. On the problem
> publisher click on the browse button to the right of the publisher and you
> will find this option at the bottom of the dialog box.
> "Adam" <Adam@.discussions.microsoft.com> wrote in message
> news:74DD5392-6B69-43B7-A591-4D80901F97D8@.microsoft.com...
>
>

Logon Error ?

The following error is logged in SQL Server 2005 Logfile. Could anyone
explain why this error is happening ?
Message
The server was unable to load the SSL provider library needed to log in; the
connection has been closed. SSL is used to encrypt either the login sequence
or all communications, depending on how the administrator has configured the
server. See Books Online for information on this error message: 0x6d.
[CLIENT: <named pipe>]Hi,
Have you installed an SSL certificate on the SQL Server?
If not then remove any configuration you may have on the server to force
encryption for connections (SQL Server Configuration Manager). You should
also remove any configuration on the client computers requiring them to
connect using encryption (SQL Native Client Configuration).
In BOL, please check
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e1e55519-97ec-4404-81ef-881d
a3b42006.htm
Nathan H. Omukwenyi
"swami" <swami@.discussions.microsoft.com> wrote in message
news:F4FC882D-DE26-4D8A-AACA-3DC7CF1C5F70@.microsoft.com...
> The following error is logged in SQL Server 2005 Logfile. Could anyone
> explain why this error is happening ?
> Message
> The server was unable to load the SSL provider library needed to log in;
> the
> connection has been closed. SSL is used to encrypt either the login
> sequence
> or all communications, depending on how the administrator has configured
> the
> server. See Books Online for information on this error message: 0x6d.
> [CLIENT: <named pipe>]|||As far as we can see - encryption is not set anywhere, either on the
server or client.
any other clues ?
"Nathan H. Omukwenyi" wrote:

> Hi,
> Have you installed an SSL certificate on the SQL Server?
> If not then remove any configuration you may have on the server to force
> encryption for connections (SQL Server Configuration Manager). You should
> also remove any configuration on the client computers requiring them to
> connect using encryption (SQL Native Client Configuration).
> In BOL, please check
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e1e55519-97ec-4404-81ef-88
1da3b42006.htm
> Nathan H. Omukwenyi
>
>
> "swami" <swami@.discussions.microsoft.com> wrote in message
> news:F4FC882D-DE26-4D8A-AACA-3DC7CF1C5F70@.microsoft.com...
>
>

Logon Error ?

The following error is logged in SQL Server 2005 Logfile. Could anyone
explain why this error is happening ?
Message
The server was unable to load the SSL provider library needed to log in; the
connection has been closed. SSL is used to encrypt either the login sequence
or all communications, depending on how the administrator has configured the
server. See Books Online for information on this error message: 0x6d.
[CLIENT: <named pipe>]Hi,
Have you installed an SSL certificate on the SQL Server?
If not then remove any configuration you may have on the server to force
encryption for connections (SQL Server Configuration Manager). You should
also remove any configuration on the client computers requiring them to
connect using encryption (SQL Native Client Configuration).
In BOL, please check
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e1e55519-97ec-4404-81ef-881da3b42006.htm
Nathan H. Omukwenyi
"swami" <swami@.discussions.microsoft.com> wrote in message
news:F4FC882D-DE26-4D8A-AACA-3DC7CF1C5F70@.microsoft.com...
> The following error is logged in SQL Server 2005 Logfile. Could anyone
> explain why this error is happening ?
> Message
> The server was unable to load the SSL provider library needed to log in;
> the
> connection has been closed. SSL is used to encrypt either the login
> sequence
> or all communications, depending on how the administrator has configured
> the
> server. See Books Online for information on this error message: 0x6d.
> [CLIENT: <named pipe>]|||As far as we can see - encryption is not set anywhere, either on the
server or client.
any other clues ?
"Nathan H. Omukwenyi" wrote:
> Hi,
> Have you installed an SSL certificate on the SQL Server?
> If not then remove any configuration you may have on the server to force
> encryption for connections (SQL Server Configuration Manager). You should
> also remove any configuration on the client computers requiring them to
> connect using encryption (SQL Native Client Configuration).
> In BOL, please check
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/e1e55519-97ec-4404-81ef-881da3b42006.htm
> Nathan H. Omukwenyi
>
>
> "swami" <swami@.discussions.microsoft.com> wrote in message
> news:F4FC882D-DE26-4D8A-AACA-3DC7CF1C5F70@.microsoft.com...
> > The following error is logged in SQL Server 2005 Logfile. Could anyone
> > explain why this error is happening ?
> >
> > Message
> > The server was unable to load the SSL provider library needed to log in;
> > the
> > connection has been closed. SSL is used to encrypt either the login
> > sequence
> > or all communications, depending on how the administrator has configured
> > the
> > server. See Books Online for information on this error message: 0x6d.
> > [CLIENT: <named pipe>]
>
>

Login succeeded followed by Logon Failed

We are experiencing some strange behaviour on SQL Server 2000. Certain
members of a domain group are unable to login. The error log says something
like
2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
Connection: Trusted.
2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
This is only affecting certain members of the group. (The SQL Server Error
msg says the user can not access their default database).Any suggestions as
to why this might be happening.stu,
If you are granting access to the server through domain groups rather that
to individual user accounts, then Accounts\Joe may be in several groups.
If he is in a group that has been assigned a default database to which he
does not have rights, then he _may_ fail to attach to his default database.
(Why won't everyone fail? Because they are not all members of the same
group and (as far as I have been able to discover) which group will provide
the default database for the user login is not deterministic.)
Actions:
1) Check to see if any Group Logins have a default database assignment to a
database in which they have no rights. If so, correct this.
2) Explicitly set the default database for the logins that are failing.
Even though all rights will still be granted through their group
memberships, the login account default database will have priority over any
group settings.
sp_defaultdb 'Accounts\Joe', 'GoodDefaultDB'
You do not have to create an Accounts\Joe login, but the sp_defaultdb will
create one for you in this case.
RLF
"stu" <stu@.discussions.microsoft.com> wrote in message
news:F8CDE8B3-B206-473A-94C5-F6A408B61064@.microsoft.com...
> We are experiencing some strange behaviour on SQL Server 2000. Certain
> members of a domain group are unable to login. The error log says
> something
> like
> 2007-04-27 08:45:14.33 logon Login succeeded for user 'Accounts\joe'.
> Connection: Trusted.
> 2007-04-27 08:45:14.33 logon Login failed for user 'Accounts\joe'.
> This is only affecting certain members of the group. (The SQL Server Error
> msg says the user can not access their default database).Any suggestions
> as
> to why this might be happening.

Login problems after publishing (sql express server)

Thanks for taking your time to read this.(sorry if someone posted this earlier but no solutions helped)

After i published my website, i am unable to login anymore. It has this error of "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed."

Note ** im using vb

This may cuased by the IIS account (5.0 is ASPNET and 6.0 is NT AUTHORITY\NETWORK SERVICE) used to connect to SQL is not allowed to generate the user instance. I'm sorry to say that I don't know how to give the permission to the account, maybe you can try to add the IIS account to local machine Administrators group. But I always use a workaround: remove the User Instance attribute from your connection string as I do not need it. To know more about connection string, you can visit this link:

http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring(d=ide).aspx