Pdm_extract and pdm_load is not working in sdm

[Anon Anon]

Can some one help me on this issue please..

(version14.1,windows 2012)

pdm_extract and pdm_load is not working in bin folder and in other path as well..

Below is the error facing by the client.

 

‘E:\Program’ is not recognized as an internal or external command,operable program or batch file.

 

Tried to check 8dot3 name and environmental variable.

 

Checked 8dot3:

E:\Program Files <x86>\CA\Service Desk Manager\bin>fsutil 8dot3name query e:

The volume state is : 1 <8dot3 name creation name is disabled>.

The registry state is : 0 <Enable 8dot3 name creation on all volumes>.

Based on the above two settings, 8dot3 name creation is enabled in e:

 

Checked environmental variables:Below path is already there

E:\Program Files (x86)\CA\Service Desk Manager\bin

 

dblaod is working in bin folder ..

E:\Program Files <x86>\CA\Service Desk Manager\bin>dbload.exe –v “c:\users\administrator\desktop\custom tables\zftr.txt”

 

Note: i tried executing pdm_status,slstat,objname,pdm_ident -h commands.. all these are working

and pdm_extract and pdm_load are available in bin folder.

[Giedrius Bekintis]

I think something wrong with your environment variable, since pdm_load is executing dbload and most probably can't find it in E:\program. I would try to rewrite E:\Program Files (x86)\CA\Service Desk Manager\bin variable using 8dot3 names.

[Kaori Kishi]

Hi ganvi06,

 

Could you check C:\Windows\paradigm.ini file if it is pointing to an appropriate SDM installation folder? It should shows:

 

[PARADIGM]

NX_ROOT=C:/PROGRA~2/CA/SERVIC~1

NX_LOCAL=C:/PROGRA~2/CA/SERVIC~1

 

Also, please run dir /x command and check if the folder "Program Files (x86)" has 8.3 file name.

 

Thank you,

 

 

Kaori

[Anon Anon]

Hi Kaori,

 

Thanks for your reply. As per your suggestion, i checked C:\Windows\paradigm.ini file and ran dir /x command .Could you pelase check it.

 

Thanks & Regards,

Vindhya

[Kaori Kishi]

Hi Vindhya,

 

It looks 8.3 file name was not used when Service Desk was installed. Also, the "Program Files (x86)" folder does not have 8.3 file name. The dir command parameter "/x" shows both short and long file name. If "Program Files (x86)" has a short (8.3) file name, the short name, like "PROGRA~1" will be displayed as shown in the following screenshot. Had the "Program Files (x86)" folder been created by another application installation, such as SQL Client installation before you enabled the 8dot3name?

 

 

Kind regards,

 

Kaori

[Anon Anon]

Kaori,

even now i tried to enable 8dot3 again..still same issue with extract and load commands

[Kaori Kishi]

Hi Vindhya,

Normally, if you enable 8dot3name before SDM installation, and the SDM installation creates the folder, the 8.3 name should automatically be created for E:\Program Files (x86) folder. Had you installed something to E:\Program Files (x86) folder before you enabled 8dot3name? Had the E:\Program Files (x86) folder been created by SDM installation? For example, if you had installed the SQL Server agent to E:\Program Files (x86) folder before you had enabled 8dot3name, and then installed SDM to the same folder, the 8.3 name may not be created for E:\Program Files (x86) folder.

Also did you restart OS after you enabled 8dot3name? If you enabled before the SDM installation, paradigm.ini should have shown "SERVIC~1" as a 8.3 name of Service Desk Manager folder even though E:\Program Files (x86) folder does not have 8.3 name for the above reason... When you run dir /x for Service Desk Manager folder, can you see 8.3 name?

If E:\Program Files (x86) and Service Desk Manager folders do not have the 8.3 name, you need to uninstall and reinstall SDM.

Kind regards,

Kaori

[MILAN ZIGA]

Hi,

we had the same trouble a few days ago. As workaround we rebooted our Service Desk server to safe mode and added requested names using fsutil, for example: fsutil file setshortname "E:\Program Files (x86)" PROGRA~1

When short names were added we changed paths in C:\Windows\paradigm.ini to use short names.  pdm_load and pdm_extract works correctly now.

Regards,

Milan