Storage Resource Manager Enterprise Edition Installation Guide

C–32 Storage Resource Manager Enterprise Edition
SRM Troubleshooting Guide
• MessageId=210
Main buffered - no connection to pipe <path>, giving up.
SRM never came back to pick up scan results, because SRM service was stopped.
• MessageId=260
Scan to pipe - could not create buffer file for pipe <path> - error <LastError>
Unable to create the temporary file to buffer data in. The <LastError> value
should provide a reason for lack of creation. This would probably be a disk space
or permissions error.
• MessageId=270
Scan to pipe - could not create buffered scan process for pipe <path> - error
<LastError>.
CreateProcess() call failed.
• MessageId=280
Scan to pipe - could not create pipe <path> for buffered scan parameters - error
<LastError>.
CreateNamedPipe() call failed.
• MessageId=290
Scan to pipe - no connection to pipe <path> for buffered scan parameters, giving
up.
No connection was made to the pipe (from the CGI script to the process started via
CreateProcess()) during the configured timeout period.
The following error messages listed in Table C–2 are self-explanatory (and should be
quite rare, based on unexpected returns from Win32 calls), or at least give a clue to
engineering what is happening:
Table C–2: Error Messages
Message Text
60 Scan to pipe - could not read stdin for pipe <path> - error
<LastError>.
70 Filters from pipe - could not create pipe <path> - error <LastError>.
80 Filters from pipe - no connection to pipe <path>, giving up.
90 Filters from pipe - connectNamedPipe <path> returned error
<LastError>.