Wednesday, December 25, 2013

Stuck in WinPE when converting P2V

In this case I got stuck in WinPE when I was converting physical server with installed Windows Server 2003 R2 SP2 operating system using VMM 2012 SP1 P2V method for creation of virtual machines. P2V process has successfully started, and source physical server has started into WinPE, but copying of source hard drive never started because of missing RAID drivers. So, now I was stuck into WinPE. Restarting the physical server was booting again into WinPE because P2V conversion was unable to finish, so modified boot sector was still in place.
Escaping from this (loop) situation was using installation media of Windows Server 2003, and booting into recovery console. Using fixboot has returned the default boot sector to the system partition, and I was able to boot again into source Windows Server 2003 R2 SP2 operating system.

Friday, December 20, 2013

End of socket stream data on Lotus Protector for Mail Security

In this case I was experiencing very strange behavior of Lotus Protector for Mail Security with latest firmware 2.8.1, some emails sent to specific domains were successfully delivered, but from some reason LPfMS was treating those emails as unsuccessfully delivered and were parked into resend queue. The sender was receiving report for temporary delivery error and after few hours a report that maximum number of delivery attempts has been reached, even though the email was successfully received by the email recipient ! Smtp server on LPfMS is based on XMail smtp server.
Following error was logged for those emails:
"End of socket stream data (2) No such file or directory - 417 Temporary delivery error"

I have opened a case for this kind of behavior, and the support engineer has recommended to change the time out value for LPfMS to send the command and to wait for getting the response back from the foreign SMTP server. The default value is 30 seconds. After raising the time out value, this strange behavior of LPfMS was gone. This parameter is smtp.send_dialog_timeoutms and can be set on Mail Security -> Policy -> Advanced Parameters. The parameter is accepting values in milliseconds.