Server Error in /MonWebApp application

[EVSpinner]

Afternoon all, I need some direction on the following - I receive the following when trying to access EV Ops Manager

I've checked the following:

The Application pools node contains an EnterpriseVaultMonitoring application pool - it does

The Default Web Site node contains a MonitoringWebApp website - it does

I've confirmed that the folder MonitorringWebApp is present in the Enterprise Vault

installation folder, for example C:\Program Files\Enterprise Vault

I checked SQL for the EnterpriseVaultMonitoring account entry, and checked the credentials are valid for that account - they are

DTraced the following while replicating the error

1 - Admin Service

2 - agentclientbroker

6 - auth serevr

13 - directory service

Set 1 v

39 - ev monitoring

72 - monitoring agent

73 - MonitoringconfigUility

73 - MonitoringMiddleTiew

75 - MonitoringWebAppUtility

100 - w3wpset

Which gives me this:

543 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} Exception: The specified user is invalid Info: Diag: Type:System.ApplicationException ST:   at Symantec.EnterpriseVault.OperationsManager.WebAppConfigForm.ConfigureOperationsManagerWebApp(String userName, String domainName, String password) Inner:None
545 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} Configure Operations Manager Web App was done
547 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} Configuration status from End Invoke = InvalidUser
549 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} Updating UI of status by calling DisplayResultOfConfiguration
551 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} Configuration status = InvalidUser
553 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} NOT running on UI thread, Begin Invoking DisplayResultOfConfiguration
555 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} Enabling UI
556 14:12:38.024  [12572] (MonitoringWebAppConfig) <628> EV-M {Tracer.WriteLine} Configuration status = InvalidUser
559 14:12:38.024  [12572] (MonitoringWebAppConfig) <12452> EV-M {Tracer.WriteLine} NOT Running on UI thread, BeginInvoking the function
561 14:12:38.024  [12572] (MonitoringWebAppConfig) <628> EV-M {Tracer.WriteLine} Running on UI thread, enabling all UI control
562 14:12:38.774  [4040] (AdminService) <3996> EV:M CMonitor::Monitor([entity 1],[critical 95],[warning 90],[interval 0],[poll 0])|
563 14:12:38.774  [4040] (AdminService) <3996> EV:M CMonitor::MapEntryToObject - Entry Found in Map:[1] Mode:[1]|

So if I take the first line at face value, the root cause of this is that the username/credentials are wrong? Am I interpreting that correctly? I know for a fact the credentials and account name are correct, so if I have correctly identified the problem and I know the account name and password is correct, my question is....what do I do next?

Can anyone point me in the right direction, please?

[RahulG]

Did you perfrom any Upgrade? Was this working fine before?

[EVSpinner]

No upgrades have been performed on the server

This is the first time this [function] has been used, so I haven't been able to establish whether it ever worked (before my time)

[EVSpinner]

If the username and password being presented to MonWebApp is also the Vault Service Account, is that a problem?

[RahulG]

No I dont think it would be the issue, my guess would be some mismatch issue with the dll files . but as you mentioned you have not perfromed any upgrade that would not be true.

[A_J1]

Hi Bluesteel,

can you check whether you are getting an .Net realted events in the Application log..

[A_J1]

Hi Bluesteel,

Could you please let us know the EV Version ??

[A_J1]

Hi Bluesteel,

Do you still need any assistance on this post ???

[GabeV]

Hello bluesteel,

Since we don't know if the monitoring feature was working before, have you tried running the 'Operations Manager Web App Configuration' tool again? The config tool perform several changes where the user account is (1) added to the IIS_IUSRS group, (2) will be given access to the MonitoringWebApp folder and the Logs subfolder, (3) access to the ASP.NET Temporary Files Folder and (4) added to the Directory database as the monitoring user. Make sure you can run it without any errors and try to open the MonitoringWebApp again.

I hope this helps.

[EVSpinner]

Hi all, yes I'm still working on this

The verison is 10

I can't run the Config tool because it asks me to log in - the Monitoring user account SQL tells me to use fails. It's the same account found in the IIS_IUSRS group

 (4) added to the Directory database as the monitoring user - SQL says same account as present in IIS_IUSRS group

Points (2) and (3) - if it were permissions on folders not applied correctly, I'd be able to log into the Config interface, but I can't

Just to repeat, the account I log onto EV with, is the same account listed in IIS_IUSRS group, is the same account listed in SQL as added to the Directory database as the monitoring user

The fact I can log onto EV as this account means we know the account is good, but EV refuses to acknowledge withwer it's a valid account or  a valid password

A colleague did suggest that I delete the IIS virtual fodlers and try starting again just in case there is a corruption that is preventing the account for being correctly recognised - at least that way I could start again and open the config wizard

[Prone2Typos]

Sorry for the suggestion... but you should check out the following document:

http://www.symantec.com/business/support/index?page=content&id=TECH51287

IME 85% of all EVOM issues can be worked out by following it . It is one of the more bland... put you to sleep... how to fix your exciting EVOM failure... documents I have read in the exciting literature offered by SYMC for EV... but it has some fixes.

In digging for a more current version of the link I found this which points to it and has some other suggestions:

http://www.symantec.com/business/support/index?page=content&id=HOWTO57990

If this or other postings have helped to resolve your issues... please ensure you flag them as such. I dont thikn that we are there yet... but it never hurts to request..

Regards.

J

[EVSpinner · Accepted solution]

Hey TypoProne, thanks for jogging my memory on this. The case has been solved after a Symantec escalation, as follows:

'We have seen this before hand and it has been fixed by using the FQDN of the domain when running the MonitoringWeAppConfig.exe rather than the DNS name'

Worked like a charm - props to the chap who suggested this. Legend