.NET Questions and Solutions

Symptoms
This article also applies to the following products:Microsoft Visual Studio 2010 SP1 Professional
IntroductionAn update is available for Microsoft Visual Studio 2010 Service Pack 1 (SP1) that adds support for designing and developing applications for Microsoft .NET Framework 4 Platform Update 1.
This update contains the updates for the .NET Framework 4 Platform Update 1 that are described in the following Microsoft Knowledge base (KB) articles: 2478063?(http://support.microsoft.com/kb/2478063/) Microsoft .NET Framework 4 Platform Update 1 – Runtime Update2495593?(http://support.microsoft.com/kb/2495593/) An update is available for Visual Studio 2010 SP1 to add support for designing and developing applications for Microsoft .NET Framework 4 Platform Update 12495638?(http://support.microsoft.com/kb/2495638/) Multi-Targeting Pack for the Microsoft .NET Framework 4 Platform Update 1 is availableFor more information about the specific features that are enabled as parts of the .NET Framework 4 Platform Update 1, click the following article number to view the article in the Microsoft Knowledge Base:
2478063?(http://support.microsoft.com/kb/2478063/) Runtime update for Microsoft .NET Framework 4 Platform Update 1

Resolution
Download information The following files are available for download from the Microsoft Download Center:

Collapse this imageExpand this image
Download thepackage now.(http://go.microsoft.com/fwlink/?LinkID=209198)
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591?(http://support.microsoft.com/kb/119591/) How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. Command line switches for this updateFor more information about the various command-line switches that are supported by this update, visit the following MSDN website:
Command-line options that are supported by this update(http://go.microsoft.com/fwlink/?LinkId=195005)For more information about Windows Installer, visit the following MSDN website:
General information about Windows Installer(http://msdn.microsoft.com/en-us/library/Aa367449)PrerequisitesTo install this update, you must have Windows Installer 3.1 or a later version installed.
To obtain the latest version of Windows Installer, visit the following Microsoft website:
Download information for Windows Installer 4.0 Redistributable(http://www.microsoft.com/downloads/en/details.aspx?familyid=5A58B56F-60B6-4412-95B9-54D056D6F9F4&displaylang=en)
Known issuesYou encounter the following known issues if you uninstall any one of the packages that are installed as parts of the .NET Framework 4 Platform Update 1:If you uninstall update 2495593, the Visual Studio toolbox support for State Machine model is removed.If you uninstall update 2495638, the Platform Update target framework and reference assemblies are removed. When you uninstall update 2495638, the uninstall operation regresses IntelliSense and compilations for Platform Update 1 features and for Workflow State Machine Designer.If you uninstall update 2478063, the runtime components that applications for Platform Update 1 require are removed.Restart requirementAfter you apply this update, you do not have to restart the computer unless the files that are being updated are locked or used.
However, you have to restart Visual Studio to display the new toolbox buttons in Visual Studio if Visual Studio 2010 SP1 is running when you install this update.Update removal informationTo remove this update completely, you have to remove the updates that are described in the following articles individually by using Add or Remove Programs in Control Panel:2478063?(http://support.microsoft.com/kb/2478063/) Microsoft .NET Framework 4 Platform Update 1 – Runtime Update2495593?(http://support.microsoft.com/kb/2495593/) An update is available for Visual Studio 2010 SP1 to add support for designing and developing applications for Microsoft .NET Framework 4 Platform Update 12495638?(http://support.microsoft.com/kb/2495638/) Multi-Targeting Pack for the Microsoft .NET Framework 4 Platform Update 1 is availableNote These three updates are installed as parts of the .NET Framework 4 Platform Update 1.
File information The global 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimeWorkflowDesigner.pkgdef5,46628-Mar-201118:15WorkflowDesigner.extension.vsixmanifest75928-Mar-201118:15

Symptoms
Consider the following scenario:An application connects to one of the following products: Microsoft SQL Server 2005 Microsoft SQL Server 2005 Express EditionMicrosoft SQL Server 2000SQL Server Desktop Engine (also known as MSDE 2000)The application uses the SET NOCOUNT ON statement for the connection. The application uses a Microsoft ActiveX Data Objects (ADO) client-side cursor toinsert a row into a table that has an identity column. When the application queries the identity column value of the newly inserted row, the value “0″ is returned incorrectly. When this value is returned, an application that uses the ActiveX Data Objects (ADO) interfacemay malfunction, or data loss may occur. Whether a malfunction or data loss occurs depends on how the application handles this scenario.
Note This problemoccurs only if the application uses a client-side cursor. If the application uses a server-side cursor, the application is not affected.
This problem occurs in the Microsoft Data Access Components (MDAC) components of the following Windows operating systems: Windows Vista Service Pack 1 (SP1)Windows XP Service Pack 2 (SP2) with hotfix 940569 Windows XP Service Pack 3 (SP3) Windows Server 2008
Resolution
To resolve this issue, install the hotfix that is described in the following Microsoft Knowledge Base article:
961451?(http://support.microsoft.com/kb/961451/) FIX: You receive an incorrect value when you query the last-inserted identity value after you use a client-side cursor to insert data to a table that contains an identity column in an application that uses ActiveX Data ObjectsNote The hotfix that was described in the “Resolution” section in the earlier version of this article is superseded by the hotfix that is described in 961451.

Symptoms
This article describes how to enable SQL Server connectivity on Windows XP Service Pack 2.
By default, Windows Firewall is enabled on computers that are running Microsoft Windows XP Service Pack 2. Windows Firewall closes ports such as 445 that are used for file and printer sharing to prevent Internet computers from connecting to file and print shares on your computer or to other resources. When SQL Server is configured to listen for incoming client connections by using named pipes over a NetBIOS session, SQL Server communicates over TCP ports and these ports must be open. SQL Server clients that are trying to connect to SQL Server will be not be able to connect until SQL Server is set as an exception in Windows Firewall. To set SQL Server as an exception in Windows Firewall, use the steps that are listed in the “More Information” section.
Resolution
Create an exception for each instance of SQL Server The following method will open User Datagram Protocol (UDP) port 1434 in addition to the Transmission Control Protocol (TCP) port. If you want to open these ports manually, see the following article in the Microsoft Knowledge Base:
841252?(http://support.microsoft.com/kb/841252/) How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL Server 2000
Note If you are running multiple instances of SQL Server, you will have to create an exception for each instance. Click Start, and then click Run. In the Run dialog box, type Firewall.cpl, and then click OK.In the Windows Firewall dialog box, click Add a Program on the Exceptions tab.In the Add Program dialog box, you can select an instance of SQL Server or you can click the Browse button to locate the instance of SQL Server that you want to add to the exception list. The default installation locations for SQL Server are listed in the following table.

Collapse this tableExpand this table
VersionFile pathSQL Server 7.0 Mssql\Binn\Sqlservr.exeSQL Server 2000 Default InstanceProgram Files\Microsoft SQL Server\Mssql\Binn\Sqlservr.exeSQL Server 2000 Named InstanceProgram Files\Microsoft SQL Server\Mssql$instancename\Binn\Sqlservr.exeSQL Server 2005 Default InstanceProgram Files\Microsoft SQL Server\MSSQL.x\MSSQL\Binn\sqlservr.exeSQL Server 2005 Named InstanceProgram Files\Microsoft SQL Server\MSSQL.x\MSSQL\Binn\sqlservr.exe
Note Each SQL Server 2005 instance is made up of a distinct set of services with specific settings for collations and other options. The directory structure, registry structure, and service names all reflect the specific instance ID of the SQL Server instance that is created during SQL Server 2005 Setup. x is the instance ID of the SQL Server instance that is created during SQL Server 2005 Setup.Select the name of the instance, and then click OK.Under Programs and Services, select the check box that is next to the name you selected in step 6, and then click OK. How to use Multiprotocol Remote Procedure Call (RPC)If you are using Multiprotocol, you must perform the steps in the “Create an exception for each instance of SQL Server” section as well as open the correct TCP ports on Windows Firewall.How to run RPC over TCPWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
To run RPC over TCP, follow these steps:Enable port 135 on Windows Firewall. To do this, follow these steps: Click Start, and then click Run.In the Run dialog box, type Firewall.cpl, and then click OK.On the Exceptions tab, click Add Port. In the Port number box, type 135, and then click the TCP button.In the Name box, type a name for the port such as MULTI, and then click OK.On the Exceptions tab, you will see the new service. To enable the port, click to select the check box next to your new service, and then click OK.Modify the \\HKLM\SOFTWARE\Policies\Microsoft\Windows NT\RPC registry key.
Note If you have just installed SQL Server, this registry key does not exist. You will have to create the key and set the value. To do this, follow these steps: Click Start, and then click Run.In the Run dialog box, type Regedit, and then click OK. This will start Registry Editor.Locate the \\HKLM\SOFTWARE\Policies\Microsoft\Windows NT\RPC Registry key.Set the RestrictRemoteClients key to 0. Quit Registry EditorRestart the computer that is running SQL Server.How to use RPC over Named PipesIf you are running RPC over Named Pipes, you must open port 445 on Windows Firewall. To do this, follow these steps: Click Start, and then click Run.In the Run dialog box, type Firewall.cpl, and then click OK.On the Exceptions tab, click Add Port. In the Port number box, type 445, and then click the TCP button.In the Name box, type a name for the port such as MULTI, and then click OK.On the Exceptions tab, you will see the new service. To enable the port, click to select the check box next to your new service, and then click OK.

Symptoms
Consider the following scenario in Microsoft Visual Studio Team System 2008 Database Edition GDR: You have a database project that includes tables.You have another database project that includes constraints for the tables in the same solution and you add a reference to the database project that includes tables.You connect both projects to the same target database on a server.Then, you deploy the projects to the database.In this scenario, you receive a System.NullReferenceException exception and then the Visual Studio IDE crashes. If you debug this exception, you receive the following error message:

System.NullReferenceException: Object reference not set to an instance of an object.
Resolution
To resolve this problem, upgrade to Microsoft Visual Studio Team System 2008 Database Edition GDR R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970479?(http://support.microsoft.com/kb/970479/) List of fixed issues in the Microsoft Visual Studio Team System 2008 Database Edition GDR R2
Note Microsoft Visual Studio Team System 2008 Database Edition GDR R2 replaces Microsoft Visual Studio Team System 2008 Database Edition GDR.

Symptoms
Consider the following scenario. An orchestration is published as a Web service. The Web service redirects the SOAP request to an external Web service. The external Web service returns a SOAP exception. In this scenario, the negative acknowledgement (NACK) message in Microsoft BizTalk Server 2006 does not contain the details of the original exception. If the hotfix in Microsoft Knowledge Base article 927492 has been installed, the NACK message may be correct. However, the message format may be incorrect. This may cause a NullReferenceException error message.
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 this specific problem. 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 tocreate 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.PrerequisitesYou must have BizTalk Server 2006 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace a previously released hotfix.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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformMicrosoft.biztalk.webservices.serverproxy.dll3.5.1714.054,34428-Sep-200717:42×86Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

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.