Saturday, 10 February 2007

Caution - Problem with Windows maximum path length and WebSphere Portal node name

Hi

Learn from my mistake

If your nodename is 8 characters or longer, you may get this exception: -

2007-02-08T11:42:00Z Result: [wsadmin] java.io.IOException: java.io.IOException: The system cannot find the specified file, either the filename is too long on Windows system or run out of file descriptor on UNIX platform. java.io.FileNotFoundException: D:\ibm\WebSphere\profiles\wp_profile\wstemp\Script110a1279556\workspace\cells\stargate\applications\BPEContainer_stargate_WebSphere_Portal.ear\deployments\BPEContainer_stargate_WebSphere_Portal\compensate_ejb.jar\META-INF\ibm-ejb-jar-ext-pme.xmi.workspace_save (The system cannot find the file specified)

This is because the nodename pushes the length of the path out to 261 characters, which exceeeds the Windows 256 character limit: -

D:\ibm\WebSphere\profiles\wp_profile\wstemp\Script110a1279556\workspace\cells\stargate\applications\BPEContainer_stargate_WebSphere_Portal.ear\deployments\BPEContainer_stargate_WebSphere_Portal\compensate_ejb.jar\META-INF\ibm-ejb-jar-ext-pme.xmi.workspace_save

I'm using Windows 2000 Server SP4.

Hope this helps.


Dave


2 comments:

John Frag said...

I would recommend you to try Long Path Tool program to fix this problem

Dave Hay said...

Thanks John