Re: Event 1287 MSExchangeSRS

Hi jremmc,

Thanks for posting here.

From the description, I understand the issue is that there is 1287
MSExchangeSRS event logged in the application log in Exchange 2003 server.
If I am off base, please don't hesitate to let me know.

Firstly please let me know if you are suffering any replications issue or
other issue between servers in the network. If not, you can safely ignore
the error event. If you prefer to trouble shoot the issue, I will try my
best to help to find the root cause of the issue. I appreciate your
understanding.

Technical speaking, the Lightweight Directory Access Protocol (LDAP) is
used to read from and write to Active Directory. By default, LDAP traffic
is transmitted unsecured. You can make LDAP traffic confidential and secure
by using Secure Sockets Layer (SSL) / Transport Layer Security (TLS)
technology.

For your current situation, please refer to the following article to double
check if the certificate is installed properly. And you have enabled the
LDAP over SSL successfully.

321051 How to Enable LDAP over SSL with a Third-Party Certification
Authority
http://support.microsoft.com/?id=321051

More information:
Description of the Server Authentication process during the SSL
http://support.microsoft.com/?id=257587

And also I suggest that you verify the following settings:

Step 1: Ensure the permissions on the Exchange 5.5 server:
=================================
1. On Exchange server 5.5, open Microsoft Exchange Administrator.

2. Click the organization, and click File -> Properties. On Permissions
tab, add w2k3\administrator as "service account admin".

3. Click the site, and click File -> Properties. On Permissions tab, add
w2k3\administrator as "service account admin".

4. Click configuration, and click File -> Properties. On Permissions tab,
add w2k3\administrator as "service account admin".

Step 2: Check the credential for services
=================================
1. On the Exchange 5.5 computer, open Control Panel, start Services
2. Click Microsoft Exchange Sytem Attendant service, and then click
Startup.
3. In the Log On As box, click This Account, and then enter the name of the
Exchange Service Account or an account that has Service Account
administrator rights on the Organization, Site, and Configuration
containers.
4. Retype the password and password confirmation.
5. Check all other Exchange related services.

More information:
288952 XADM: Error 2186 Occurs When You Start the Microsoft Exchange
http://support.microsoft.com/?id=288952

Step 3: Reboot the following services to see if it helps:
=================================
1. Please stop and then start the Exchange Directory Service.

2. Please stop and then start the MsexchangeSRS service.

3. Please stop and then start the ADC service.

4. Please run the Knowledge Consistency Checker:

Run the Exchange Knowledge Consistency Checker (KCC) on your Exchange 5.5
server. To run the KCC, perform the following steps:

a. Open the Exchange Server Administrator program, and connect to the
server.

b. Click to expand the Organization container, click to expand the Site
container, click to expand the Configuration container, and then click the
server object.

c. In the right pane, click the directory service icon and open the
properties.

d. On the General tab, click the Check Now button next to Check
knowledge consistency.

5. Please ensure point the Connection Agreements (Recipient CA and Public
CA ) in ADC to the SRS server. This is recommended method when there is SRS
server available in the environment.

You can refer to the following articles to do:

XGEN: How to Configure a Two-Way Recipient Connection Agreement for
Exchange Server 5.5 Users
http://support.microsoft.com/?id=296260

281223 Understanding Connection Agreements in Exchange
http://support.microsoft.com/?id=281223

Then please monitor the server to see if the event disappears.

=================================
If the issue persists, please help me collect the following information for
analyze:

1. Do you have any issues on your servers in the network? Please describe
more detail.

2. How many exchange server installed in your domain? What is your network
topology? Could you describe it for me?

3. Please increase the diagnostic logging level for MSExchangeSRS to max.
And collect exchange mps reports on all exchange servers.

- To increase the diagnostic logging and check the application log files.

a. Clear the current log files.
b. Start ESM, locate the Exchange server object.
c. Right click and then Properties.
d. On the Diagnostic logging tab, highlight MSExchangeSRS, and set all the
sub-categories level to Max.
e. Monitor the server till the event logged again. Then please mail the
application log to me.

- To collect Exchange MPS Report

1) Please download the MPSRPT_Exchange.EXE from the following link and then
run this tool to gather some information from the problematic computer:
http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f-
88b7-f9c79b7306c0&displaylang=en

2) Double-click on the MPSRPT_Exchange.EXE file.
[Note] This process may take some time; however, it will not have a
negative effect on the performance.

3) A CAB file will be generated in the
%systemroot%\MPSReports\Setup\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.

Please kindly send these log files to my working mailbox:
v-natliu@xxxxxxxxxxxxx

I appreciate your time. I am happy to be of assistance to you and look
forward to your reply.

Have a great day!

Sincerely,
Jenny Wu, MCSE 2000/2003, MCSA 2000/2003, MCDBA, MCSD
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--------------------
From: "Ed Crowley [MVP]" <curspice@xxxxxxxxxxxxxx>
References: <ekkZjac0GHA.1568@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: Event 1287 MSExchangeSRS
Date: Wed, 6 Sep 2006 22:55:56 -0700
Lines: 36
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
X-RFC2646: Format=Flowed; Response
Message-ID: <#V$YKJk0GHA.2196@xxxxxxxxxxxxxxxxxxxx>
Newsgroups: microsoft.public.exchange.admin
NNTP-Posting-Host: adsl-216-103-85-85.dsl.snfc21.pacbell.net 216.103.85.85
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.exchange.admin:567149
X-Tomcat-NG: microsoft.public.exchange.admin

My guess is that you're requiring SSL in a place where you shouldn't be.
--
Ed Crowley
MVP - Exchange
"Protecting the world from PSTs and brick backups!"

"jremmc" <jremmc@xxxxxxxxxxxxxx> wrote in message
news:ekkZjac0GHA.1568@xxxxxxxxxxxxxxxxxxxxxxx
We started getting this error Event ID 1287 from MSExchangeSRS

Unable to connect an LDAP SSL client due to an internal error. Verify
that
the SSL credentials are properly set up on this server.

about three weeks ago. That is extent of error message; no info as to
which/what client. I have no experience with this error. Search Technet,
Google turned up nothing other than the small blurb in MS Help & Support
link in error mesage. I'd be inlined to think that since SRS is throwing
the error it would relate to either E2K3 server or ADC server (which is
a
DC) or our branch 5.5 server. But none of the servers had an SSL
certificate when errors started, none would be trying to connect via SSL
to the other. Start of error "may" have coincided with a company wide
email that we were imminently installing an SSL certificate and someone
may have jumped the gun and configured their PC or phone for SSL early.
But then why would SRS be the reporting service?

We did install SSL (one of the big third-party) on E2K3 last week but
errors continue. Pretty sure SSL cert installed correctly, no issues
otherwise.

Any ideas, including how to track down client causing errors?

Thanks,
jremmc





.