Sunday, July 24, 2016

Connection Sharing Problems


How to Troubleshoot Internet Connection Sharing Problems

Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Summary
This article describes how to troubleshoot problems with Internet Connection Sharing (ICS) on Windows 98 Second Edition-based computer.
More information
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

When you use ICS, you can share one Internet connection between two or more computers. Before you install or use ICS, you should contact your Internet service provider (ISP) or read your ISP's Terms and Conditions of use policy to determine if you are permitted to share your connection.

For additional information about ICS, click the article number below to view the article in the Microsoft Knowledge Base:
234815 Description of Internet Connection Sharing
To install ICS:
  1. Click Start, point to Settings, click Control Panel, and then double-click Add/Remove Programs.
  2. Click Internet Tools on the Windows Setup tab, and then click Details.
  3. Click to select the Internet Connection Sharing check box, click OK, and then click OK again.
  4. Follow the instructions to run the ICS wizard.
NOTE: You should only install ICS on the computer that you use to connect to the Internet. This computer is called the "host" computer. The other computers on the local area network (LAN) that use the host to connect to the Internet are called "client" computers.

For additional information about ICS requirements, click the article number below to view the article in the Microsoft Knowledge Base:
230140 Only One Internet Connection Sharing Host Is Required on a LAN
NOTE: The term "dial-up adapter" is used in this article to refer to your modem. This term may also refer to an Integrated Services Digital Network (ISDN) or Asymmetric Digital Subscriber Line (ADSL) device.

Host Configuration

To troubleshoot ICS, verify that the correct components are installed on the host after you install ICS. Check for the following two components in Network properties, where adapter is your dial-up adapter or your network adapter:

  • TCP/IP(Shared)->adapter
  • TCP/IP(Home)->adapter
To check the components in Network properties:
  1. Click Start, point to Settings, click Control Panel, and then double-click Network.
  2. On the Configuration tab, view the The following network components are installed box to verify that both the TCP/IP(Shared) and TCP/IP(Home) components are listed.
If either of the components appear in Network properties but do not have the (Home) and (Shared) reference, ICS is not installed correctly and does not work correctly. You may need to remove and then reinstall ICS to resolve this issue.

For additional information about the ICS entries in Network properties, click the article number below to view the article in the Microsoft Knowledge Base:
236465 Description of How ICS Appears in Network Properties
The TCP/IP(Shared) component should be the adapter that you use to connect to the Internet and the TCP/IP(Home) component should be the adapter that you use to connect to your LAN. If the TCP/IP(Shared) component is not in the The following network components are installed box, the host and client computers cannot connect to the Internet. If the TCP/IP(Home) component is not in the The following network components are installed box, the host and client computers may not be able to connect to each other on the LAN.

NOTE: If you know the adapter that you use to connect to the Internet and the adapter that you use to connect to the LAN, you can skip the following Determining the TCP/IP(Shared) and the TCP/IP(Home) adapter section.

How to Determine the TCP/IP(Shared) and TCP/IP(Home) Adapters

  • Standard Dial-Up Networking Connections

    For a standard Dial-Up Networking connection, the Microsoft dial-up adapter should be listed in Network properties. To determine if Dial-Up Networking is used to connect to the Internet, check for an icon for your ISP in the Dial-Up Networking folder. To view the Dial-Up Networking folder, double-click My Computer, and then double-click the Dial-Up Networking folder.

    For a standard Dial-Up Networking connection, the following components should be listed in Network properties for the host computer:

    • TCP/IP(Shared)->Dial-Up Adapter
    • TCP/IP(Home)->Network Adapter
    • Third-Party Internet Dialer Connections

    To determine if you are using a third-party dialer to connect to the Internet, check Network properties to view the third-party dialer's dial-up adapter. For ICS to work correctly with a third-party dialer, the dialer software must use a 32-bit dial-up adapter. Some ISPs use their own dialer to connect to the Internet, for example, America Online (AOL).

    For a third-party dialer connection, the following components should be listed in Network properties for the host computer, where Third-Party Dialer Adapter is the name of the third-party dialer adapter, and is the name of the network adapter:

    • TCP/IP(Shared)->Third-Party Dialer Adapter
    • TCP/IP(Home)->Network Adapter

    For additional information about how to use third-party dialers with ICS, click the article numbers below to view the articles in the Microsoft Knowledge Base:
    230233 How to Use AOL with Internet Connection Sharing
    229978 ICS Cannot Autodial 3rd-Party Internet Dial-Up Connections
    NOTE: For devices that use a network adapter, some ISP's record the adapter address, which is often referred to as the "MAC address" of the network adapter. Your ISP may only allow you to connect to the internet with that specific network adapter. If you want to use a different network adapter, you may need to contact your ISP for additional assistance.
  • Unidirectional devices

    For unidirectional devices, such as one-way cable modems, you must have a connection to a source to send data and a connection to a source to receive data. ICS does not work correctly with this type of configuration.For additional information about one-way adapters, click the article number below to view the article in the Microsoft Knowledge Base:
    231648 ICS Does Not Function with Unidirectional Adapters
  • Two-way cable modems

    For a two-way cable modem, the cable modem requires a network adapter for the host computer. This configuration requires that you have two network adapters installed in your computer, one for the cable modem and one for the LAN.

    For a cable modem connection, the following components should be listed in Network properties for the host computer, here the TCP/IP(Shared) is the network adapter connected to the cable modem, and TCP/IP(Home) is the network adapter connected to the LAN:
    • TCP/IP (Shared)->Network Adapter1
    • TCP/IP (Home)->Network Adapter2
  • ADSL devices

    For an external asymmetric digital subscriber line (ADSL) device, the ADSL device requires that there is a network adapter installed in the host computer. This configuration requires two network adapters to be installed in the computer, one for the cable modem and one for the LAN.

    For a external ADSL device connection, the following components should be listed in Network properties for the host computer, where TCP/IP(Shared) is the network adapter that is connected to the ADSL device, and TCP/IP(Home) is the network adapter that is connected to the LAN:

    • TCP/IP(Shared)->Network Adapter1
    • TCP/IP(Home)->Network Adapter2

    NOTE: For an internal ADSL device, the ADSL device uses the standard dial-up adapter to connect to the Internet. Internal ADSL devices should function the same as standard dial-up networking connections. This can also be true for external ADSL devices, such a those that connect through USB ports. You will normally see a reference to a PPPoE (Point-to-Point Protocol over Ethernet) or PPPoA (Point-to-Point Protocol over ATM). You should also see TCP/IP (Shared), Dial-up Adapter (as listed above), or Modem Connections.

    For more information, see the following articles in the Microsoft Knowledge Base:
    273587 How to Configure ICS for Use with DSL Connections That Use PPPoE
    265728 Internet Connection Sharing Requires Two Network Adapters
  • ISDN devices
    For an Integrated Services Digital Network (ISDN) device, both internal and external ISDN devices use the dial-up adapter to connect to the Internet. ISDN devices should function the same as standard dial-up networking connections.

Using the Icssetup.log File

To determine which adapters the Internet Connection Sharing wizard identified as potential Shared and Home Adapters, check the Icssetup.log file in the Windows folder. The Internet Connection Sharing wizard checks for possible adapters from the lists of adapters in Network Properties. If problems exist, verify that each of these adapters are also listed under Network Adapters in Device manager.

NOTE: The Internet Connection Sharing wizard will never identify a dial-up adapter as the Home Adapter.

Sample Icssetup.log file

Internet Connection Sharing Setup Log: Wednesday Mar 17 1999
Build Adapter ListBuild Adapter List - found: Dial-Up Adapter
Build Adapter List - found: Linksys LNEPCI II PCI Ethernet Adapter
Build Adapter List - found: Internet Connection Sharing
Find Internal Adapter Candidates, checking: Dial-Up Adapter NOT a
candidate, known special purpose adapter
Find Internal Adapter Candidates, checking: Linksys LNEPCI II PCI Ethernet Adapter IS a candidate
Find Internal Adapter Candidates, checking: Internet Connection Sharing NOT a candidate, known special purpose adapter
Find External Adapter Candidates, checking: Dial-Up Adapter IS a candidate
Find External Adapter Candidates, checking: Linksys LNEPCI II PCI Ethernet Adapter NOT a candidate, only valid Internal adapter
Find External Adapter Candidates, checking: Internet Connection Sharing NOT a candidate, known special purpose adapter
Find Internal Adapter Candidates, checking: Dial-Up Adapter NOT a candidate, known special purpose adapter
Find Internal Adapter Candidates, checking: Linksys LNEPCI II PCI Ethernet Adapter IS a candidate
Find Internal Adapter Candidates, checking: Internet Connection Sharing NOT a candidate, known special purpose adapter
Loaded external adapter: Dial-Up Adapter
Loaded internal adapter: Linksys LNEPCI II PCI Ethernet Adapter

TCP/IP(Home) and TCP/IP(Shared) Appear on the Wrong Adapters

To resolve this issue, follow these steps:
  1. Click Start, point to Settings, click Control Panel, and then double-click Internet Options.
  2. On the Connections tab, click Sharing.
  3. Under Connect to the Internet using, select the adapter for your Internet connection from the list.
  4. Under Connect to my home network using, select the adapter for your LAN from the list.
  5. Click OK, click OK again, and then restart your computer when you are prompted.
If the Sharing button is not present, this can be caused by the wrong versions of the Inetcpl.cpl and Inetcplc.dll files. For additional information on this issue, click the article number below to view the article in the Microsoft Knowledge Base:
236152 No Sharing Button After Installing Internet Connection Sharing
NOTE: If you remove or reinstall any components that are displayed in Network Properties on the Host, you must also remove and reinstall ICS.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

Only One of the TCP/IP Components is Listed in Network Properties

This issue can occur if one or more registry key is damaged. To resolve this issue, follow these steps:
  1. In Network Properties, write down the description of each of the adapters listed.
  2. In Registry Editor, open the following key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\Net\<nnnn>
    Where <nnnn> is an incremental 4-digit number starting at 0000.
  3. Delete each key where the DeviceDesc entry does not match the description of one of the adapters in Network Properties.

    If there are multiple keys for the same adapter listed in Network Properties, delete each of the keys and then remove and reinstall the adapter in Device Manager. To remove the adapter in Device Manager, click Start, point to Settings, click Control Panel, double-click System, click the Device Manager tab, double-click Network adapters, click the adapter, and then click Remove.NOTE: You may need the original driver disk or software to reinstall the adapter after you remove it from Device Manager.

TCP/IP(Shared) and TCP/IP(Home) Components Missing

This issue can occur if the Iphlpapi.dll file is the incorrect version or damaged.

To resolve this issue, extract a new version of the file from the Windows 98 Second Edition CD-ROM and then remove and reinstall ICS. To extract the Iphlpapi.dll file, follow these steps:
  1. Click Start, click Run, type sfc.exe in the Open box, and then click OK.
  2. Click Extract one file from Installation disk.
  3. Type iphlpapi.dll in the Specify the system file you would like to restore box, and then click Start.
  4. In the Restore From box, type the drive letter and path to the Windows 98 Second Edition Source CD-ROM folder.
  5. In the Save File In box, type the full path to the \Windows\System folder (for example, C:\Windows\System), and the click OK.
  6. Click OK to use the default backup folder when you are prompted.
  7. Click OK and the quit System File Checker.
  8. Remove and reinstall ICS

Enable DHCP Services on Host

Without a proper IP address, the client will be unable to communicate with the Host computer. If the client computer does not obtain an IP address from the Host, the DHCP service may be disabled. To enable the DHCP services on the Host computer, follow these steps:
  1. On the Windows 98 Second Edition CD-ROM, open the Tools\MTSutil\ICS folder.
  2. Right-click the Dhcp_on.inf file, and then click Install.
  3. Restart Windows.

Client Configuration

Configure Client for DHCP

To configure the client computer to obtain an IP address from the Host computer, follow these steps:
  1. Click Start, point to Settings, click Control Panel, and then double click Network.
  2. Click the TCP/IP component installed for the Network Adapter on you LAN.
  3. Click Properties.
  4. On the IP Address tab, click Obtain IP address automatically.
  5. On the WINS Configuration tab, click Use DHCP for WINS Resolution.
  6. On the Gateway tab, remove any gateways that may be installed.
  7. On the DNS Configuration tab, click Disable DNS.
  8. Click OK, click OK again, and then click Yes if you are prompted to restart the computer.
If you prefer to assign the client IP information manually, or feel that the DHCP is not functioning properly, refer to the section entitled How to Assign a Static IP Address later in this article.

How to Assign a Static IP Address

Before you can assign a static IP address, you will need the DNS configuration information from your ISP. Or, on the Host computer, click Start, click Run, type winipcfg, and then click OK. Click ICShare Adapter, click More Info, note the DNS server address, and then click OK. After you obtain the DNS setting, follow these steps:
  1. Click Start, point to Settings, click Control Panel, and then double-click Network.
  2. Click the TCP/IP component installed for the Network Adapter on you LAN.
  3. Click Properties.
  4. On the IP Address tab, click Specify an IP Address.
  5. In the IP Address box, type 192.168.0.x (where x is a number between 2 and 254).

    NOTE: The IP address should be one that is not currently in use by another computer on your LAN.
  6. In the Subnet Mask box, type 255.255.255.0.
  7. On the WINS Configuration tab, click Disable WINS Resolution.
  8. On the Gateway tab, type 192.168.0.1 in the New gateway box, and then click Add.
  9. On the DNS Configuration tab, click Enable DNS, type the host computer name in the Host box.

    NOTE: The Domain box can be left blank, and note that the computer name is case-sensitive.
  10. In the DNS Server Search Order box, type the IP address for your HOST computer (usually 192.168.0.1),, and then click Add.NOTE: If the HOST IP address does not work properly, try using your ISP's DNS server IP address.
  11. Click OK, click OK again, and then click Yes if you are prompted to restart the computer.
For additional information about how to assign a static IP address, click the article number below to view the article in the Microsoft Knowledge Base:
230150 How to Configure a Permanent IP Address for Network Devices

The Host Connects to the Internet But the Client Does Not

With the Host connected to the Internet, test the LAN and Internet connections by performing the following procedures:
  • Use Winipcfg Tool

    To use the Winipcfg tool to verify the IP address, follow these steps:

    1. Click Start, click Run, type winipcfg, and then click OK.
    2. In the Ethernet Adapter Information box, select the network adapter.
    3. Click Release, click Renew, and then click OK.
    If the IP address for the network adapter is 192.168.0.x (where x is a number between 2 and 254), the client successfully obtained an IP address from the host.

    If the client does not obtain an IP address from the Host, you may need to enable the DHCP service on the Host or manually assign a static IP address to the client.
  • Ping IP Address of Host

    To use the Ping command to verify the functionality of Transport Control Protocol/Internet Protocol (TCP/IP), follow these steps:
    1. Click Start, point to Programs, and then click MS-DOS Prompt.
    2. At the command prompt, type ping 192.168.0.1, and then press ENTER.
    3. At the command prompt, type exit, and then press ENTER to return to Windows.
    If you receive a reply, the client computer is able to communicate with the Host computer over the LAN with TCP/IP.

    If you do not receive a reply, troubleshoot the issue as a general network connection problem in Windows. For information about troubleshooting network connection problems in Windows, click the article number below to view the article in the Microsoft Knowledge Base:
    192534 Troubleshooting Windows 95/98 Network Connection Problems
  • Ping IP address on Internet

    To ping the IP address of a Web site on the Internet, you first need to obtain the IP address of a Web site on the Internet from the Host. To obtain the IP address for a Web site, follow these steps:

    1. On the Host computer, click Start, point to Programs, and then click MS-DOS Prompt.
    2. At the command prompt, type ping <Web site name> (where <Web site name> is the Uniform Resource Locator (URL) of a Web site), and then press ENTER.NOTE: Some Web sites (such as www.microsoft.com) may not return a reply, if this occurs, try a different Web site.
    3. If the Web site returns a reply, you should receive the following message:
      pinging <Web site name> [xxx.xxx.xxx.xxx]...
      Where <Web site name> is the Uniform Resource Locator (URL) of the Web site and xxx.xxx.xxx.xxx is the IP address of the Web site.
    4. Write down this IP address to use later.
    After you have obtained the IP address for a Internet Web site, to test the TCP/IP connection on the client, following these steps:

    1. On the client computer, click Start, point to Programs, and then click MS-DOS Prompt.
    2. At the command prompt, type ping xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the IP address for the Internet Web site), and then press ENTER.
    3. At the command prompt, type exit, and then press ENTER to return to Windows.
    If you receive a reply, the client computer is able to communicate with the Internet over the LAN with TCP/IP.

    If you do not receive a reply, refer the the Host Configuration section mentioned previously in this article for steps to configure and troubleshoot problems with the Host computer.
  • Ping Internet Name

    If the client can successfully ping the IP address of a website, use the Internet name to test the DNS configuration with ping. To do this, follow these steps:
    1. Click Start, point to Programs, and then click MS-DOS Prompt.
    2. At the command prompt, type ping <Web site name> (where <Web site name> is the Uniform Resource Locator (URL) of a Web site), and then press ENTER.

      NOTE: Some Web sites (such as www.microsoft.com) may not return a reply, if this occurs, try a different Web site.
    If you receive a reply, the Host and client computer are configured and working correctly. NOTE: If your browser is still unable to open a Web Site by name, check the browser's connection settings and make sure it is configured to use the LAN to connect and that no proxy servers are configured.
  • Open IP Address in Browser

    To test the browser by attempting to open a Web site by the IP address, follow these steps:

    1. Click Start, click Run, type http://xxx.xxx.xxx.xxx (where xxx.xxx.xxx.xxx is the IP address of the Web site), and then click OK.
    If the Web site is displayed, the browser is functioning properly and there may be a problem with Domain Name Server (DNS) resolution.

    For additional information about configuring DNS, click the article number below to view the article in the Microsoft Knowledge Base:
    229974 Connection Error Messages When You Use ICS with an FQDN
    If the Web site is not displayed, there may be a problem with Winsock on the computer.

    For information about possible Winsock issues, click the article number below to view the article in the Microsoft Knowledge Base:
    188952 "Internal Error Occurred" Error Message Using Internet Explorer

Damaged Registry Keys

This issue can occur if one or more registry key is damaged. To resolve this issue, follow these steps:
  1. In Network properties, write down the description of each of the protocols listed.
  2. In Registry Editor, open the following key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\nnnn
    Where nnnn is an incremental four-digit number starting at 0000.
  3. Check the number of subkeys under the NetTrans folder with the number of instances of protocols installed in the network configuration. There should be one subkey for each instance of a protocol installed.

    If there are more keys than protocols listed in Network properties, uninstall ICS, export a copy of the NetTrans key, and then delete the NetTrans key from the registry. This can remove all components from the network configuration except the adapters installed.
  4. To rebuild the NetTrans key, double-click Network in Control Panel, and then click the Add button on the Network Configuration tab. Click Client, click Add, click Client for Microsoft Networks, and then click OK. When the Network Configuration screen returns, it will have added the default protocol and rebuilt the NetTrans key in the registry so that there is only one subkey for each protocol installed.
  5. Check the registry again to make sure that only one NetTrans subkey exists per protocol installed. If so, reinstall ICS on the host and check to see if the problem is resolved.
Properties
Article ID: 238135 - Last Review: 06/19/2014 06:04:00 - Revision: 2.0
  • kbenv kbhowto kbnetwork kbtshoot KB238135
Feedback
Posted by at No comments:

Wednesday, February 3, 2016

Bugs that are fixed in SQL Server 2012 Service Pack 2

Bugs that are fixed in SQL Server 2012 Service Pack 2

Introduction
This article lists the bugs that are fixed in Microsoft SQL Server 2012 Service Pack 2 (SP2).

Notes
  • Additional fixes that are not documented here may also be included in the service pack.
  • This list will be updated when more articles are released.
For more information about how to obtain SQL Server 2012 service packs, click the following article number to view the article in the Microsoft Knowledge Base:
2755533 How to obtain the latest service pack for SQL Server 2012
Note For more information about which download you should select from the available downloads list, check the release notes here.
More information
SQL Server 2012 service packs are cumulative updates and upgrade all editions and service levels of SQL Server 2012 to SP2. In addition to the fixes that are listed in this article, this service pack contains up to and including Microsoft SQL Server 2012 SP1 Cumulative Update 9 (CU9). 

For more information about the cumulative update packages that are available for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2772858 The SQL Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was released

Issues that are fixed in this service pack

For more information about the bugs that are fixed in SQL Server 2012 SP2, click the following article numbers to view the articles in the Microsoft Knowledge Base.
VSTS bug numberKB article numberDescription
13746172028830FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 or SQL Server 2012 Failover Cluster installation
17030142963382FIX: Can't connect to the server when you run a cube creation MDX query in SSAS 2012
20112472927741FIX: Image is not displayed correctly in the webpage when you use DrillThrough action on an SSRS 2012 report
20349942963383FIX: Text truncated when you use HPB renderer to view a report in SSRS 2012
17694692963384FIX: SQL Server crashes when the log file of tempdb database is full in SQL Server 2012
19731682963386FIX: SSRS 2012 fails with IsolatedStorageException when subscriptions exported to Excel worksheets are larger than 10 MB
19731962963388FIX: SSRS 2012 cannot export a report that is larger than 10 MB to Excel format
7873582963404FIX: Rollback causes database to go to suspect mode in SQL Server 2012
10437172806979FIX: Poor performance when you run a query against a table in an RCSI-enabled database in SQL Server 2012
11785852963412New DMF sys.dm_fts_index_keywords_position_by_document in SQL Server 2012 SP2
11822412966520FIX: New log files are not created when you restart the Reporting Services Windows Service in SSRS 2012 on January 1
12408482966519FIX: No error message when log backup failed in SQL Server 2012
12538612936004FIX: Visual Studio 2012 crashes because of access violation when the data source binding is completed in Report Viewer 2012 UI in local mode
12620292966522FIX: File Share subscription doesn't populate the description column in SSRS 2012
14817732966523FIX: The "Name" drop-down list is empty when an SSRS 2012 report is specified
14193672964762FIX: Event ID 22 or error 0xC1000016 will be logged when you use Discover command in SSAS 2012
21039032972285FIX: Performance issues when you use SSISDB as your deployment store in SQL Server 2012
20215812965035SSAS 2012 logging feature improvement in SQL Server 2012 Service Pack 2
2037492952444FIX: Poor performance when you use table variables in SQL Server 2012
20950642936328FIX: Access violation occurs when you run CHECKTABLE or CHECKDB against a table that has persisted computed columns in SQL Server 2008 R2 or SQL Server 2012
12224722827857FIX: DTA does not work on SQL Server 2012 instance that uses a supplementary character collation
21242092939277FIX: Incorrect results when you run queries that contain UNION operator by using parallel query plan in SQL Server
Resolutions to the following issues are also included in SQL Server 2012 SP2.
VSTS bug numberDescription
950185Improved messaging around processing errors and warnings when you work with large HTML reports.
950189Improved messaging around processing errors and warnings when you work with reports with large number of parameters.
994470Incorrect results when you work with block mode unary operators.
1041277DPM’s full backup on the server with AlwaysOn secondary will be converted to copy_only backup.
1278767The value of tabular instance perfmon counters: Memory\VertiPaq <TypeName> KB is always 0.
1355346The end SCOPE statement does not match the opening SCOPE statement.
1374617FIX: Shared components are installed in the wrong location when you implement a SQL Server 2008 Failover Cluster installation
1610447Uninitialized object leads to crashes and potentially wrong results when executing DAX expressions with conditional calculations.
1610492A simple DAX query returns unexpected results when you use PowerPivot v2 11.0.3000.0.
2060218"ACTIONABLE_HEAP_CORRUPTION" when SSRS configuration file is parsed by using an invalid InstanceId.
2065570NonYieldProcessTable record in RING_BUFFER_NONYIELD_PROCESSTABLE ring buffer does not have user and kernel process time.
2075161Provides platform information in the log of SSRS 2012
1347204FIX: Access Violation when you insert data into a table that has a column with a sequence default from a cross-database transaction in SQL Server 2012
1184332If a tail log backup is performed against the model database, model database will freeze in restoring state during a server restart that will prevent the SQL Server from starting successfully. This is because Tempdb database could not be created during the server startup and you receive the following error message: “Database '<DatabaseName>' cannot be opened"
1243853Error 3456 occurs when restoring the log backup of a bulk-logged DB where a new data file was added with an initial size greater than 64704KB.
1404999When you drop of a database snapshot is issued in a session with a LOCK_TIMEOUT setting, a time-out error may occur followed by an assertion error.
1190211Installation of SQL Server by using InstallShield ends up in a hang state. For more information, go to this Knowledge Base article.
1386073After you install SQL Server 2012 SP2, when SQL Server is stopped from either configuration manager or service control manager, an informational message is logged to the SQL Server immediately after shutdown is issued. In earlier versions, we issued this messages after internal services, such as the .NET Framework, service broker, were stopped.
Fixes for Connect Items submitted by the community
Connect Bug IDDescription
714689Evaluation results are written to output xml file multiple times when you implement Enterprise Management Framework against multiple servers and an error occurs against one of the servers in the list.
735543Database goes into a restore mode when its backup is restored as a different database on the same instance.
736509You cannot debug a stored procedure that calls sp_executesql in SQL Server Management Studio (SSMS). When F11 is pressed, you receive an 'Object reference not set to an instance of object' error message.
740181SSMS does not fully manage Full-Text in SQL Server Express.
745566SQL Server SMO ignores default constraint in SQL Server 2012 and SQL Server 2014.
764197SSMS handles Numbered Stored procedures inconsistently.
769121"Column '<column name>' does not belong to table summary. (System.Data)" error message when replicating tables have the same names but are located in different schemas.
773710After reverting to a database snapshot that contains full-text indexes, you cannot create any ft_catalogs until you either restart SQL Server, detach and then attach the database, or take the database offline and then set the database online.
774317SSMS occasionally crashes on close, which then causes it to automatically restart
785064"Value of 'null' is not valid for 'stream' " error message when you work with customer pipeline components in Business Intelligence Development Studio (BIDS).
785151When you execute queries with Show Actual Query Plan turned on, the result of Null is returned, and you receive the following error message:
Error: Msg 50000, Level 16, State 10, Procedure test, Line 34 String or binary data would be truncated.
791929"A system assertion check has failed" error message when you insert data into a partitioned view that has triggers.
797967Create script duplicates the statements when scripting column level permissions in SSMS.
799430SSMS may crash when you try to refresh the SSMS window icon on the task bar.
804901Deploying new versions of large projects encounters a time-out during deployment into SSIS Catalog database (SSISDB). Additionally, you receive the following error messages:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier ’219′. (Microsoft SQL Server, Error: 27203) Failed to deploy the project. Fix the problems and try again later.:Timeout expired. The timeout period 
Posted by at No comments:
Subscribe to: Posts (Atom)