8.3 Directory Support in Windows 2003
Hello,
Did anyone packaged USD (UniCenter Service Desk)?
I have a problem. Package seems to be ok on my test VM but it fails on Production servers.
I noticed this. This is a 16 bit app that works with 8.3 directory structure. There is a INI file (PARADIGM.INI) under user profile\Windows folder that reads like this:
[PARADIGM]
NX_ROOT=C:/PROGRA~1/CA/UNICEN~1/SERVIC~1
NX_LOCAL=C:/PROGRA~1/CA/UNICEN~1/SERVIC~1
NX_OS_TYPE=WINNT
When you launch the "Windows Client" shortcut, app load JAVA, and runs HELPDESK.JAR file. This is failing in PROD servers because Production server are not supporting 8.3 dir structure. Even if you change the INI file with "C:\Program Files\CA\Unicenter\Service Desk", still you cannot launch the short cut because I guess the EXE is hard coded to look for
C:/PROGRA~1/CA/UNICEN~1/SERVIC~1.
I also changed the below registry setting to "0".
HKLM\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation
Still it doesn't work.
Also I noticed this:
At Start-->Run
If I type C:\Progra~1\CA, I get the explore screen.
But If I type C:\Progra~1\CA\Unicen~1, it failes with an error.
Some how, it works for 2 directory levels, but failing if I go beyond that.
Did any one come across this? Any help is appreciated.
Did anyone packaged USD (UniCenter Service Desk)?
I have a problem. Package seems to be ok on my test VM but it fails on Production servers.
I noticed this. This is a 16 bit app that works with 8.3 directory structure. There is a INI file (PARADIGM.INI) under user profile\Windows folder that reads like this:
[PARADIGM]
NX_ROOT=C:/PROGRA~1/CA/UNICEN~1/SERVIC~1
NX_LOCAL=C:/PROGRA~1/CA/UNICEN~1/SERVIC~1
NX_OS_TYPE=WINNT
When you launch the "Windows Client" shortcut, app load JAVA, and runs HELPDESK.JAR file. This is failing in PROD servers because Production server are not supporting 8.3 dir structure. Even if you change the INI file with "C:\Program Files\CA\Unicenter\Service Desk", still you cannot launch the short cut because I guess the EXE is hard coded to look for
C:/PROGRA~1/CA/UNICEN~1/SERVIC~1.
I also changed the below registry setting to "0".
HKLM\System\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreation
Still it doesn't work.
Also I noticed this:
At Start-->Run
If I type C:\Progra~1\CA, I get the explore screen.
But If I type C:\Progra~1\CA\Unicen~1, it failes with an error.
Some how, it works for 2 directory levels, but failing if I go beyond that.
Did any one come across this? Any help is appreciated.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
YRKUMAR
17 years ago
I got a work around for this. This is as per one of my friend's advice:
Installed the application in C:\CA\Unicentr\Svcedesk.
My PARADIGM.INI looks like this.
[PARADIGM]
NX_ROOT=C:/CA/Unicentr/Svcedesk
NX_LOCAL=C:/CA/Unicentr/Svcedesk
NX_OS_TYPE=WINNT
This eliminated long file names situation, and application launched successfully.
Installed the application in C:\CA\Unicentr\Svcedesk.
My PARADIGM.INI looks like this.
[PARADIGM]
NX_ROOT=C:/CA/Unicentr/Svcedesk
NX_LOCAL=C:/CA/Unicentr/Svcedesk
NX_OS_TYPE=WINNT
This eliminated long file names situation, and application launched successfully.
Posted by:
nheim
17 years ago
Hi Paul,
glad to see it worked out for you.
Just a hint: Check the 'real' shortfile names on the command line with dir /x.
Also check the shortfile names in the MSI (directory + file tables).
Regards, Nick
glad to see it worked out for you.
Just a hint: Check the 'real' shortfile names on the command line with dir /x.
Also check the shortfile names in the MSI (directory + file tables).
Regards, Nick
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.