Error 193 Occurred While Creating User Login
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: 193 Error Windows Server > Remote Desktop Services (Terminal Services) Question 0 Sign in to vote Hi Experts,We have my application running on terminal services, clients are able to access the application from their clients start menu, all works as it should. We are now want to configure a client so that the application starts at runtime. If I open a remote desktop connection and point the Program Start and Filename to the application file I get the error:An Error (193) occurred while creating user logon...This initial program cannot be started...........The application will load if I point the "Program Start and Filename" in the remote connection to the setup.exe file the application loads. Anyone know why this is happening?Regards,Joe Wednesday, February 13, 2008 6:17 PM Reply | Quote Answers 0 Sign in to vote Hi Joe, What extension does this application have? If there's a file type that has an associated executable, I don't believe it will be picked-up here, for instance, if you put 'c:\MyTextFile.txt', it won't run, but if you run it in explorer, it knows to load up notepad and pass 'c:\MyTestFile.txt' as a parameter to notepad.exe, so instead one could pass 'notepad.exe c:\MyTestFile.txt' to get that same effect. Same goes here, you may need to find out which executable is associated with that file you want to launch. Thanks, Drew Monday, February 18, 2008 3:58 PM Reply | Quote Owner All replies 0 Sign in to vote Hi Joe, Please try this with the following string "C:\Windows\notepad.exe". Do you still see the same error message? If not, I would recommend checking your full path. Cheers, Moshe Thursday, February 14, 2008 1:50 AM Reply | Quote Moderator 0 Sign in to vote Hi Moshe, Thanks for the reply, I can run notepad or any other application using your approach and this probably exposes the issue! The file I am trying to run is not an exe file but an application built as part of an vb.net published program, this runs and looks for updates to the published program and then runs the exe, it doe’s not have an exe extension itself. Do I have to grant permissions to run this type of application! Yo
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > An error (193) occured while creating user logon. Want to Advertise Here? Solved An error (193) occured while creating user logon. Posted on 2009-01-12 https://social.technet.microsoft.com/Forums/windowsserver/en-US/ef1d21aa-7c51-44b2-8e13-1fc0f08eff88/193-error?forum=winserverTS Windows OS 1 Verified Solution 2 Comments 1,339 Views Last Modified: 2012-05-06 I have configured an MMC unlocked account.mmc & unlocked account.vbs in a windows 2003 server and shared to everone. I made delegation control to an OU that result in that mmc. My problem is when i configured terminal services and run the program like or \\servername\sharedfolder\unlocked account.mmc and https://www.experts-exchange.com/questions/24044480/An-error-193-occured-while-creating-user-logon.html try to connect then it shows the error An error (193) occured while creating user logon.The initial program cannot be started:\\servername\sharedfolder\unlocked account.vbs . FYI , I have enabled the remote previlages and local admin previlages but still nots working. Please give me a solution Larry Bangladesh 0 Question by:Idham60 Facebook Twitter LinkedIn Google LVL 7 Best Solution byC-Shadows Also this... http://support.microsoft.com/kb/186604 Go to Solution 2 Comments LVL 7 Overall: Level 7 Windows OS 1 Message Expert Comment by:C-Shadows2009-01-24 Check this.... http://support.microsoft.com/kb/186609 0 LVL 7 Overall: Level 7 Windows OS 1 Message Accepted Solution by:C-Shadows2009-01-24 Also this... http://support.microsoft.com/kb/186604 0 Write Comment First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. Featured Post Why You Should Analyze Threat Actor TTPs Promoted by Recorded Future After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent.
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for https://www.experts-exchange.com/questions/22457941/RDP-connection-error-An-Error-193-occurred-while-creating-user-logon.html a Full Time Job Ways to Get Help Expand Search Submit Close Search http://forum.windowsfaq.ru/archiveen/index.php/t-125588.html Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > RDP connection error: An Error (193) occurred while creating user logon... Want to Advertise Here? Solved RDP connection error: An Error (193) occurred while creating user logon... Posted on 2007-03-19 MS error 193 Server OS Windows OS Office / Productivity 1 Verified Solution 7 Comments 5,735 Views Last Modified: 2013-11-21 I have created a RDP connection to our application server that will start a .mdb file. Unfortunately, I am receiving this error when I try to connect: An Error (193) occurred while creating user logon... Within the Programs tab on RDP I have filled in: Program path error 193 occurred and file name: CRM.mdb Start in the following folder: D:\AccessDatabases What am I doing wrong? Thank you! 0 Question by:afoedit Facebook Twitter LinkedIn Google LVL 67 Active today Best Solution bysirbounty You could use a vbs instead... save as crm.vbs CreateObject("wscript.shell").run "D:\AccessDatabases\CRM.mdb", 0 Go to Solution 7 Comments LVL 67 Overall: Level 67 Windows OS 13 MS Server OS 11 Office / Productivity 1 Message Active today Expert Comment by:sirbounty2007-03-19 Is D a mapped drive? You might try running access.exe and using D:\AccessDatabases\CRM.mdb as a parameter 0 LVL 25 Overall: Level 25 MS Server OS 5 Windows OS 3 Office / Productivity 1 Message Expert Comment by:Ron M2007-03-19 Alot easier just to put a shortcut to the database in the "%alluserprofile%\start menu\programs\startup" folder on the terminal server. 0 Message Author Comment by:afoedit2007-03-19 I do not have D:\ mapped on my local machine D: is a separate local hard drive on the application server running terminal services. The need is to have multiple users run the database file from an RDP connection on their desktop. Currently, I have the database file store on the application server within the
TS (excuse me a new call can not) on win2008R2, user neadmin normally comes on a normal desktop. if user rdp client to specify "to run the program on input" or ANY notepad waddle error 193 its English version: An Error (193) occurred while creating user logon ... This initial program cannot be started the same program normally runs as this user, if he will run it by logging on to the server stol path command line option in the properties of the tabs in the normal RDP server properties allow launching programs from the profile ... remoteAPP not offer! Thank you for your answers AnSol2010-01-06 12:02:12 Specifies the full path or just notepad.exe? www_tank2010-01-06 14:59:15 Quote: Specify the full path or just notepad.exe? . Lnk problem is removed! this behavior in Windows 2008R2, if you try to call is not exe-file even lnk, cmd, vbs .... wants to run remoteApp черный2010-01-06 23:10:53 Quote: This behavior in Windows 2008R2, if you try to call is not exe-file even lnk, cmd, vbs .... wants to run remoteApp live and learn :)