Finance | Project Operations, Human Resources, ...

System Message 5004; CreateProcess() error 193

(0) Share

Report

Posted on by Community Member

Went to a client's server today to add a user to their SL system. When I started SL, I received the following error:

System Message 5004

Unable to execute e:\mdsl\microsoft dynamics\SL\Applications\SM\9822000 DEFAULT. Windows CreateProcess()error 193.

Clicking on OK, the menu appeared, so I tried to access User Maintenance, received an error similar to this one (I got this trying to access AR's Invoice and Memo:)

System Message 5004

Unable to execute e:\MDSL\Microsoft Dynamics\SL\Applications\AR\0801000.exe 1

[Navigation]navpath='<Company Name>\Financial\Accounts Receivable\Input\Invoice and Memo'. Windows CreateProcess() error 193

I get the same sort of message no matter what I try to start. I've checked the registry entries, permissions on the SL folders and even tried turning off the virus protection for a few minutes (with the same results.)

Any ideas on what I need to do to fix this?

Thanks!

Stuart Nottingham

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

CFROTON 4,710 on at

Like (0)

Report
Copy link

Link copied!

Dear Stuart,

Are you saying that you are logging in as the user you created to access the screens?

Did you try logging in as the sysadmin.

The error received can be caused by a few things, some of these may pertain to you.

Third party software in which you don't have access, or its not in Screen maintenance (screens for that software)

The module is not installed.

Antivirus programs- you should reboot after you disable it

The drive on the workstation is not properly mapped to the SL-applications folders

The screen doesn't have file rights to Everyone or the windows user is not in the everyone group.

UAC was on when you installed SL

You can create a case in support, but you might try and run a process monitor during the attempt to access the screens

docs.microsoft.com/.../procmon

Best Regards,

Jana MacDonald

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Jana, this is the server install. I am the sysadmin (Windows Authentication.) Module (SM) is installed. Other workstations are operating fine.

No third party add-ons.

Disabled Symanted, rebooted. Same errors.

Drive mapping not applicable as this is the server.

I am in Everyone group as SYSADMIN.

Will try Procmon in the morning and report back.

Was this reply helpful? Yes No
CFROTON 4,710 on at

Like (0)

Report
Copy link

Link copied!

Dear Stuart,

I've inquired with an Environment specialist regarding the errors.

He will likely ask the version you run. Can you post that in your next post?

Best Regards,

Jana

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Thanks, Jana. They're on SL 2015 CU2.

Was this reply helpful? Yes No
Sean Cross 225 on at

Like (0)

Report
Copy link

Link copied!

"Windows Updates" did this to me a week or so ago.

The next round of 'windows updates' cleared it up.

Looks like a change in the .NET Framework dlls that they then fixed.

Have you run all the windows updates on the server?

My clients had no problems using Dynamics, only we could not use Dynamics on the server itself.

Was this reply helpful? Yes No