.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 ‘Server’

FIX: “Exception caught: Object reference not set to an instance of an object” error message when you compile a large map in BizTalk Server 2004

Symptoms
In Microsoft BizTalk Server 2004, you may receive the following error message when you try to compile a large map:

Exception Caught: Object reference not set to an instance of an object.
Resolution
Service pack informationTo resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
888751?(http://support.microsoft.com/kb/888751/) How to obtain the latest BizTalk Server 2004 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 tool in Control Panel.

DateTimeVersionSizeFile name——————————————————————————————01-Apr-200402:313.0.5267.0676,864Btsxmltools.dll01-Apr-200402:573.0.5267.0274,432Microsoft.biztalk.basefunctoids.dll01-Apr-200402:573.0.5267.045,056Microsoft.biztalk.crossreferencing.dll01-Apr-200402:573.0.5267.040,960Microsoft.biztalk.crossreferencingfunctoids.dll01-Apr-200402:573.0.5267.0249,856Microsoft.biztalk.mapper.dll01-Apr-200402:573.0.5267.01,114,112Microsoft.biztalk.tom.dll
NoteBecause of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Exception 0E in Vredir.vxd during CoCreateInstanceEx() on remote DCOM server

Symptoms
If your network is set up as a workgroup, you have a drive mapped to a Microsoft Windows NT-based server, and you run a Distributed Component Object Model (DCOM) program that attempts to start a remote server component on the Windows NT-based server, you may receive one of the following error messages on a blue screen.
Windows 95, Windows 98, Windows 98 Second Edition:

Windows
A fatal exception 0E has occurred at 0028:???????? in VXD VREDIR(??)+ ????????. The current application will be terminated.
* Press any key to terminate the current application.
* Press CTRL+ALT+DEL again to restart your computer. You will lose any unsaved information on all applications.
Press any key to continue.Windows Millennium Edition (Me):

Windows
An error has occurred. To continue:
Press Enter to return to Windows, or Press CTRL+ALT+DEL to restart your computer. If you do this, you will lose any unsaved information in all open applications.
File Name: VREDIR(06) + 00006C54 Error: 0E : 0028 : C02D2770
Press any key to continue.If you press ENTER, CoCreateInstanceEx returns RPC_S_CALL_FAILED (0×800706BE). The program may display the following error message:

The remote procedure call failed.See the “More Information” section of this article for the error message values for various versions of the Vredir.vxd file.
Resolution
The redirector (Vredir.vxd) incorrectly references internal resource data for the mapped drive connection while setting up the connection that the DCOM Remote Procedure Call (RPC) traffic will use.

Event ID 5000 occurs when the Exchange IMAP4 worker process crashes intermittently in Exchange Server 2007

Symptoms
The Exchange IMAP4 worker process crashes intermittently on a computer that is running Microsoft Exchange Server 2007. When this problem occurs, an event is logged that resembles the following:

Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Description: EventType clr20r3, P1 microsoft.exchange.imap4.exe, P2 8.1.278.2, P3 481f7feb, P4 microsoft.exchange.imap4, P5 8.0.0.0, P6 481f7feb, P7 a6, P8 17, P9 system.nullreferenceexception, P10 NIL.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Resolution
To resolve this problem, install Update Rollup 4 for Exchange Server 2007 Service Pack 1 (SP1) on the Exchange server.For more information about Update Rollup 4 for Exchange Server 2007 Service Pack 1, see the following Exchange Help topic:
Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1 (http://go.microsoft.com/fwlink/?LinkId=152556)For more information about how to obtain the latest Exchange service pack or update rollup, see the following Exchange Help topic:
How to Obtain the Latest Service Pack or Update Rollup for Exchange 2007(http://go.microsoft.com/fwlink/?LinkId=152570)

Error when you try to call the Prepare method before you add parameters: “An unhandled exception of type ‘System.Data.SqlClient.SqlException’ occurred in system.data.dll”

Symptoms
When you create a parameterized command against Microsoft SQL Server 7.0, if you call the Prepare method before you add parameters to the command, you receive the following error message:

An unhandled exception of type ‘System.Data.SqlClient.SqlException’ occurred in system.data.dll.
Additional information: System error. This problem does not occur in SQL Server 2000.
Resolution
This problem occurs in SQL Server 7.0 because, by design, you cannot run the Prepare method before you add parameters. This applies to most database systems.
SQL Server 2000 does not generate the above-mentioned exception because it does not run Prepare until the first command is executed. This optimization prevents the overhead of Prepare if no commands are subsequently executed.

Error message when you use SQL Server Management Studio to connect to SQL Server 2005 Integration Services from a client computer: “Connect to SSIS Service on machine ‘<SSISServer>’ failed …

Symptoms
Consider the following scenario. A server is running Microsoft SQL Server 2005 Integration Services (SSIS). From a client computer, you use SQL Server Management Studio to connect to Integration Services on the server. To connect to Integration Services on the server, you use auser account that is not a member of the Administrators group on the server. In this scenario, you receive the following error message:

Cannot connect to SSISServer
Additional information:Failed to retrieve data for this request (Microsoft.SqlServer.SmoEnum)
Connect to SSIS Service on machine “SSISServer” failed: Access is denied.Note In this error message, SSISServer is a placeholder for the name of the server or for the IP address of the server.
However, you can successfully connect to Integration Services on the server locally by using the same user account that you used to connect to Integration Services from the client computer.
Resolution
To work around this problem, follow these steps:On the client computer, enable Windows Management Instrumentation (WMI) for remote administration. To do this, follow these steps:Click Start, click Run, type gpedit.msc, and then click OK.In the Group Policy Object Editor, expand Computer Configuration, expand Administrative Templates, and then expand Network.Expand Network Connections, expand Windows Firewall, and then click Domain Profile.Right-click Windows Firewall: Allow remote administration exception, and then click Properties.
Note In Windows Vista, right-click Windows Firewall: Allow inbound remote administration exception.In the Windows Firewall: Allow remote administration exception Properties dialog box, click Enabled, and then click OK.
Note In Windows Vista, the dialog box is the Windows Firewall: Allow inbound remote administration exception dialog box.On the server and on the client computer, specify that DCOM is available for all Microsoft COM applications. To do this, follow these steps:Click Start, click Run, type dcomcnfg, and then click OK.In the Component Services dialog box, expand Component Services, expand Computers, right-click My Computer, and then click Properties.In the My Computer Properties dialog box, click the Default Properties tab.On the Default Properties tab, click to select the Enable Distributed COM on this computer check box, and then click OK.On the server, add the user account to the Distributed COM Users group. To do this, follow these steps:Click Start, click Run, type lusrmgr.msc, and then click OK.In the Local Users and Groups dialog box, click Groups, and then double-click Distributed COM Users.In the Distributed COM Users Properties dialog box, click Add.In the Select Users dialog box, type the user name under Enter the object names to select, and then click OK two times.On the server, grant theappropriate permissions for the MsDtsServer DCOM application. To do this, follow these steps:Click Start, click Run, type dcomcnfg, and then click OK.In the Component Services dialog box, expand Component Services, expand Computers, and then expand My Computer.Expand DCOM Config, right-click the MsDtsServer object, and then click Properties.In the MsDtsServer Properties dialog box, click the Security tab.Under Launch and Activation Permissions, click Customize, and then click Edit.In the Launch Permission dialog box, click Add.In the Select Users or Groups dialog box, type the user name under Enter the object names to select, and then click OK.In the Launch Permission dialog box, click the user name under Group or user names.Under Permissions for UserName, click to select the Allow check box for the following permissions:Local LaunchRemote LaunchLocal ActivationRemote ActivationNote UserName is a placeholder for the user name that you clicked in step h.Click OK.In the MsDtsServer Properties dialog box, click Customize under Access Permissions, and then click Edit.In the Access Permission dialog box, click Add.In the Select Users or Groups dialog box, type the user name under Enter the object names to select, and then click OK.In the Access Permission dialog box, click the user name under Group or user names.Under Permissions for UserName, click to select the Allow check box for the following permissions:Local AccessRemote AccessClick OK two times.Restart the SQL Server Integration Services service.

Error message when you use a startup script to start the SQL Server PowerShell provider in SQL Server 2008: “Set-Location: Object reference not set to an instance of an object”

Symptoms
Microsoft SQL Server 2008 installs the SQL Server PowerShell (SQLPS) provider as a feature. When you use a startup script to start the SQL Server PowerShell provider separately without using the SQLPS minishell, the SQL Server PowerShell provider does not let you navigate the SQL Server object hierarchy. Instead, you receive the following exception error message:

Set-Location: Object reference not set to an instance of an object.
Resolution
The SQL Server PowerShell provider requires certain global variables to exist. Typically, the SQLPS minishell sets these global variables. However, when you use a startup script to start the SQL Server PowerShell provider, these global variables are not declared.