samarchon
Active Member
I am doing the deployment server install of 8.9 and am running into this issue:
As part of the 8.9 install, I installed Planner ESU PF1954. For special instructions, now PeopleSoft supplies SpecialInstrs.bat batch file. When I double click this to apply it I get following errors in the SpecialInstrs.log:
***************************************************
Planner update PF1954 Special Instructions
***************************************************
Path to SpecialInstrs.bat: D:\B9DOWNLOADS\ESU\PF1954\SCRIPTS\SPECIALINSTRS.BAT
Msg 536, Level 16, State 3, Server BTS01PSD01\JDELOCAL, Procedure tempsp_special_instrs, Line 39
Invalid length parameter passed to the substring function.
Database name: PF1954
Attaching planner update database PF1954
Msg 15004, Level 16, State 1, Server BTS01PSD01\JDELOCAL, Procedure sp_attach_db, Line 26
Name cannot be NULL.
Error: Failed to attach database PF1954
Error: Failed to perform special instructions
************************************************
This is all happening on the deployment server.
Has anybody run into this issue before?
Thanks
As part of the 8.9 install, I installed Planner ESU PF1954. For special instructions, now PeopleSoft supplies SpecialInstrs.bat batch file. When I double click this to apply it I get following errors in the SpecialInstrs.log:
***************************************************
Planner update PF1954 Special Instructions
***************************************************
Path to SpecialInstrs.bat: D:\B9DOWNLOADS\ESU\PF1954\SCRIPTS\SPECIALINSTRS.BAT
Msg 536, Level 16, State 3, Server BTS01PSD01\JDELOCAL, Procedure tempsp_special_instrs, Line 39
Invalid length parameter passed to the substring function.
Database name: PF1954
Attaching planner update database PF1954
Msg 15004, Level 16, State 1, Server BTS01PSD01\JDELOCAL, Procedure sp_attach_db, Line 26
Name cannot be NULL.
Error: Failed to attach database PF1954
Error: Failed to perform special instructions
************************************************
This is all happening on the deployment server.
Has anybody run into this issue before?
Thanks