Problem with extractpl.bat / prolib.exe

M

Maviee

New Member
Hi,

I'm using Progress version 9.1e and I'm trying since days to extract the adecomm.pl and adeedit.pl files. Progress has a nice batch file on-board which should do this automatically.

Progress installation in Path L:\dlc91 , so I set the %DLC% variable to "L:\dlc91" also. Furthermore the extractpl suggests that you include the %DLC%/bin directory into the path. I also did this. Here are both commands:

set DLC= L:\dlc91
set PATH=%DLC%\bin

Typing "SET" in a DOS prompt I get the vars (I think correctly):

DLC=L:\dlc91
Path=L:\dlc91\bin

Alright I thought, everything is correct, lets try to unpack the files with the following line:

extractpl adeedit.pl AND extractpl adecomm.pl

The batch file creates the directoy but then prolib (which gets called by the batch file) tells me:

The DLC environment variable must contain a valid directory/path (11002).

I also tried the same thing in the proenv environment, but I still get the same error.
Did someone has the same problem or does anyone has a solution to my problem ?

Thanks in advance
Mav
 
This sounded pretty good, so I checked my registry entries. Every key in my registry has the value I assiged to the %DLC% variable. :(

Greetings
Mav

Lee Curzon said:
Check your DLC value in the registry, and in your ini file.

Needs to be exactly correct.
Click to expand...
 
I notice your drive is L:.

Is it shared? There are issues with shared/mapped drives sometimes.

If so, try adding a backslash to the end of your DLC entries/variables.

Remember to backup before any registry/ini changes!

Try the environment variables first.
 
You are perfectly right. The L:\ drive is a shared drive on one of our DB servers. I tried one more backslash, but still without success. Is it possible to copy necessary files to my C:\ drive and start the unpacking from there ?

Greetings
Mav

Lee Curzon said:
I notice your drive is L:.

Is it shared? There are issues with shared/mapped drives sometimes.

If so, try adding a backslash to the end of your DLC entries/variables.

Remember to backup before any registry/ini changes!

Try the environment variables first.
Click to expand...
 
You mean transfer the pls?

You can try, but it sounds like the problem is with the prolib executable itself.

There is a simple test: type the prolib command longhand (full pathname), including the full pathname of a pl you want to operate on (the pl can be anywhere - try it on your local drive).

If it works, then make a copy of the scripts, and replace the prolib commands with L:...\prolib (whatever), and try again.


Going back to the shared drive thing:

KB P86941 suggests a couple of other workarounds:

1. Upgrade to 10.0a :)

2. Share the drive at a higher level

(Quote)
1. If you share out the directory above the DLC this does not occur.
eg, sharing c:\program files\progress instead of c:\program
files\progress\dlc this error will not occur.


Incidentally, search the KB on error message 11002. That may give you a couple of other pointers.


If this doesn't work, and none else can help, you may need to talk to Tech Support (sorry!).
 
You must log in or register to reply here.
Back
Top