FIX: Data that is associated with a component that uses the System.Data object may become corrupted in an application that is built on the Microsoft .NET Framework 2.0

Article translations Article translations
Article ID: 932491 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

When you try to use a component in an application that is built on the Microsoft .NET Framework 2.0, data that is associated with the component may become corrupted. This problem occurs when the component uses a System.Data.DataSet object. When this problem occurs, you may experience one or more of the following issues:
  • When the AcceptChanges method in a DataView class is called, the record manager may become corrupted.
  • The computed values in an expression column may not be updated correctly.
  • When the DataTable.Select method is called by using multiple statements, an incorrect result may be returned.
  • The internal index of a DataTable object may become corrupted. Additionally, you receive a '13' error message.
  • When a Merge operation occurs, the record manager may become corrupted if the target row is in the edit state.
  • The internal index of a DataTable object may become corrupted. Additionally, you receive a '5' 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.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:
http://code.msdn.microsoft.com/KB932491

Note The MSDN Code Gallery displays the languages for which the hotfix is available. If you do not see your language listed, it is because the Code Gallery resource page is not available for that language.

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

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart your 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.
For x86-based computers
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Mscordacwks.dll2.0.50727.802802,30403-Feb-200711:22x86
Mscorjit.dll2.0.50727.802326,65603-Feb-200711:22x86
Mscorlib.dll2.0.50727.8024,308,99203-Feb-200711:22x86
Mscorpe.dll2.0.50727.802102,91203-Feb-200711:22x86
Mscorwks.dll2.0.50727.8025,625,34403-Feb-200711:21x86
Normalization.dll2.0.50727.80215,36003-Feb-200711:22x86
Normidna.nlpNot Applicable59,34203-Feb-200711:22Not Applicable
Normnfc.nlpNot Applicable45,79403-Feb-200711:22Not Applicable
Normnfd.nlpNot Applicable39,28403-Feb-200711:22Not Applicable
Normnfkc.nlpNot Applicable66,38403-Feb-200711:22Not Applicable
Normnfkd.nlpNot Applicable60,29403-Feb-200711:22Not Applicable
Peverify.dll2.0.50727.802136,19203-Feb-200711:21x86
Sos.dll2.0.50727.802382,46403-Feb-200711:22x86
System.data.dll2.0.50727.8022,902,01603-Feb-200711:22x86
System.data.oracleclient.dll2.0.50727.802482,30403-Feb-200711:22x86
Vsavb7rt.dll8.0.50727.8021,330,68803-Feb-200711:21x86
For x64-based computers
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Mscordacwks.dll2.0.50727.8021,597,44003-Feb-200703:14x64
Mscordacwks.dll2.0.50727.802802,30403-Feb-200711:22x86
Mscorjit.dll2.0.50727.8021,587,71203-Feb-200703:13x64
Mscorjit.dll2.0.50727.802326,65603-Feb-200711:22x86
Mscorlib.dll2.0.50727.8023,960,83203-Feb-200706:28x64
Mscorlib.dll2.0.50727.8024,308,99203-Feb-200711:22x86
Mscorpe.dll2.0.50727.802157,18403-Feb-200703:07x64
Mscorpe.dll2.0.50727.802102,91203-Feb-200711:22x86
Mscorpjt.dll2.0.50727.8022,004,99203-Feb-200703:13x64
Normalization.dll2.0.50727.80218,43203-Feb-200703:12x64
Normalization.dll2.0.50727.80215,36003-Feb-200711:22x86
Normidna.nlpNot Applicable59,34203-Feb-200703:14Not Applicable
Normidna.nlpNot Applicable59,34203-Feb-200711:22Not Applicable
Normnfc.nlpNot Applicable45,79403-Feb-200703:14Not Applicable
Normnfc.nlpNot Applicable45,79403-Feb-200711:22Not Applicable
Normnfd.nlpNot Applicable39,28403-Feb-200703:14Not Applicable
Normnfd.nlpNot Applicable39,28403-Feb-200711:22Not Applicable
Normnfkc.nlpNot Applicable66,38403-Feb-200703:14Not Applicable
Normnfkc.nlpNot Applicable66,38403-Feb-200711:22Not Applicable
Normnfkd.nlpNot Applicable60,29403-Feb-200703:14Not Applicable
Normnfkd.nlpNot Applicable60,29403-Feb-200711:22Not Applicable
Peverify.dll2.0.50727.802136,19203-Feb-200711:21x86
Peverify.nlp2.0.50727.802205,82403-Feb-200703:13Not Applicable
Sos.dll2.0.50727.802480,76803-Feb-200703:22x64
Sos.dll2.0.50727.802382,46403-Feb-200711:22x86
System.data.dll2.0.50727.8022,967,04003-Feb-200706:28x64
System.data.dll2.0.50727.8022,902,01603-Feb-200711:22x86
System.data.oracleclient.dll2.0.50727.802498,68803-Feb-200706:28x64
System.data.oracleclient.dll2.0.50727.802482,30403-Feb-200711:22x86
Mscorwks.dll2.0.50727.80210,323,45603-Feb-200703:11x64
Mscorwks.dll2.0.50727.8025,625,34403-Feb-200711:21x86
Vsavb7rt.dll8.0.50727.8021,330,68803-Feb-200711:21x86
For Itanium-based computers
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Mscordacwks.dll2.0.50727.8022,719,23203-Feb-200703:15IA-64
Mscordacwks.dll2.0.50727.802802,30403-Feb-200711:22x86
Mscorjit.dll2.0.50727.8022,705,92003-Feb-200703:13IA-64
Mscorjit.dll2.0.50727.802326,65603-Feb-200711:22x86
Mscorlib.dll2.0.50727.8023,960,83203-Feb-200706:42IA-64
Mscorlib.dll2.0.50727.8024,308,99203-Feb-200711:22x86
Mscorpe.dll2.0.50727.802313,85603-Feb-200703:06IA-64
Mscorpe.dll2.0.50727.802102,91203-Feb-200711:22x86
Mscorpjt.dll2.0.50727.8023,501,05603-Feb-200703:14IA-64
Normalization.dll2.0.50727.80215,36003-Feb-200711:22x86
Normalization.dll2.0.50727.80244,03203-Feb-200703:12IA-64
Fl_normidna.nlpNot Applicable59,34203-Feb-200711:22Not Applicable
Normidna.nlpNot Applicable59,34203-Feb-200703:14Not Applicable
Normnfc.nlpNot Applicable45,79403-Feb-200711:22Not Applicable
Normnfc.nlpNot Applicable45,79403-Feb-200703:14Not Applicable
Normnfd.nlpNot Applicable39,28403-Feb-200711:22Not Applicable
Normnfd.nlpNot Applicable39,28403-Feb-200703:14Not Applicable
Normnfkc.nlpNot Applicable66,38403-Feb-200711:22Not Applicable
Normnfkc.nlpNot Applicable66,38403-Feb-200703:14Not Applicable
Normnfkd.nlpNot Applicable60,29403-Feb-200711:22Not Applicable
Normnfkd.nlpNot Applicable60,29403-Feb-200703:14Not Applicable
Peverify.dll2.0.50727.802136,19203-Feb-200711:21x86
Peverify.dll2.0.50727.802383,48803-Feb-200703:13IA-64
Sos.dll2.0.50727.802382,46403-Feb-200711:22x86
Sos.dll2.0.50727.802862,72003-Feb-200703:23IA-64
System.data.dll2.0.50727.8022,902,01603-Feb-200711:22x86
System.data.dll2.0.50727.8023,109,88803-Feb-200706:42IA-64
System.data.oracleclient.dll2.0.50727.802482,30403-Feb-200711:22x86
System.data.oracleclient.dll2.0.50727.802501,76003-Feb-200706:42IA-64
Mscorwks.dll2.0.50727.8025,625,34403-Feb-200711:21x86
Mscorwks.dll2.0.50727.80221,309,95203-Feb-200703:11IA-64
Vsavb7rt.dll8.0.50727.8021,330,68803-Feb-200711:21x86

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

Issue 1: When the AcceptChanges method in a DataView class is called, the record manager may become corrupted

Record manager corruption may occur during a write operation from an event handler. When this occurs, a System.NullreferenceException exception may be raised. Additionally, when the application performs a write operation in a ListChanged event, index updates may occur in the incorrect order.

For example, consider the following scenario:
  1. You use the following code in the application:
    using System;
    using System.ComponentModel;
    using System.Data;
    
    class Test {
        private static DataRow _dr = null;
        private static bool _accept = false;
        
        public static void Main()
        {
            try {
                DataSet ds = new DataSet();
                DataTable dt = ds.Tables.Add("Customers");
                DataColumn c = dt.Columns.Add("Id", typeof(int));
                dt.PrimaryKey = new DataColumn[] { c };
                dt.Columns.Add("Name", typeof(string));
                dt.Columns.Add("Age", typeof(int));
                
                dt.Rows.Add(new object[] { 1, "A", 10 });
                dt.Rows.Add(new object[] { 2, "B", 20 });
                dt.Rows.Add(new object[] { 3, "G", 30 });
                dt.Rows.Add(new object[] { 4, "H", 40 });
                dt.Rows.Add(new object[] { 5, "I", 50 });
    
                ds.AcceptChanges();
                            
                DataView dv = new DataView(dt);
                dv.Sort = "Name ASC";
                                        
                dv.ListChanged += new ListChangedEventHandler(OnListChanged);
                            
                _dr = dt.Rows[4];
                
                _accept = true;
                _dr["Name"] = "C";
                _accept = false;
                            
                _dr["Name"] = "D";
                _dr["Age"] = 55;            
                            
                Console.WriteLine(dv[2][1]);                        
            } catch (Exception exc) {
                Console.WriteLine(exc);
            }
        }
        
        public static void OnListChanged(object sender, ListChangedEventArgs args)
        {
            if (_dr != null && _accept) {
                _dr.AcceptChanges();
            }
        }
    }
  2. You run the application.
In this scenario, you receive an error message that resembles the following error message:
System.NullReferenceException: Object reference not set to an instance of an object. at System.Data.DataView.IsOriginalVersion(Int32 index) at System.Data.DataRowView.get_Item(Int32 ndx) at Test.Main() in c:\Work\bugs\newbug1\Test.cs:line 42
To work around this issue, do not perform any write operations in a ListChanged event. It is best to use the RowChanged event instead of the ListChanged event.

Issue 2: The computed values in an expression column may not be updated correctly

When you try to compute the values of an expression column in a DataSet object, and the expression column is part of a relationship, the computed values of the expression column may not be updated correctly. For example, consider the following scenario:
  1. You use the following code in the application:
    using System;
    using System.ComponentModel;
    using System.Data;
    
    class Test {
        public static void Main()
        {
            try {
                DataSet ds = new DataSet();
    
                DataTable dt1 = ds.Tables.Add("T1");
                dt1.Columns.Add("CustId", typeof(int));
                dt1.Columns.Add("CustName", typeof(string));
    
                DataTable dt2 = ds.Tables.Add("T2");
                dt2.Columns.Add("EmpId", typeof(int));
                DataColumn dcEmpName = dt2.Columns.Add("EmpName", typeof(string));
                DataColumn dcMgrName = dt2.Columns.Add("MgrName", typeof(string));
                DataColumn dcReports = dt2.Columns.Add("NumberOfReports", typeof(int));
                
                DataRelation rel1 = ds.Relations.Add("T1T2", dt1.Columns["CustId"], dt2.Columns["EmpId"], false);
                DataRelation rel2 = ds.Relations.Add("T2T2", dt2.Columns["EmpName"], dt2.Columns["MgrName"], false);
    
                dcEmpName.Expression = "Parent(T1T2).CustName";
                dcMgrName.Expression = "Parent(T1T2).CustName"; 
    
                //Each person is a manager to himself.
                dcReports.Expression = "Count(Child(T2T2).EmpName)"; 
    
                AddRow(dt1, 1, "N1");
                AddRow(dt1, 2, "N2");
                AddRow(dt1, 3, "N3");
    
                AddRow(dt2, 1);
                AddRow(dt2, 2);
                AddRow(dt2, 3);
    
                Console.WriteLine(ds.GetXml());
    
                dt1.Rows[0]["CustName"] = "N4";
    
                Console.WriteLine(ds.GetXml());
            } catch (Exception exc) {
                Console.WriteLine(exc);
            }
        }
    
        public static void AddRow(DataTable dt, params object[] objArr)
        {
            Console.WriteLine("Adding row to table {0}", dt.TableName);
            dt.Rows.Add(objArr);
        }
    }
  2. You run the application.
In this scenario, you receive the following output:
<NewDataSet>
 <T1>
   <CustId>1</CustId>
   <CustName>N4</CustName>
 </T1>
 <T1>
   <CustId>2</CustId>
   <CustName>N2</CustName>
 </T1>
 <T1>
   <CustId>3</CustId>
   <CustName>N3</CustName>
 </T1>
 <T2>
   <EmpId>1</EmpId>
   <EmpName>N4</EmpName>
   <MgrName>N4</MgrName>
   <NumberOfReports>0</NumberOfReports> 
 </T2>
 <T2>
   <EmpId>2</EmpId>
   <EmpName>N2</EmpName>
   <MgrName>N2</MgrName>
   <NumberOfReports>1</NumberOfReports>
 </T2>
 <T2>
   <EmpId>3</EmpId>
   <EmpName>N3</EmpName>
   <MgrName>N3</MgrName>
   <NumberOfReports>1</NumberOfReports>
 </T2>
</NewDataSet>
In this output, the NumberOfReports element in the first T2 element contains the incorrect value of 0 instead of 1.

Issue 3: When the DataTable.Select method is called by using multiple statements, an incorrect result may be returned

When you use the Select method of a DataTable object together with the AND clause to retrieve data for multiple statements, the Select method may return an incorrect result. For example, the following code returns an incorrect result:
string filter = "(NOT ColTwo = 1) AND (ColOne = 2)";
DataTable.Select(filter);
However, the following code returns the correct result:
string filter = "NOT ColTwo = 1 AND ColOne = 2";
DataTable.Select(filter);
Additionally, consider the following scenario:
  1. You use the following code in the application:
    public static void Main()
    {
      DataTable table = new DataTable();
      table.Columns.Add("ColID", typeof(int));
      table.Columns.Add("ColOne", typeof(int));
      table.Columns.Add("ColTwo", typeof(int));
      table.Rows.Add(new object[] { 1, 1, 1 });
      table.Rows.Add(new object[] { 2, 1, 2 });
      table.Rows.Add(new object[] { 3, 2, 1 });
      table.Rows.Add(new object[] { 4, 2, 2 });
    
      string[] queries = new string[] {
          "(NOT ColTwo = 1) AND (ColOne = 2)",
          "(ColOne = 2) AND (NOT ColTwo = 1)",
    
          "NOT ColTwo = 1 AND ColOne = 2",
          "ColOne = 2 AND NOT ColTwo = 1",
    
          "NOT ColTwo = 1 AND (ColOne = 2)",
          "(ColOne = 2) AND NOT ColTwo = 1",
    
          "(NOT ColTwo = 1) AND ColOne = 2",
          "ColOne = 2 AND (NOT ColTwo = 1)",
      };
    
      Console.WriteLine("Select");
      foreach(string query in queries) {
          DataRow[] rows = table.Select(query);
          Console.WriteLine("query=\"{0}\" count={1}", query, rows.Length);
          foreach(DataRow row in rows) {
              Console.WriteLine("\t{0}, {1}, {2}", row[0], row[1], row[2]);
          }
      }
    }
    
  2. You run the application.
In this scenario, you receive the following output:
query="(NOT ColTwo = 1) AND (ColOne = 2)" count=2
        3, 2, 1
        4, 2, 2
query="(ColOne = 2) AND (NOT ColTwo = 1)" count=1
        4, 2, 2
query="NOT ColTwo = 1 AND ColOne = 2" count=1
        4, 2, 2
query="ColOne = 2 AND NOT ColTwo = 1" count=1
        4, 2, 2
query="NOT ColTwo = 1 AND (ColOne = 2)" count=2
        3, 2, 1
        4, 2, 2
query="(ColOne = 2) AND NOT ColTwo = 1" count=1
        4, 2, 2
query="(NOT ColTwo = 1) AND ColOne = 2" count=1
        4, 2, 2
query="ColOne = 2 AND (NOT ColTwo = 1)" count=1
        4, 2, 2
In this output, "(ColOne = 2)" is incorrectly displayed on the right side of an AND clause.

Issue 4: The internal index of a DataTable may become corrupted, and you receive a '13' error message

When you try to use the AcceptChanges method of a DataSet object that is used by the DataTable object, and you set a ForeignKey rule to AcceptRule.Cascade, the internal index values that are used by the DataSet object may become corrupted. This issue occurs if the following conditions are true:
  • The DataSet object contains one or more tables that have one-to-many relationships.
  • The AcceptChanges method of the DataSet object is called.
  • The AcceptRejectRule value of the DataSet object is set to Cascade. When this value is set to Cascade, the child table is changed so that it automatically either accepts data or rejects data.
For example, consider the following scenario:
  1. You use the following code in the application:
    public void Main()
    {
    			DataTable Table = new DataTable("Employee");
    			Table.Columns.Add("Id", typeof(int));
    			Table.Columns.Add("ManagerId", typeof(int));
    			Table.Columns.Add("Name", typeof(string));
    
    			Table.Columns["Name"].AllowDBNull = false;
    			Table.PrimaryKey = new DataColumn[] {Table.Columns["Id"]};
    
    			DataSet Employees = new DataSet();
    			Employees.Tables.Add(Table);
    
    			DataRelation rel = Employees.Relations.Add(Table.Columns["ID"], Table.Columns["ManagerId"]);
    			rel.ChildKeyConstraint.AcceptRejectRule = AcceptRejectRule.Cascade;
    
    			DataRow ManagerA = Table.NewRow();
    			ManagerA["ID"] = 2019;
    			ManagerA["Name"] = "Manager A";
    			Table.Rows.Add(ManagerA);
    
    			DataRow ManagerB = Table.NewRow();
    			ManagerB["ID"] = 392;
    			ManagerB["Name"] = "Manager B";
    			Table.Rows.Add(ManagerB);
    
    			DataRow EmployeeB = Table.NewRow();
    			EmployeeB["ID"] = 716;
    			EmployeeB["Name"] = "Employee of B";
    			EmployeeB.SetParentRow(ManagerB);
    			Table.Rows.Add(EmployeeB);
    
    			EmployeeB = Table.NewRow();
    			EmployeeB["ID"] = 637;
    			EmployeeB["Name"] = "2nd employee of B";
    			EmployeeB.SetParentRow(ManagerB);
    			Table.Rows.Add(EmployeeB);
    
    			Employees.AcceptChanges();
    			Table.Rows.Find(392).Delete();
    			Employees.AcceptChanges();
    }
  2. You run the application.
In this scenario, you receive the following error message:
DataTable internal index is corrupted: '13'.

Issue 5: When a Merge operation occurs, the record manager may become corrupted if the target row is in the edit state

If one or more rows in a DataTable object are being edited, and then a DataTable.Merge operation occurs or a DataSet.Merge operation occurs, the record manager for the DataSet object of the DataTable object may become corrupted.

Note When a row in a DataTable object is being edited, the DataRowVersion value of the row is set to Proposed.

For example, consider the following scenario:
  1. You use the following code in the application:
    using System;
    using System.Data;
    using System.Collections.Generic;
    using System.Text;
    
    namespace ConsoleApplication1
    {
        class Program
        {
            static void Main(string[] args)
            {
                DataSet set = new DataSet();
                DataTable table = set.Tables.Add("table");
                table.Columns.Add("C1", typeof(int));
                table.Columns.Add("C2", typeof(char));
                table.PrimaryKey = new DataColumn[] { table.Columns[0] };
                for (int i = 0; i < 26; ++i)
                {
                    table.Rows.Add(new object[] { i, (char)((ushort)'a' + i) });
                }
                table.AcceptChanges();
    
                DataSet clone = set.Copy();
                clone.Tables[0].Rows[0][1] = 'Z';
                //clone.AcceptChanges();
    
                table.Rows[0][1] = '1';
                table.Rows[0].BeginEdit();
                table.Rows[0][1] = '2';
    
    
                try
                {
                    set.Merge(clone);
                }
                finally
                {
                   foreach (DataRow row in table.Rows) {
    																	Console.WriteLine("{0}={1}", row[0], row[1]);
    															}
                }
    
            }
        }
    }
  2. You run the application.
In this scenario, the record manager for the DataSet object of the DataTable object is corrupted.

To work around this problem, make sure that there are no rows in the destination DataSet object that have the DataRowVersion value set to Proposed before you use the DataTable.Merge method or the DataSet.Merge method.

Issue 6: The internal index of a DataTable object may become corrupted, and you receive a '5' error message

The following scenarios cause corruption in a DataTable object by changing the data in the DataTable object without updating the internal indexes of the DataTable object:
  1. The DataColumn.Expression value is changed from an expression to no expression. In this scenario, all the data in the DataColumn object is set to DBNull.
  2. When the DataTable.Clear method is called, all the data in the DataTable object is removed and the indexes are updated. However, other tables that reference the DataTable object are not updated.
For example, consider the following scenario:
  1. You use the following code in the application:
    using System;
    using System.Data;
    using System.Collections.Generic;
    using System.Text;
    
    namespace ConsoleApplication1
    {
        class Program
        {
            static void Main(string[] args)
            {
                DataSet set = new DataSet("s");
                DataTable table1 = set.Tables.Add("a");
                table1.Columns.Add("C1", typeof(int));
                table1.Columns.Add("C2", typeof(int));
                table1.DefaultView.Sort = "C2";
    
                DataTable table2 = set.Tables.Add("b");
                table2.Columns.Add("C1", typeof(int));
                table2.Columns.Add("C2", typeof(int));
                table2.DefaultView.Sort = "C2";
    
                set.Relations.Add(new DataRelation("t1t2", table1.Columns[0], table2.Columns[0], false));
                table1.Columns[1].Expression = "Sum(Child(t1t2).C2)";
    
                AddData(table1, 1);
                AddData(table2, 2);
    
                table1.Columns[1].Expression = null;
    
                AddData(table2, 2);
                AddData(table1, 2);
    
            }
            private static void AddData(DataTable table, int y)
            {
                object[] x = new object[y];
                Random rand = new Random(20070125);
                for (int i = 0; i < 1000; ++i)
                {
                    switch (rand.Next(3))
                    {
                        case 0:
                        case 1:
                            for (int k = 0; k < x.Length; ++k)
                            {
                                x[k] = rand.Next(500);
                            }
                            table.Rows.Add(x);
                            break;
                        case 2:
                            if (0 < table.Rows.Count)
                            {
                                table.Rows.RemoveAt(rand.Next(table.Rows.Count));
                            }
                            break;
                    }
                }
            }
    
        }
    }
    
    
  2. You run the application.
In this scenario, you receive the following error message:
DataTable internal index is corrupted: '5'.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 932491 - Last Review: October 8, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft .NET Framework 2.0
Keywords: 
kbfix kbbug kbprb kbexpertiseinter kbexpertisebeginner kbqfe KB932491

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com