elgwhoppo wrote:
[...] This is on the security server, the Blast Gateway Server service is paused and will not start. In event viewer, I see the following error circling in event viewer.
I've seen this happen when the Blast Secure Gateway tries to rotate (rename) its old logfiles to make way for a new one, but it is unable to do that because some program has one of the old logfiles locked. IIRC running 'more absg.log' in a command window is one way of getting into this situation. Look through your windows and make sure that you don't have any of the BSG logfiles (absg.log, absg.log.1 and so on) open in any of them.
We doublechecked to make sure that the certificate was friendly named vdm appropriately, but it doesn't look like the service won't start after reboot or re-install. Will post more detailed logs if inquiring minds are wondering.
If there was a problem with the cert then I'd expect to see some sort of diagnostic report in the BSG logfile. Do you see anything at all being written into the current logfile while this problem is happening? The BSG tries to write a few lines into the logfile on every startup, so if you see no new content at all in there then that would be another hint that there's a locking or access issue with the logfile.
The BSG logfiles are in C:\ProgramData\VMware\VDM\logs\Blast Secure Gateway by default. absg.log is the current logfile and older versions of it are rotated in the usual way, by appending a number that gets bumped higher each time a rotation is performed.
Mike.
--
Disclaimer: I work at VMware, but I do not speak for VMware.
