premature eof encountered(233)

[o1crimson1o]

NB 8.1, I'm trying to create a new Storage Lifecycle but everytime I get premature eof encountered(233).

I've dug thru logs (I'm not 100% positive which log I should dig thru tho).

0,51216,132,132,940,1512512425508,3760,139751625520896,0:,93:Returning SLPValidationInfoSeq length:0Error code:233(StorageServiceControlFacetImpl.cpp:127),45:StorageServiceControlFacetImpl::validateSLP#1,1
0,51216,132,132,941,1512512425509,3760,139751625520896,0:,96:NB error code: 233 NB localized Error text: premature eof encountered(NBUErrorTranslator.cpp:47),37:NBUErrorTranslator::getErrorDetails(),1
0,51216,132,132,942,1512512425509,3760,139751625520896,0:,184:Error:StorageServiceControlFacetImpl::validateSLP#1:../StorageServiceControlFacetImpl.cpp(156): errNo:233 localizedStr:premature eof encountered additionalStr:(ExceptionManager.cpp:97),39:ExceptionManager::fillExceptionObject(),1
0,51216,132,132,943,1512512425509,3760,139751625520896,0:,63:Exception name:NBSLOpException(CORBAExceptionTranslator.cpp:47),43:CORBAExceptionTranslator::getErrorDetails(),1
0,51216,132,132,944,1512512425509,3760,139751625520896,0:,69:Rethrowing NBSLOpException exception(CORBAExceptionTranslator.cpp:85),43:CORBAExceptionTranslator::getErrorDetails(),1

I've tried even changing the volume pool an an older working SLP and got the same error message.

[Systems_Team]

Hi 01crimson10,

You haven't mentioned what you have named your SLP, but is it SLP#1 by any chance (I notice this in several locations in your log snippet)?  I'm wondering if the # might be causing issues.  The allowed characters from the NetBackup Naming Conventions are:

• Alphabetic (A-Z a-z) (names are case-sensitive)
• Numeric (0-9)
• Period (.)
• Plus (+)
• Minus (-)
• Do not use a minus as the first character
• Underscore (_)

This doesn't explain the issue with you trying to change an older SLP (unless that also has character that is not allowed), but worth a check.

Hope this helps,

Steve

[o1crimson1o]

Here is a SS of the SLP names, I believe I am gollowing the proper conventions.

[o1crimson1o]

I even went as far as deleting ALL the SLPs and trierd remaking one. And it still gives me the same error.

[Marianne]

@o1crimson1o

Probably time to log a Support call.

My guess is that some file got corrupted and we are not going to find it here.

Veritas engineers will request highest possible logging levels (remember to watch space!) and should be able to trace the issue.

Please remember to come back and tell us.