.NET Questions and Solutions

Symptoms
After you upgrade a Microsoft SQL Server 2000-based computer to Microsoft SQL Server 2000 Service Pack 4 (SP4), a SQL Server query that calls a registry extended stored procedure may fail, and you receive the following error message:

Access is denied.You receive the error message when you use any one of the registry extended stored procedures in the following list: xp_regreadxp_instance_regreadxp_regenumkeysxp_instance_regenumkeysxp_regenumvaluesxp_instance_regenumvaluesxp_regwritexp_instance_regwritexp_regaddmultistringxp_instance_regaddmultistringxp_regremovemultistringxp_instance_regremovemultistringxp_regdeletevaluexp_instance_regdeletevaluexp_regdeletekeyxp_instance_regdeletekey
Resolution
This problem occurs because SQL Server 2000 SP4 implements a restriction on which registry paths the registry extended stored procedures can access. When a query calls a registry extended stored procedure, the registry extended stored procedure examines the requested registry subkey against a control list of registry hives. If the registry subkey that the query requests is not in the control list, you receive the following error message:

‘Access is denied.’ This error message has nothing to do with the permissions of the SQL Server user account in the context of which one of these registry extended stored procedures is called. The error message occurs even if the user has Administrator permissions.
Note When you receive the error message, the registry extended stored procedure returns no results.

Symptoms
On a Microsoft Windows XP-, Microsoft Windows Server 2003-, Microsoft Windows Vista- and Microsoft Windows Server 2008-based computer, if you attempt to shutdown the computer when you are running an application that uses the Remote Access Connection Manager, or the Telephony service, the Remote Access Connection Manager or the Telephony service may not be stopped properly and an unexpected error may occur.
In addition, even if you try to stop the Remote Access Connection Manager service or the Telephony service, the following error massage is displayed and the service cannot be stopped.

When running the Remote Access Connection Manager service Windows XP and Windows Server 2003

Cannot stop the Remote Access Connection Manager service on a local computer.
The service did not return an error. This could be an internal Windows error or an internal service error.
If the problem persists, contact your system administrator. On Windows Vista and Windows Server 2008, you cannot click the Stop button once the service is in use and an error message will not be displayed.
When running the Telephony service Windows XP and Windows Server 2003

Cannot stop the Telephony service on a local computer.
Error 1053:The service did not respond to the start or control request in a timely fashion. Windows Vista and Windows Server 2008

Cannot stop the Telephony service on a local computer.
Error 1052:The requested control is not valid for this service.
Resolution
Because the Remote Access Connection Manager or the Telephony service cannot be stopped properly, an application that uses these services may return an unexpected error.

Symptoms
When you try to activate Windows Vista or Windows Server 2008 over the Internet, the activation may be unsuccessful. Additionally, you may experience one or more of the following symptoms: Activation fails with error code 0×8004FE33. The following Error events may be recorded in the Application log:

Log Name: Application
Source: Software Licensing Service
Event ID: 8198
Level: Error Description: License Activation (SLUI.exe) failed with the following error code: 0×80004005

Log Name: Application
Source: Software Licensing Service
Event ID: 1008
Level: Error Description: Acquisition of Secure Processor Certificate failed. Status Code=hr=0×8004FE33Activation is not successful, and you are not prompted for credentials.
Resolution
This issue may occur when you connect to the Internet through a proxy server where Basic authentication is enabled.
When the proxy server is configured for Basic authentication, the server requires that you type a username and a password. However, the activation user interface does not let you enter these credentials. Therefore, the Basic authentication fails, and activation is not successful.

Symptoms
A data transferprocess does not automatically resume after you re-enable the disk drive. You experience this problem when the following conditions are true: You disable the disk drive during the data transfer process.Your computer is running one of the operating systems that are listed in the “Applies to” section.Note This problem also occurs when you use a removable storage device such as a floppy disk.
Resolution
This problem occurs because the Background Intelligent Transfer Service (BITS) performs the following functions:BITS changes the state of the data transfer to theERROR state.BITS generates a BG_E_VOLUME_CHANGED error return value.Then, when you re-enable the disk drive and BITS resumes the data transfer job, BITS changes the state of the data transfer from the ERROR state to the TRANSIENT_ERROR state. BITS also generates the BG_E_DESTINATION_LOCKED error return value again. The data transfer remains in the same state and does not automatically resume.
MORE INFORMATION
The BG_E_DESTINATION_LOCKED error return value translates to the following:The destination file system volume, specified in the local file name, is locked.
BITS is a Windows component that performs the following functions:BITS asynchronously transfers files in the foreground or the background.BITS preserves the responsiveness of other network programs.BITS automatically resumes file transfers after the network disconnects and the computer restarts.

Symptoms
On a computer that is running Windows Server 2008 or Windows Vista, you receive the following Stop error message when you create a snapshot of a volume:?

STOP: 0×0000007E (parameter1, parameter2, parameter3, parameter4)
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Notes The parameters in this error message vary, depending on the configuration of the computer.Not all “0×0000007E” Stop errors are caused by this issue.For example, you receive this Stop error message after you enable Volume Shadow Copy Service on a volume for a secondary Data Protection Manager (DPM) server.
Resolution
This issue occurs because of a race condition in the Volume Shadow Copy Service driver (Volsnap.sys).
When the volume size is being changed in the snapshot creation process, the race condition might be encountered.

Symptoms
Consider the following scenario:
You have a computer that is running Windows Server 2008 or Windows Server 2008 R2.You set up a software RAID5 volume on the computer by using dynamic disks.You perform some disk I/O-intensive operations on the volume.
For example, you use Distributed File System (DFS) Replication to replicate files.In this scenario, you receive a Stop error message that resembles the following:

STOP 0×0000001E (parameter1, parameter2 , parameter3 , parameter4)
KERNEL_MODE_EXCEPTION_NOT_HANDLED
NotesThe parameters in this Stop error message vary, depending on the configuration of the computer. Not all “Stop 0×0000001E” error messages are caused by this issue.
Resolution
This issue occurs because of an error in the Volmgrx.sys driver.