CmdServer.exe missing


Author
Message
Julian
J
Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)Junior Member (14 reputation)
Group: Forum Members
Posts: 1, Visits: 3
I'm trying to get the Telnet Server running although when I connect with an account the connection is immediately lost. There's an error in the event viewer that says: "Internal CmdServer C:\Program Files\Pragma\Shared Files\CmdServer.exe -NONAWS TELNETD 30 120 telnet_7708_1332 Startup Failure.   Error 2: The system cannot find the file specified.". I tried looking for the CmdServer.exe file but it is not in the folder. 

Any idea what I could do to fix this error?

 
Attachments
tmp.PNG (1 view, 12.00 KB)
Technical Support Group...
Technical Support Group (TSG)
Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)Pragmateer (1.5K reputation)
Group: Moderators
Posts: 136, Visits: 639
Hi Julian

The most common cause of this error is a migration from a 32-bit machine to a 64-bit system. When you migrate this way, but install a 32-bit package on the new server and import settings using the legacy method of a .pcfg file, the settings will not match correctly.

If this is the issue, you have two options.

Option A
1.    Uninstall the 32-bit package and install a 64-bit package
2.    Manually copy the settings over. You might be able to import the .pcfg file, but you could continue to have issues. The .pcfg file is a registry export, so it might import to the 32-bit hive and not the 64-bit hive.

Option B
1.    Check that your installation directory is C:\Program Files (x86)\Pragma
2.    Go to the registry hive, using regedit.exe, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PragmaSystems
3.    Change all references of Pragma Files to Program Files (x86)

I recommend option A because it will get you running the correct platform for your new server.


The most common cause of this error is a migration from a 32-bit machine to a 64-bit system. When you migrate this way, but install a 32-bit package on the new server and import settings using the legacy method of a .pcfg file, the settings will not match correctly.

If this is the issue, you have two options.

Option A
1.    Uninstall the 32-bit package and install a 64-bit package
2.    Manually copy the settings over. You might be able to import the .pcfg file, but you could continue to have issues. The .pcfg file is a registry export, so it might import to the 32-bit hive and not the 64-bit hive.

Option B
1.    Check that your installation directory is C:\Program Files (x86)\Pragma
2.    Go to the registry hive, using regedit.exe, HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PragmaSystems
3.    Change all references of Pragma Files to Program Files (x86)

I recommend option A because it will get you running the correct platform for your new server.


Pragma Systems Technical Support
13809 Research Blvd, #675
Austin, TX 78750
http://www.pragmasys.com
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search