You should at least post the error message, and some information about your
environment.
-----
Regards
Anders Bengtsson
Microsoft MVP - MOM
http://www.contoso.se
s> What does this mean and what is the resolution
s>
SCOM is installed on a Windows 2003 server
SQL 2005 resides on the same server
All latest updates since mid October from Windows updates
I restarted servers after running windows updates and noted that the alerts
were not coming thru.
I have since been trying to troubleshoot the issue. I called MS Support and
I think it is worse than it was as they had me reseting a bunch of accounts
and now I ahve more issues than I had before.
Error calling ADsOpenObject in LDAP probe module Object:
LDAP://neagencies.corp Provider: LDAP Provider Error string: 8009030C:
LdapErr: DSID-0C09043E, comment: AcceptSecurityContext error, data 0, vece
Error code: -2146893044 HRESULT: 0x8007052e One or more workflows were
affected by this. Workflow name: NEA_BUF_MAN_1104_neagencies.corp Instance
name: buf-man-1104.neagencies.corp Instance ID:
{BECE3473-0E2B-E174-73E3-6183D8E4F74F} Management group: NorthEast Agencies
Path : buf-man-1104.neagencies.corp
Alert Rule : AD Agent Assignment: Unable to bind to Domain
Created : 10/31/2007 12:42:21 PM
Knowledge :
--------------------------------------------------------------------------------
Resolutions: No resolutions were found for this alert Causes: No knowledge
for causes was available for this alert
Summary: No summary was available for this problem
I dont reconize that issue, sorry. But try found more information in event
view logs. If you have reset accounts in AD you should update all account
in the console too.
-----
Regards
Anders Bengtsson
Microsoft MVP - MOM
http://www.contoso.se
s> Anders
s>
s> SCOM is installed on a Windows 2003 server
s> SQL 2005 resides on the same server
s> All latest updates since mid October from Windows updates
s> I restarted servers after running windows updates and noted that the
s> alerts were not coming thru.
s>
s> I have since been trying to troubleshoot the issue. I called MS
s> Support and I think it is worse than it was as they had me reseting a
s> bunch of accounts and now I ahve more issues than I had before.
s>
s> Error calling ADsOpenObject in LDAP probe module Object:
s> LDAP://neagencies.corp Provider: LDAP Provider Error string:
s> 8009030C: LdapErr: DSID-0C09043E, comment: AcceptSecurityContext
s> error, data 0, vece Error code: -2146893044 HRESULT: 0x8007052e One
s> or more workflows were affected by this. Workflow name:
s> NEA_BUF_MAN_1104_neagencies.corp Instance name:
s> buf-man-1104.neagencies.corp Instance ID:
s> {BECE3473-0E2B-E174-73E3-6183D8E4F74F} Management group: NorthEast
s> Agencies Path : buf-man-1104.neagencies.corp Alert Rule : AD Agent
s> Assignment: Unable to bind to Domain Created : 10/31/2007 12:42:21 PM
s>
s> Knowledge :
s>
s> ---------------------------------------------------------------------
s> -----------
s>
s> Resolutions: No resolutions were found for this alert Causes: No
s> knowledge for causes was available for this alert
s>
s> Summary: No summary was available for this problem
s>
s> "Anders Bengtsson" wrote:
s>
No problem, actually thats what MS said too. I think they are stumped as
they have not called me back in three days even thou I excualted the issue
several times.
Have a good one.
Seems everytime we install Windows updates we ahve issues. I only say that
because thats the last thing we did and now its broke.
I have several events. When I do a google search on each, I don't really
find anything significant. Seems as thou there isn't really much
documentation on this product, which makes troubleshooting it fustrating.
Seems strange with windows update, I have not seen any other threads about
that, there should be more posting about a windows update issue.
-----
Regards
Anders Bengtsson
Microsoft MVP - MOM
http://www.contoso.se
s> Anders
s>
s> No problem, actually thats what MS said too. I think they are
s> stumped as they have not called me back in three days even thou I
s> excualted the issue several times.
s>
s> Have a good one.
s>
s> Seems everytime we install Windows updates we ahve issues. I only
s> say that because thats the last thing we did and now its broke.
s>
s> I have several events. When I do a google search on each, I don't
s> really find anything significant. Seems as thou there isn't really
s> much documentation on this product, which makes troubleshooting it
s> fustrating.
Yes I would agree. I just can't think of anything else that changed.
Phil