.NET Questions and Solutions

As a software engineer, I focus on .NET, especially asp.net, C#, WCF and so on, and I am also very interested in Search Engine Optimization.

Entries Tagged ‘EXE’

After you run the Sysprep.exe tool in Windows Vista or in Windows Server 2008, the ACLs for a folder in C:\users\public\documents\data are out of order

Symptoms
When you run the System Preparation tool (Sysprep.exe) on a computer that is running Windows Vista or Windows Server 2008,a folder is created in or copied to the following location:
C:\users\public\documents\dataHowever, the access control lists (ACLs) forthis folder are out of order.
For example, assume that you create a folder under C:\users\public\documents\data. Then, you right-click the folder, you click Properties, and then you click the Security tab. In this scenario, the Security dialog box does not appear. Instead, youreceive the following error message:

The permissions on %foldername% are incorrectly ordered, which may cause some entries to be ineffective.
Resolution
Hotfix information A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support(http://support.microsoft.com/contactus/?ws=support)Note The “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.Prerequisites To apply this hotfix on a computer that is running Windows Vista, you must have Windows Vista Service Pack 1 (SP1) orWindows Vista SP2 installed.
To apply this hotfix on a computer that is running Windows Server 2008, you must have Windows Server 2008 SP1 orWindows Server 2008 SP2 installed. Restart requirement You do not have to restart the computer after you apply this hotfix. Hotfix replacement information This hotfix does not replace any other hotfixes. File information The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Vista and Windows Server 2008 file information notesThe MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment arelisted separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature. For all supported x86-based versions of Windows Server 2008 andof Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSetupcl.exe6.0.6001.2243441,98415-May-200910:37×86Setupcl.exe6.0.6002.2213741,98415-May-200910:25×86For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSetupcl.exe6.0.6001.2243448,64015-May-200910:56×64Setupcl.exe6.0.6002.2213748,64015-May-200910:33×64For all supported IA-64-based versions of Windows Server 2008
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSetupcl.exe6.0.6001.2243495,23215-May-200910:34IA-64Setupcl.exe6.0.6002.2213795,23215-May-200910:26IA-64

FIX: A floating point exception occurs during the optimization of a query

Symptoms
An INSERT, UPDATE, or DELETE query that operates on a table that is referenced by an indexed view may encounter a floating point exception during optimization. The batch and transaction is aborted, and you receive the following error message:

Server: Msg 3628, Level 16, State 1, Line 1
A floating point exception occurred in the user process. Current transaction is canceled.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft SQL Server 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
290211?(http://support.microsoft.com/kb/290211/) How to obtain the latest SQL Server 2000 service pack
Hotfix informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

DateTimeVersionSizeFile name——————————————————————-31-May-200317:452000.80.818.078,400Console.exe25-Jun-200300:012000.80.818.033,340Dbmslpcn.dll25-Apr-200301:12786,432Distmdl.ldf25-Apr-200301:122,359,296Distmdl.mdf30-Jan-200300:55180Drop_repl_hotfix.sql12-Sep-200302:262000.80.859.01,905,216Dtspkg.dll26-Aug-200319:162000.80.854.0528,960Dtspump.dll23-Jun-200321:402000.80.837.01,557,052Dtsui.dll23-Jun-200321:402000.80.837.0639,552Dtswiz.dll24-Apr-200301:51747,927Instdist.sql03-May-200300:561,581Inst_repl_hotfix.sql08-Feb-200305:402000.80.765.090,692Msgprox.dll01-Apr-200301:071,873Odsole.sql05-Apr-200300:462000.80.800.062,024Odsole70.dll07-May-200319:412000.80.819.025,144Opends60.dll02-Apr-200320:482000.80.796.057,904Osql.exe02-Apr-200322:152000.80.797.0279,104Pfutil80.dll04-Aug-200317:17550,780Procsyst.sql11-Sep-200323:3712,305Qfe469315.sql22-May-200321:5719,195Qfe469571.sql06-Sep-200300:361,090,932Replmerg.sql06-Sep-200306:182000.80.858.0221,768Replprov.dll06-Sep-200306:182000.80.858.0307,784Replrec.dll05-Sep-200323:001,087,150Replsys.sql13-Aug-200315:28986,603Repltran.sql29-Jul-200319:132000.80.819.0492,096Semobj.dll31-May-200317:272000.80.818.0172,032Semobj.rll05-Aug-200320:06127,884Sp3_serv_uni.sql01-Jun-200300:012000.80.818.04,215,360Sqldmo.dll07-Apr-200316:4425,172Sqldumper.exe19-Mar-200317:202000.80.789.028,672Sqlevn70.rll01-Jul-200323:182000.80.834.0180,736Sqlmap70.dll03-Sep-200301:562000.80.857.0188,992Sqlmmc.dll02-Sep-200322:032000.80.857.0479,232Sqlmmc.rll08-Feb-200305:402000.80.765.057,920Sqlrepss.dll23-Sep-200300:032000.80.863.07,614,545Sqlservr.exe25-Jul-200320:442000.80.845.0590,396Sqlsort.dll08-Feb-200305:402000.80.765.045,644Sqlvdi.dll25-Jun-200300:012000.80.818.033,340Ssmslpcn.dll01-Jun-200300:012000.80.818.082,492Ssnetlib.dll01-Jun-200300:012000.80.818.025,148Ssnmpn70.dll01-Jun-200300:012000.80.818.0158,240Svrnetcn.dll31-May-200317:592000.80.818.076,416Svrnetcn.exe30-Apr-200322:522000.80.816.045,132Ums.dll01-Jul-200323:192000.80.834.098,816Xpweb70.dll Note Because of file dependencies, the most recent hotfix or feature that contains these files may also contain additional files.

Exception Error in Nwconv.exe During Migration

Symptoms
When you attempt to migrate user accounts and data from Novell NetWare3.1x servers to Windows NT 3.5, 3.51, or 4.0 servers using the MigrationTool for Netware (Nwconv.exe), the Migration Tool for NetWare may stopresponding with an exception error 0xc0000005 in Nwconv.exe and generatea Drwtsn32.log file.
Resolution
During migration, the Migration Tool for NetWare builds a PrinterOperators member list. It enumerates all the print servers on the NetWareserver and then builds the user list of who is in the Printer Operatorgroup associated with the respective print server. The Migration Tool forNetWare sets a buffer size to hold a print server name less than or equalto 20 characters, including the null character. NetWare allows less thanor equal to 47 characters for the print server name. Unexpected resultsmay occur when you read a string into the buffer of a smaller size. Inthis case, the result is an exception error in Nwconv.exe.

Error Message: STOP 0×00000001e KMODE_EXCEPTION_NOT_HANDLED in Win32k.sys

Symptoms
When you restart your computer, you may receive the following error message:

STOP 0×0000001e KMODE_EXCEPTION_NOT_HANDLED in win32k.sys
or

STOP 0xC000021A {Fatal System Error}The Windows Logon Process terminated unexpectedly.
Resolution
This behavior can occur if you downloaded the Backdoor.NTHack virus from a remote host into your computer. This virus is initiated by the Dl.bat file in the InetPub\Scripts folder.
As a result, both the Firedaemon.exe and Sud.exe files are installed on the computer as well as the Os2srv.exe and Mmtask.exe files, which along with the Sud.exe and Index.exe files are run as services.

Error Message: Dr. Watson Exception (0×80000003)

Symptoms
When you try to run a program, the following Dr. Watson error message may be displayed:

An application error has occurred and an application error log is being generated.
<Program.exe>
Exception: hardcoded-breakpoint (0×80000003), Address: 0×77f76274Where <Program.exe> is the name of your program’s executable file. The Address value may be different.
Resolution
This problem occurs if a program makes a request for memory with the MEM_TOP_DOWN flag set. A bad pointer may be returned, causing the Dr. Watson error message.

BUG: You receive an “Unhandled Win32 exception” error message you use the Just-In-Time (JIT) debugger

Symptoms
When you use the Just-In-Time (JIT) debugger, you may experience the following symptoms: You receive the following error message:

“Just -In-Time Debugging Handler and CLR Remote Host: An exception ‘unhandled win32 exception’ has occurred in process ‘processID’. However, Visual Studio 7 just-in-time debugging has failed. Would you like to try debugging with the previously registered debugger (msdev path/msdev.exe)?”You receive an error message and the JIT Debugger does not start.
Resolution
This problem is because the absolute path of the shell resides in the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\shell with a value c:\windows\explorer.exe or c:\winnt\explorer.exe.