[erlang-bugs] erlang:open_port bug!

Jan Jacobs <>
Wed Apr 4 22:46:31 CEST 2007


Hi All,

The erlang:open_port is drive sensitive. Meaning if the software is installed on the C: drive it works. If the same software is installed on the D: (or E:)  the following error occurs:

1> system_srv:start_link(). 
** exited: {einval,[{erlang,open_port,
                            [{spawn,"d:/Program Files/Ecs/UniNetscan-0.0.25/lib/system-0.0.1/priv/win32_system_info.exe"},
                             [{packet,2},binary,exit_status]]},
                    {port_api,open_port,2},
                    {system_srv,init,1},
                    {gen_server,init_it,6},
                    {proc_lib,init_p,5}]} **

I have noticed this for the first time today on a HP server which is running Windows 2003. The above example is done on my
noname AMD box running Windows XP.

If I reduce the length from "d:/Program Files/Ecs/UniNetscan-0.0.25/lib/system-0.0.1/priv/win32_system_info.exe" to 
"d:/Ecs/UniNetscan-0.0.25/lib/system-0.0.1/priv/win32_system_info.exe" it works. (work around to get the software working!)
If I install the exact same software on the C: drive "c:/Program Files/Ecs/UniNetscan-0.0.25/lib/system-0.0.1/priv/win32_system_info.exe" it works.

The same thing happens with the erlang software:

Eshell V5.5.3  (abort with ^G)
1> pwd().
D:/Program Files/Ecs/EcsProman-0.1.4
ok
2> odbc:connect("DSN=printspool;UID=SYSDBA;PWD=masterkey",[]).

=INFO REPORT==== 4-Apr-2007::22:39:47 ===
The odbc application was not started. Has now been started as a temporary applic
ation.
{error,{einval,[{erlang,open_port,
                        [{spawn,"d:/Program Files/Ecs/EcsProman-0.1.4/lib/odbc-2.0.7/priv/bin/odbcserver.exe"},
                         [{packet,4},binary,exit_status]]},
                {odbc,init,1},
                {gen_server,init_it,6},
                {proc_lib,init_p,5}]}}

Thanks
Jan Jacobs
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20070404/d0c787c2/attachment.html>


More information about the erlang-bugs mailing list