ForefrontUC event id 7 on Edge server
-
viernes, 26 de febrero de 2010 12:13Hi,
I have installed an OCSR2 Edge server some 9 months back.
In november I then added FSOSC.
All appear to work fine, except for this.
I see error event id 7 in the windows application log every 10 seconds.
There is no additional information about that error.
I have seen something similar when I used wrong IM notification credentials. But that also gave me a nice hint with another 10161 error.
This doesn't happen here. All seems fine except that event.
I have reinstalled FSOSC without any change.
Another edge server that was used for testing has the same error. Only difference is that its event id 9 on that one and that its not activation (and now expired).
Todas las respuestas
-
lunes, 01 de marzo de 2010 11:31
Opening 5061 to the vip of the pool where the FSOCS notification account was located change this. The Edge server only had 5061 opened to the vip for the directors. This obviously isn't enough for FSOCS.
I still need to get it verified that this is infact the problem due to some RFC delays on firewall changes. -
miércoles, 03 de marzo de 2010 13:03
This wasn't enough. Now the error 7 has changed to a Warning EventID 9 instead. Still the same source: ForefrontUC. What am I missing??
TIA -
miércoles, 07 de abril de 2010 8:43Bumping this one. I'm still wondering why this is happening.
-
viernes, 09 de abril de 2010 15:47
Hi Kent
Does it say anything more then only "Warning EventID 9"
// Tommy Clarke - Blog: http://www.cinline.se/ - Twitter: http://twitter.com/itommyclarke -
lunes, 19 de abril de 2010 16:32
I am getting the Source ForeFrontUC EventID 7 error after installing FCS for OCS. I havent changed anything since I seen this error..
Below is the complete error description:
The description for Event ID 7 from source ForefrontUC cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ForefrontUC
officecomm.mydomain.com
12.34.56.78
5061
10060
----------------------
Anyone help would be greatly appreciated
-
martes, 20 de abril de 2010 7:27
Hi Kent
Does it say anything more then only "Warning EventID 9"
// Tommy Clarke - Blog: http://www.cinline.se/ - Twitter: http://twitter.com/itommyclarke
Hi,That's all I get in the eventlog! As mentioned I got eventid 7 first. After opening 5061 to the pool from the edge server I now get eventid 9.
I also checked the ProgramLog.txt in the FSOCS's data folder. It writes "Failed to login." + "Error occured logging in to server 80EE00A6."
-
martes, 20 de abril de 2010 7:29
EventID 7 occured for me when I didn't have port 5061 open to the pool/FE servers. Try telnet the port and verify connectivity.
-
miércoles, 21 de abril de 2010 15:46
I reinstalled FSOCS, making sure that I had followed the prereq's and the errors went away for now.
The only difference between this install and the first was I added the account that I was installing the program with to the "RTCUniversalServerAdmins" group.
If the error returns.. Ill be back to post some more...
-
jueves, 21 de octubre de 2010 11:54
This was fixed by typing in the external FQDN of the access edge server (sip.domain.com:443). Note that you will need to add the portnumber aswell. Apparently the director is relaying the Forefront Notification Agent and is not doing a proxy. Thus the login failure.
- Marcado como respuesta -Kent- jueves, 21 de octubre de 2010 11:54
-
viernes, 22 de octubre de 2010 16:31
Hi Kent,
Where exactly did you enter the FQDN?
Thanks in advance.
Dan
.png)
