Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

• A NT Service - More Info
• A NT Service Template Script - For Beginners
• A NT Service Template Script - For Experts
• Anyway to Stop a Stop_Pending Service
• Can You Run a Uncompiled Script as a Service
• Explanation of Problems with NT Services
• Initialize variables for the SvcWaitForCmd
• Internal NT Errorwith WB Services
• Passing Parameters to a WinBatch Service
• Run Winbatch as a Service Sample Code
• Running a Service Script with Both Interact with Desktop and Network Access
• Sample Code to Start and Stop a Service
• SvcWaitForCmd User Commands
• UDF to Run Native Winbatch Service
• WB Service to Interact with Network Share
• XP SP2 Rebooting from Winbatch Service Failing

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Internal NT Error with WB Services

Keywords: 	 2140 Internal NT Error with WB Services

---

Question:

I am (successfully) running a WB service. I tried to add logic where if an error occurs I perform some drive UNmappings etc requiring the wwwnt34i.dll extender. When I put in the add extender line and compile as an exs file the service will not start, giving "Error 2140: An internal Windows NT error occurred". When I try to compile as a large exec and include the wwwnt34i.dll extender, the same thing happens. Simply commenting out the AddExtender line stops the error ... How do you use extenders in WB services ?

Answer:

1. Use a large or small exe (I suggest small exe's and placing the dll separately.

2. What account is the service running under. The LocalSystem account does not have network access privileges.

3. Check event log? What version of Windows are you running this on.

4. Using the divide and conquer strategy, try using some other extender (WILX) and do some inconsequnetial operation (Check version info) and get that part working to make sure we are not dealing with an extender installation/connect issue.

   If you can get WILX to work, test the wwwnt34i extender on the same machine as a login account to make sure the machine can load it.

   Then back into the service. Ummmmm however the service has its own mapped drives, different from the logged in user's ones.

   And if you are unmapping drives, no part of WinBatch (including the extenders) can be on the drives you are unmapping else horrible failures will occur.

Resolution:

I found the problem. I was running the .exs file from the c:\winnt\system32 directory however this directory did not contain the wbdch34i.dll (main winbatch dll). While the service would run using plain vanilla stuff, when I tried to add extender wwwnt34i.dll (or any other that I tried) I got the error described, even though wwwnt34i.dll was in the system32 directory.

---

Article ID:   W15683

File Created: 2003:05:13:11:29:32

Last Updated: 2003:05:13:11:29:32