Page 322 of 728« First...102030...320321322323324...330340350...Last »

PRB: DataGrid Control Does Not Display Correctly in .aspx Page

When you view an .aspx page that contains a DataGrid control, the data grid may not appear. Alternately, only the
header of the data grid may appear, but the data grid may not contain any data.

Data Grid Does Not Appear

The data grid does not appear at all if:

  • You do not set the DataSource property of the DataGrid control. -or-
  • You do not call the DataBind method of the DataGrid control or the DataBind method of the Page object from your code.

Data Grid Header Appears But Data Grid Is Empty

The data grid header appears, but the data grid does not contain
any data if:
This problem occurs because the .aspx page retrieves the
details of the header fields from the
DataSetName.xsd file. The
DataSetName.xsd file is created for each dataset
when you generate a dataset at the design time. This file contains the
Extensible Markup Language (XML) representation of the dataset. The .aspx page
retrieves the header field details from this file. Therefore, the data grid
header appears but the data grid is empty.

Data Grid Does Not Appear

To resolve this problem, follow these steps:

  1. Set the DataSource property of the DataGrid to point to the appropriate data source. For example:

    Visual Basic

    DataGrid1.DataSource = dataSet11.Tables("Authors")
    						

    Visual C#

    DataGrid1.DataSource = dataSet11.Tables"Authors" ;
    						

    NOTE: If you programmatically retrieve the data from the data source,
    assign the data source to the DataSource property of the DataGrid.

  2. If you use the designer to add a DataAdapter to the Web form and to generate a dataset, open the DataGrid property page, and then select the appropriate DataSet or DataView object in the DataSource property.
  3. Call the DataBind method of the DataGrid control or the DataBind method of the Page object. For example:

    Visual Basic

    'Use one of the following lines.
    'Page.DataBind()
    DataGrid1.DataBind()
    						

    Visual C#

    //Use one of the following lines.
    //Page.DataBind();
    DataGrid1.DataBind();
    					

Data Grid Header Appears But Data Grid Is Empty

To resolve this problem, follow these steps:

  1. Make sure your that your data source contains data and that
    your query returns data.
  2. Use a DataAdapter to fill the dataset. For example:

    Visual Basic

    sqlDataAdapter1.Fill(dataSet11, "Authors")
    						

    Visual C#

    sqlDataAdapter1.Fill(dataSet11,"Authors");
    					

This
behavior is by design.
You must bind the DataGrid Web server control to a data source through the DataSource property of the DataGrid to correctly render the data grid on the page. After you set the
data source, you must also explicitly call the DataBind method of the DataGrid control or the DataBind method of the Page object from your code.

Steps to Reproduce the Behavior

Data Grid Does Not Appear

  1. Create a new ASP.NET Web Application project in Visual
    Basic .NET or Visual C# .NET.
  2. Drag a DataGrid control from the toolbox, and drop the control onto the
    form.
  3. In the designer, double-click the .aspx page to open the
    code-behind window. Add the following code to the top of the code-behind window
    to add the required namespace references:

    Visual Basic

    Imports System.Data
    Imports System.Data.SqlClient
    						

    Visual C#

    using System.Data.SqlClient;
    					

  4. Replace the code in the Form_Load event with the following code:

    Note You must change uid = and
    pwd = to the correct values before you run this code. Be
    sure that UID has the appropriate permissions to perform this operation on the
    database.

    Visual Basic

    Private Sub Page_Load(ByVal sender As System.Object, _
    ByVal e As System.EventArgs) Handles MyBase.Load
         'Write code to access the database.
         Dim myConnection As New SqlConnection("server=(local);database=pubs;uid=;pwd=")
         Dim myDataAdapter As New SqlDataAdapter("select * from authors", myConnection)
         Dim myDataSet As New DataSet()
         myConnection.Open()
         myDataAdapter.Fill(myDataSet)
    
        'Uncomment the following line to resolve this problem.
        'DataGrid1.DataSource = myDataSet
        DataGrid1.DataBind()
    End Sub
    						

    Visual C#

    private void Page_Load(object sender, System.EventArgs e)
    
    //Write code to access the database.
    SqlConnection myConnection = new SqlConnection("server=(local);database=pubs;uid=;pwd=");
    SqlDataAdapter myDataAdapter = new SqlDataAdapter("select * from authors", myConnection);
    DataSet myDataSet = new DataSet();
    myConnection.Open();
    myDataAdapter.Fill(myDataSet);
    
    //Uncomment the following line to resolve this problem.
    //DataGrid1.DataSource = myDataSet;
    DataGrid1.DataBind();
    

  5. Modify the connection string as appropriate for your
    environment.
  6. Build the project, and then view the .aspx page in the
    browser. Notice that data grid does not appear.

Data Grid Header Appears But Data Grid Is Empty

  1. Create a new ASP.NET Web Application project in Visual
    Basic .NET or Visual C# .NET.
  2. Drag a DataGrid control from the toolbox, and drop the control onto the
    form.
  3. Add a SqlDataAdapter control to the Web form. Complete the following steps in the
    DataAdapter Configuration Wizard to set the connection properties:

    1. Click New Connection to create a new connection to your Microsoft SQL Server database.
      Select the server, type the logon information, and then select the Pubs
      database.
    2. Under Query type, click SQL Statements, and then click Next.
    3. Type the following SQL statement:
    4. Click Finish.
  4. Right-click the DataAdapter, and then click Generate Dataset.
  5. Set the DataSource property of the DataGrid to the dataset that is generated.
  6. In the designer, double-click the .aspx page to open the
    code-behind window. Add the following code to the Page_Load event:

    Visual Basic

    Visual C#

  7. Build the project, and then view the .aspx page in the
    browser. Notice that the header of the data grid appears, but the data grid
    does not contain any data.
For more information about the DataGrid control and for samples that use this control, refer to the
following Microsoft Web sites:

Article ID: 313156 – Last Review: July 25, 2012 – Revision: 4.0


Applies to
  • Microsoft ASP.NET 1.0
  • Microsoft ASP.NET 1.1
kbdatabinding kbprb kbservercontrols KB313156

See original article:
PRB: DataGrid Control Does Not Display Correctly in .aspx Page

PRB: DataGrid Does Not Automatically Generate UniqueIdentifier Fields with AutoGenerateColumns=True

When you use the DataGrid Web server control in your .aspx pages, corresponding columns are not generated automatically for fields of type UniqueIdentifier. This behavior occurs when the AutoGenerateColumns property for the DataGrid is set to True.
When you set AutoGenerateColumns=True, DataGrid internally creates a collection of autogenerated columns. If the data type of a field is not one of Primitive, String, Decimal, or DateTime, DataGrid does not generate a column for that field. Because the UniqueIdentifier data type is actually a System.GUID type, DataGrid excludes this field while generating columns. For this reason, you do not see UniqueIdentifier column when the DataGrid is displayed on the .aspx page.
To work around this behavior, use one of the following methods. Both methods involve explicitly creating a bound column for fields of type UniqueIdentifier.

NOTE: You do not need to turn off the AutoGenerateColumns property. If you do turn it off, you must create every column explicitly. Otherwise, new columns that you create are added to the DataGrid in conjunction with autogenerated columns.

Method 1: Create a Column for UniqueIdentifier Field at Run Time and Add the Column to the Columns Collection

  1. Create a new BoundColumn, and then set the DataField and HeaderText properties.
  2. Add the column to the Columns collection of the DataGrid.

This workaround is more useful if you do not know which fields are returned from the DataSource. In this case, you can loop through the results from the DataSource and create a column for each field on the fly. Use the following code to achieve this:

Microsoft Visual Basic .NET

   Dim myBoundColumn As New BoundColumn()
   myBoundColumn.DataField = "UniqueIdentifierA"
   myBoundColumn.HeaderText = "UniqueIdentifierA"
   DataGrid1.Columns.Add(myBoundColumn)
				

Microsoft Visual C# .NET

   BoundColumn myBoundColumn = new BoundColumn();
   myBoundColumn.DataField = "UniqueIdentifierA";
   myBoundColumn.HeaderText = "UniqueIdentifierA";
   DataGrid2.Columns.Add(myBoundColumn);
				

Method 2: Define a BoundColumn Template

If you know which fields are returned from the DataSource, you can create BoundColumn templates for the fields of type UniqueIdentifier. You must specify the DataField attribute
as the field name that you want to display. The following sample code defines a DataGrid with a BoundColumn template for the UniqueIdentifier field:

   
        
	   
        
   
				

This behavior is by design.
Currently, the DataGrid does not automatically generate columns for the following SQL data types. Also, you can use either of the preceding workarounds for these types:
  • Binary
  • Image
  • Sqlvariant
  • Timestamp
  • Uniqueidentifier
  • Varbinary

Steps to Reproduce the Behavior

NOTE: You must have a table that contains one or more fields of type UniqueIdentifier or any of the SQL data types mentioned in the “More Information” section of this article. Make sure that you have some data in that table.

  1. Create a new ASP.NET Web application by using Microsoft Visual Basic .NET or Microsoft Visual C# .NET.
  2. Drag a DataGrid control from the Toolbox onto the Web form.
  3. Drag a SQLDataAdapter control onto the Web form. Follow these steps in the DataAdapter Configuration Wizard to set the connection properties:
    1. Click New Connection to create a new connection to your SQL database. Select the server, the logon information, and the database that you want.
    2. Under Choose a Query type, select SQL Statements, and then click Next. Type the following SQL statement. Replace mytable with the name of the table that contains a UniqueIdentifier column:
    3. Click Finish.
  4. Right-click DataAdapter, and then click the Generate Dataset command.
  5. Set the DataSource property of the DataGrid to the generated DataSet.
  6. In the Designer, double-click the .aspx page to go to the Code-behind window. In the page_Load event, paste the following code. Replace mytable with your table name.

    Microsoft Visual Basic

       sqlDataAdapter1.Fill(dataSet11, "mytable")
       DataGrid1.DataBind()
    					

    Microsoft C#

       sqlDataAdapter1.Fill(dataSet11,"mytable");
       DataGrid1.DataBind();
    					

  7. Build the project, and then view the .aspx page in the browser. Notice that DataGrid does not display a column for the UniqueIdentifier field.
For more information, visit the following Microsoft Web sites:

Article ID: 313155 – Last Review: July 25, 2012 – Revision: 3.0


Applies to
  • Microsoft ASP.NET 1.1
  • Microsoft ASP.NET 1.0
kbdatabase kbdatabinding kbprb kbservercontrols KB313155

Read More:
PRB: DataGrid Does Not Automatically Generate UniqueIdentifier Fields with AutoGenerateColumns=True

How to loop through and examine CheckBox control values in a DataGrid column by using ASP.NET and Visual C# .NET

This article was previously published under Q320707

This step-by-step article demonstrates how to loop through each row of an ASP.NET DataGrid control and how to determine if the ASP.NET CheckBox server control that is used to identify the row has been selected.

The sample code in this article uses the Microsoft SQL Server Northwind database to populate the DataGrid control and then adds a CheckBox server control to the initial column for each row. This is a common technique that allows users to select multiple, specific rows in a DataGrid.

Requirements

  • Microsoft Windows 2000 Professional, Windows 2000 Server, Windows 2000 Advanced Server, or Windows XP Professional
  • Microsoft .NET Framework
  • Microsoft Internet Information Services (IIS)
  • Microsoft Visual Studio .NET

Create an ASP.NET Web application by using Visual C# .NET

  1. Start Microsoft Visual Studio .NET.
  2. On the File menu, point to New, and then click Project.
  3. In the New Project dialog box, click Visual C# Projects under Project Types, and then click ASP.NET Web Application under Templates.
  4. In the Location box, replace the WebApplication# default name with MyWebApp. If you are using the local server, you can leave the server name as http://localhost. The resulting Location box appears as follows:

    http://localhost/MyWebApp

Create the sample Web Form page

  1. Add a new Web Form to the ASP.NET Web application as follows:
    1. Right-click the project node in Solution Explorer, point to Add, and then click Add Web Form.
    2. In the Name box, type MySample.aspx, and then click Open.
  2. In the Properties window, change the pageLayout property for the document to FlowLayout. Although you do not have to do this to use the sample code, this will make the presentation appear cleaner.
  3. Add a DataGrid, a Button, and a Label server control to the page as follows:
    1. Drag an ASP.NET DataGrid server control from the Web Forms toolbox onto the page.
    2. In the Properties window, change the ID of the DataGrid control to DemoGrid.
    3. Drag an ASP.NET Button server control from the Web Forms toolbox onto the page below the DataGrid.
    4. In the Properties window, change the ID of the Button control to GetSelections, and then change the Text property to Get Selections.
    5. Drag an ASP.NET Label server control from the Web Forms toolbox onto the page below the Button control.
    6. In the Properties window, change the ID of the Label control to ResultsInfo, and then delete any text in the Text property.
  4. Switch to HTML view in the editor. Add the code to the default DataGrid template to construct the columns. The resulting code for the control should appear as follows:
    
    	
    	
    	
    	
    	
    	
    	
    
    					

  5. Right-click the page, and then click View Code. This opens the code-behind class file in the editor. Add the following namespace references to the code-behind class file:
    using System.Data.SqlClient;
    using System.Text;
    					

  6. Replace the existing code for the Page_Load event handler with the following code:
    private void Page_Load(object sender, System.EventArgs e)
    
    	if(!IsPostBack)
    
    		//Create a SqlConnection object.
    		//Modify the connection string as necessary for your environment.
    		SqlConnection cn = new SqlConnection("Server=localhost;database=Northwind;UID=sa;PWD=");
    
    		SqlCommand cmd = new SqlCommand("SELECT * FROM Customers",cn);
    		cn.Open();
    		SqlDataReader reader = cmd.ExecuteReader();
    		DemoGrid.DataSource = reader;
    		DataBind();
    		reader.Close();
    		cn.Close();
    
    }
    					

  7. Switch to Design view, and then double-click GetSelections. This opens the code-behind class file in the editor. Replace the existing code in the GetSelections_Click event handler with the following code:
    private void GetSelections_Click(object sender, System.EventArgs e)
    
    	int rowCount = 0;
    	StringBuilder gridSelections = new StringBuilder();
    
    	//Loop through each DataGridItem, and determine which CheckBox controls
    	//have been selected.
    	foreach(DataGridItem DemoGridItem in DemoGrid.Items)
    
    		CheckBox myCheckbox = (CheckBox)DemoGridItem.Cells0.Controls1;
    		if(myCheckbox.Checked == true)
    
    			rowCount++;
    			gridSelections.AppendFormat("The checkbox for 0 was selected",
    						DemoGrid.DataKeysDemoGridItem.ItemIndex.ToString());
    		}
    	}
    	gridSelections.Append("
    
    "); gridSelections.AppendFormat("Total number selected is: 0", rowCount.ToString()); ResultsInfo.Text = gridSelections.ToString(); }

Verify that it works

  1. On the File menu, click Save All to save the Web Form and other files that are associated with the project.
  2. On the Build menu in the Visual Studio .NET integrated development environment (IDE), click Build Solution.
  3. In Solution Explorer, right-click the Web Form page (MySample.aspx), and then click View in Browser. Notice that the page displays the data in the grid. Additionally, a check box appears in the first column of each row. The user can click to select this check box to mark specific rows.
  4. Click to select a few of the check boxes for the rows, and then click Get Selections.

    After the page makes a round trip to the server and executes the code in the GetSelections_Click event handler, a list of the items that you selected in the previous step appears. The code in the GetSelections_Click event handler loops through each DataGridItem in your ASP.NET DataGrid server control, determines whether the Checked property of the related CheckBox control is true, and then records the associated key value at that specific position for the DataKeys of the DataGrid.

For more information about the DataGrid control, click the following article number to view the article in the Microsoft Knowledge Base:

306227

(http://support.microsoft.com/kb/306227/
)

How to use a CheckBox Web control in a DataGrid in Visual Studio .NET

For more information about the DataGrid control and for samples that use this control, visit the following MSDN Web sites:

Article ID: 320707 – Last Review: July 25, 2012 – Revision: 5.0


Applies to
  • Microsoft ASP.NET 1.1
  • Microsoft ASP.NET 1.0
  • Microsoft Visual C# .NET 2003 Standard Edition
  • Microsoft Visual C# .NET 2002 Standard Edition
kbhowtomaster kbservercontrols KB320707

Other Support Sites

Community

Get Help Now

Article Translations

Read the original:
How to loop through and examine CheckBox control values in a DataGrid column by using ASP.NET and Visual C# .NET

HOW TO: Create a Summary Row for a DataGrid in ASP.NET by Using Visual C# .NET

This step-by-step article describes how to create a summary row for a DataGrid control in ASP.NET.

In this article, you create a Visual C# .NET project, add code to access the Sales Totals by Amount view from the Northwind database, and then bind the Sales Totals by Amount view to the DataGrid. This sample uses the ItemDataBound event of the DataGrid to total the SaleAmount field when you bind the data to the DataGrid. This sample also uses the footer of the DataGrid to display the summary or the totals.

Requirements

The following list outlines the recommended hardware, software, network infrastructure, and service packs that are required:

  • Microsoft Windows 2000 Professional, Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, or Microsoft Windows XP
  • Microsoft .NET Framework
  • Microsoft Visual Studio .NET
  • Microsoft Internet Information Services (IIS)
  • Microsoft SQL Server 7.0 or later and the Northwind database

NOTE: The Northwind is included with Microsoft SQL Server 7.0 and later.

Create a Visual C# .NET Project and Add the DataGrid

In this section, you create a Visual C# .NET project, select a format for the DataGrid, and then set the DataGrid to display the footer. Because you use the footer to display the summary, it is important that you display the footer.

NOTE: By default, the ShowFooter property is turned off.

  1. Start Visual Studio .NET. The Visual Studio .NET IDE appears.
  2. On the File menu, point to New, and then click Project.
  3. In the New Project dialog box, click Visual C# Projects under Project Types, and then click ASP.NET Web Application under Templates.
  4. In the New Project dialog box, notice that the Name box is unavailable (it appears dimmed). The Location box contains the following text (or similar):

    http://localhost/WebApplication1

    Change the location to http://localhost/SummaryRow, and then click OK. A new project is created, which includes a Web Form that is named WebForm1.aspx.

  5. In Solution Explorer, double-click WebForm1.aspx.
  6. Drag a DataGrid control from the toolbox to the form.
  7. Right-click DataGrid, and then click Auto Format. Click Colorful 1, and then click OK.
  8. Right-click DataGrid, and then click Properties. In the Properties dialog box, change the value of the ShowFooter property to True.

Write Code to Access the Database

In this section, you use the Sales Totals by Amount view that is located in the Northwind database to calculate the summary for the SaleAmount field. The Sales Totals by Amount view includes the Orders, the CompanyName, and the SaleAmount fields.

  1. In the Visual Studio .NET IDE, right-click the Web Form, and then click View Code.
  2. In the code-behind window, add the following code to the top of the page:
    using System.Data.SqlClient;
    					

  3. Add the following code in the class declaration section:
    private double myTotal;  //This variable tracks the running total.
    					

  4. Replace the code in the Page_Load event with the following code:
    private void Page_Load(object sender, System.EventArgs e)
    
       //Connect to the database, retrieve data, and then fill the data in the  DataSet.
      SqlConnection myConnection = new SqlConnection("server=(local);uid=sa;" +
                   "pwd=password;database=northwind");
      SqlDataAdapter myDataAdapter = new SqlDataAdapter("SELECT top 15 OrderID, CompanyName, " +
                   "SaleAmount  FROM Northwind.dbo.Sales Totals by Amount",   myConnection);
      DataSet myDataSet = new DataSet();
      myDataAdapter.Fill(myDataSet);
    
      //Set the DataSource for the DataGrid, and then bind the data.
      DataGrid1.DataSource = myDataSet;
      DataGrid1.DataBind();
    

  5. Modify the connection string as appropriate for your environment.
  6. Expand the “Web Form Designer generated code” region, and then add the following statement in the InitializeComponent function:
    this.DataGrid1.ItemDataBound += new System.Web.UI.WebControls.DataGridItemEventHandler(this.DataGrid1_ItemDataBound);
    					

Use the ItemDataBound Event

The ItemDataBound event is raised after an item is data bound to the DataGrid control. This event gives you with the last opportunity to access the data item before it appears on the client. After this event is raised, the data item is null and is no longer available.

For each item that is data bound, you must check the ItemType property. If ItemType is of type Item or AlternatingItem, you receive the value from the last cell of the item, which contains the SaleAmount value. In this sample, you add this value to the running summary variable. When the ItemType is Footer, you receive the total from all of the rows. Therefore, you assign the value of the summary variable to the text value of the last cell.

NOTE: This code uses formatting expressions to provide a uniform look for the SaleAmount data.

Add the following code after the Page_Load event:

private void DataGrid1_ItemDataBound(object sender, System.Web.UI.WebControls.DataGridItemEventArgs e )

  switch ((int)(e.Item.ItemType))

    case (int)ListItemType.Item :
    case (int)ListItemType.AlternatingItem:
         //Calculate total for the field of each row and alternating row.
         myTotal += Convert.ToDouble(e.Item.Cells2.Text);
	 //Format the data, and then align the text of each cell to the right.
	e.Item.Cells2.Text = Convert.ToDouble(e.Item.Cells2.Text).ToString("##,##0.00");
	e.Item.Cells2.Attributes.Add("align", "right");
	break;
    case (int)ListItemType.Footer:
	//Use the footer to display the summary row.
	e.Item.Cells1.Text = "Total Sales";
	e.Item.Cells1.Attributes.Add("align", "left");
	e.Item.Cells2.Attributes.Add("align", "right");
	e.Item.Cells2.Text = myTotal.ToString("c");
	break;

}
				

Build the Project and Test the Code

  1. On the File menu, click Save All.
  2. On the Build menu, click Build Solution.
  3. In Solution Explorer, right-click the .aspx page, and then click View in Browser. The .aspx page appears in the browser, and the DataGrid displays the OrderID, the CompanyName, and the SaleAmount columns. Notice that the footer displays the total of the SaleAmount column.

For more information, visit the following Microsoft Web sites:

Article ID: 326339 – Last Review: July 25, 2012 – Revision: 4.0


Applies to
  • Microsoft ASP.NET 1.1
  • Microsoft ASP.NET 1.0
  • Microsoft Visual C# .NET 2003 Standard Edition
  • Microsoft Visual C# .NET 2002 Standard Edition
kbcodesnippet kbdatabinding kbevent kbhowtomaster kbservercontrols KB326339

View the original here:
HOW TO: Create a Summary Row for a DataGrid in ASP.NET by Using Visual C# .NET

Troubleshooting Office Kernel32.dll errors under Windows 95

This article contains information about troubleshooting and eliminating
invalid page faults that occur in module Kernel32.dll when you work with a
Microsoft Office program under Microsoft Windows 95. When a Kernel32.dll
error message appears, a message similar to the following appears

caused an invalid page fault in module Kernel32.dll

where is the name of the program you are using.

When an invalid page fault occurs, an unexpected event occurs in the
Microsoft Windows operating system. An invalid page fault typically
indicates that a program improperly attempted to use random access memory,
for example, when a program or a Windows component reads or writes to a
memory location that is not allocated to it. When this occurs, the program
can potentially overwrite and corrupt other program code in that area of
memory.

An invalid page fault may occur when parameters are passed between programs
and the Windows 95 operating system. An invalid parameter may cause a
program to execute invalid instructions, which results in an invalid page
fault. This behavior usually occurs because a program incorrectly passes
data that Windows or a Windows-based program cannot interpret.

It is important that you follow the steps in each of the sections in this
article in the order in which they are presented. Because invalid page
faults are typically caused when two or more programs interact, skipping
steps may prolong identifying the problem.

Determine Whether the Problem Is Documented

Many Kernel32.dll errors are already documented in the Microsoft Knowledge
Base and have solutions. For more information, query on the following words
in the Microsoft Knowledge Base:

“invalid page fault” kernel32.dll

NOTE: It may be helpful to add the program name in which the problem occurs
at the end of the query to narrow your search.

For additional information on related kernel32.dll error messages, please
see the following articles in the Microsoft Knowledge Base:

162398

(http://support.microsoft.com/kb/162398/EN-US/
)

First Aid 97 causes invalid page fault

166125

(http://support.microsoft.com/kb/166125/EN-US/
)

Problems with Millennium and Mystique video cards when you use Office 97 programs

162153

(http://support.microsoft.com/kb/162153/EN-US/
)

Problems after returning computer from suspended state

Do Not Install Clipart, Binder and Find Fast

It has been reported that on some systems, when you encounter this error
message during setup of Microsoft Office 97, bypassing installation of
Clipart, Binder and Find Fast bypasses the Kernel32.dll error message.
These components are installed by default with a Typical or Custom
installation. You must perform a Custom installation and choose to not
install these components. To do this, follow these steps:

  1. Quit all programs.
  2. On the Windows Start menu, click Run.
  3. Type in the following syntax to start Setup

    :Setup

    where is the drive letter you are installing from. So if
    you install from a CD-ROM drive (usually drive D), the syntax would
    look like this:

    D:Setup

  4. Proceed through Setup as you normally would, but select Custom as the
    installation type.
  5. Click Office Tools, and then click Change Option.
  6. Click to clear the Clipart Gallery, Popular Clipart and Find Fast
    check boxes, and then click OK.
  7. Click to clear the Microsoft Binder check box. Click Continue. Proceed
    through the rest of Microsoft Office 97 Setup as you normally would. If
    the Setup program completes without error, you can install Clipart,
    Binder and Find Fast by running Setup in maintenance mode.

Start Windows in Safe Mode

Windows 95 has a built-in troubleshooting mode called Safe mode. It
bypasses startup files and uses only basic system drivers, including basic
networking. When you start Windows in Safe mode, Windows uses only the
mouse, keyboard, and standard video graphics adapter (VGA) device drivers.
This makes Safe mode useful for isolating and resolving error conditions
that are caused by both real-mode and Windows-based drivers. Windows 95
also has troubleshooting features that may help you identify the problem.
To start Windows 95 in Safe mode and make the additional troubleshooting
features available, follow these steps:

  1. In the Control Panel, double-click the System icon, and then click the
    Performance tab.
  2. Click File System, and then click the Troubleshooting tab.
  3. Click the following check boxes to select them:

    Disable protect-mode hard disk interrupt handling
    Disable synchronous buffer commits
    Disable all 32-bit protect-mode disk drivers
    Disable write-behind caching for all drive

  4. Click OK, click Close, and then click Yes.
  5. Press F8 when you see the “Starting Windows 95″ message.
  6. On the Windows Startup menu, select option 3 (Safe Mode).
  7. After Windows 95 is running again, perform the same operation that
    caused the error.

When you use Safe mode or when you disable 32-bit protected-mode disk
drivers, Windows 95 does not process protected-mode drivers, the
Autoexec.bat file, and the Config.sys file. Therefore, the CD-ROM drive is
not available. To use Safe mode with CD-ROM drive support, determine
whether Windows 95 uses protected-mode drivers for the CD-ROM drive. If
Windows 95 is using protected mode drivers, install the real-mode (MS-DOS)
drivers for the CD-ROM drive on the computer. The real-mode drivers are
usually located on a disk that is shipped with the CD-ROM drive or with the
computer. The drivers are installed in the Autoexec.bat and Config.sys
files.

For additional information on determining if Windows 95 is using protected-
mode drivers, please see the following article in the Microsoft Knowledge
Base:

151634

(http://support.microsoft.com/kb/151634/EN-US/
)

Protected-Mode CD-ROM drive support in Windows 95

For additional information on installing real-mode drivers for the
CD-ROM, please see the following article in the Microsoft Knowledge Base:

167069

(http://support.microsoft.com/kb/167069/EN-US/
)

Installing Real Mode CD-ROM Drivers for Office Installation

Disable the CD-ROM Drive Cache

If the error message appears while you are reading from a CD-ROM drive, try
disabling the CD-ROM drive cache. This may make the drive more reliable but
reduce performance. To disable the CD-ROM drive cache, follow these steps:

  1. In Control Panel, double-click System.
  2. Click the Performance tab and click File System.
  3. Click the CD-ROM tab, click No Read-Ahead in the “Optimize access
    pattern for” list.
  4. Verify that the Supplemental Cache Size slider is positioned in the far
    left position (the Small setting), and then click OK.

If you are using real-mode CD-ROM drive drivers, the drive may be cached by
the Smartdrv.exe program. If this is the case, remark the line from the
Autoexec.bat by typing “REM” (without the quotation marks) at the beginning
of the line.

Check for Registry Corruption

When you start Windows 95 in Safe mode, Windows does not read the entire
registry. Therefore, damage to the registry may not be evident when you run
Windows in this mode. It may be necessary to replace the existing registry
(System.dat) with a backup to determine whether the problem is caused by a
damaged registry. To troubleshoot a damaged registry, follow these steps:

  1. Restart the computer. When the “Starting Windows 95″ message appears,
    press F8.
  2. On the Windows Startup menu, select option 6 (Command Prompt Only).
  3. To remove the file attributes from the backup of the registry, type the
    following command, and then press ENTER.:

    c:windowscommandattrib -h -s -r c:system.1st

  4. To remove the file attributes from the current registry, type the
    following command, and then press ENTER:

    c:windowscommandattrib -h -s -r c:windowssystem.dat

  5. To rename the registry, type the following command, and then press
    ENTER:

    ren c:windowssystem.dat *.dax

  6. To copy the backup file to the current registry, type the following
    command, and then press ENTER:

    copy c:system.1st c:windowssystem.dat

  7. Restart the computer. If the Windows 95 Startup Menu displays, choose
    Safe Mode, or Safe Mode With Network Support if you need network
    connectivity.

NOTE: The System.1st file is a backup of the registry that is created
during the final stage of a Microsoft Windows 95 installation. Therefore,
the “Running Windows 95 for the first time” banner appears, and Windows 95
finalizes settings as if you reinstalled it.

If replacing the System.dat file with the System.1st file resolves the
issue, the problem may be related to registry damage. Note that you may
have to reinstall programs and device drivers that you installed after you
installed Windows 95 to update the new registry.

If the issue is not resolved, restore the original registry. To do this,
follow these steps:

  1. Restart the computer. When the “Starting Windows 95″ message appears,
    press F8.
  2. On the Windows Startup menu, select option 6 (Command Prompt Only).
  3. Type the following commands:
    c:windowscommandattrib -s -h -r c:windowssystem.dat

    copy c:windowssystem.dax c:windowssystem.dat

  4. Restart the computer.

For additional information on resolving registry errors, please see the
following article in the Microsoft Knowledge Base:

131431

(http://support.microsoft.com/kb/131431/EN-US/
)

How to troubleshoot registry errors in Windows 95

The steps listed in this section are also known to resolve the following
error message:

Fatal Exception 0E @ 0028:C025C32F in VXD.VMM (06)

Check for a Valid Temporary Folder and Excess Temporary Files

There should be at least 3 megabytes (MB) of free space on the hard disk
that contains the temporary folder. To check for a temporary folder and
delete excess files from that folder, follow these steps:

  1. Close any running programs and restart your computer by clicking
    Shutdown on the Start menu and clicking Restart Your Computer (Microsoft
    Windows 95) or Restart (Under Windows NT). Press F8 when you see the
    “Starting Windows 95″ message, and then choose “Safe mode command prompt
    only.”
  2. Type set and press ENTER. Note the
    location of the TEMP variable.
  3. Change to the folder you noted in step 2. For example, if TEMP is set
    to C:WINDOWSTEMP, type the following line and then press ENTER:

    cdwindowstemp

    If the folder you noted in step 2 does not exist, create the folder. For
    example, you can create a temporary folder called win95tmp on drive C by
    typing the following line at the command prompt:

    md c:win95tmp

  4. Delete any temporary files in this folder. Temporary files typically
    have a .tmp file name extension. To delete these files, type the
    following line, and then press ENTER:

    del *.tmp

    NOTE: Do not delete these files from within the Windows 95 graphical
    user interface (that is, when you are running Windows 95) because
    Windows 95 or a Windows program may be using one of these files.

Check the Hard Disk for Disk Errors and Fragmentation

Use the ScanDisk program to check the hard disk for lost clusters and other
file allocation table (FAT) errors and to test the hard disk integrity. You
can also use the ScanDisk program to repair any of these problems. To run
ScanDisk, follow these steps:

  1. On the Start menu, point to Programs.
  2. Point to Accessories, point to System Tools, and then click ScanDisk.

Hard disks that are very fragmented can affect the performance and
reliability of Microsoft Office programs and other tasks in Windows 95. To
resolve this problem, run Disk Defragmenter to defragment the hard disk. To
run Disk Defragmenter, follow these steps:

  1. On the Start menu, point to Programs.
  2. Point to Accessories, point to System Tools, and then click Disk
    Defragmenter.

Verify That the Compact Disc Is Clean and Unscratched

If the error message appears while you are installing from a compact disc,
verify that the compact disc you are using is clean. You can wipe the
compact disc with a soft, lint-free cloth. Also ensure that there are no
large scratches on the compact disc. If the compact disc is damaged and
unreadable, error messages may appear during installation.

Check for a Corrupted Swap File

The Kernel32.dll error may also appear if your Windows swap file is
corrupted. To create a new swap file, restart the computer in MS-DOS mode,
delete the Win386.swp file in the Windows folder, and then restart the
computer. To create a new swap file, follow these steps:

  1. On the Start menu, click Shut Down.
  2. In the Shut Down Windows dialog box, click “Restart the Computer in
    MS-DOS Mode,” and then click Yes.
  3. At the MS-DOS prompt, switch to the Windows folder by typing the
    following command:

    cd :Windows

    where is the drive letter that contains the Windows folder.

    Typically, is C.

    NOTE: The swap file exists in the Windows folder if Windows manages
    virtual memory settings on your computer. If you chose to manage
    virtual memory settings on the computer, the swap file exists at the
    root level of the hard disk. To determine whether Windows manages
    virtual memory settings, right-click My Computer, click Properties,
    click Performance, and then click Virtual Memory.

  4. To delete the swap file, type the following:

    del Win386.swp

  5. After you delete the swap file, restart the computer.

Corrupted Custom Profile

Corrupted custom profiles have also been known to cause Kernel32.dll
errors. Deleting and recreating the profile can possibly resolve this
problem.

If you are using the Microsoft Office 97 system policy templates that are
included in the Microsoft Office 97 Resource Kit, you must use the version
of the System Policy Editor that is included in the Microsoft Office 97
Resource Kit or the Microsoft Windows NT 4.0 Resource Kit.

NOTE: You can download Policy.exe, a self-extracting executable file
containing Poledit.exe, from online services. Download this file from the
following Web site:

NOTE: Because the Microsoft Web site is regularly updated, the site
address may change without notice. If this occurs, link to the
Microsoft home page at the following address:

Disable Enhanced BIOS Features

Most computers have several enhanced settings that allow the computer to
fully use the computer hardware. These high-speed settings can cause
the system to become unstable; disabling these features may make the
computer more stable. Contact your computer manufacturer for information
about entering the basic input/output system (BIOS) and changing the BIOS
settings. You can enter the BIOS on most systems immediately after turning
on the power. Usually a keystroke (such as DEL) is required to enter the
BIOS. Below are the common features that can interfere with Microsoft
Office programs:

Memory Shadow RAM
Video Shadow RAM
Internal Cache
External Cache
Built-in Virus Protection

Newer chipsets may have more advanced features (such as memory wait states)
that may cause errors. Most BIOS installation programs have an option to
load the BIOS default settings. This option usually disables all advanced
features.

WARNING: Incorrectly altering hardware BIOS settings can cause serious
problems that may cause your computer to fail to start or function
properly. Microsoft cannot guarantee that problems that result from the
incorrect setting of hardware BIOS options can be solved. Alter the
hardware BIOS settings at your own risk.

Customers have reported that the Dell A02 BIOS does not work with Windows
95. This BIOS version is used on the Dell Dimension models. Dell technical
support can be contacted at (800) 624-9896.

Disabling the External Cache feature on Tyan Titan III VX and Tyan Tomcat
III motherboards has been known to resolve Kernel32.dll error messages.
Similar problems have also been reported when using Gigabyte motherboards.

Remove and Reinstall the Program

If the problem occurs after you run the Setup program, some of the dynamic
link library (DLL) files may be damaged or corrupted. To troubleshoot this
problem, first completely remove the program. For additional information,
please see the following articles in the Microsoft Knowledge Base:

158658

(http://support.microsoft.com/kb/158658/EN-US/
)

How to completely remove Microsoft Office 97

176823

(http://support.microsoft.com/kb/176823/EN-US/
)

Utility to completely remove remaining Office 97 files
and registry entries

133274

(http://support.microsoft.com/kb/133274/EN-US/
)

Setup “Remove All” doesn’t remove all files

After you completely remove the program, reinstall the program.

Check for Software Updates

Outdated and incompatible software may also cause error messages to appear.
Check with the manufacturer of the computer for various software updates,
such as BIOS updates, OEM Windows updates, and hardware driver updates
(such as CD-ROM drive drivers). If you are using third-party partitioning
software (for example, EZDrive, or Ontrack Disk Manager), verify that you
have the most recent versions of these products.

The third-party products discussed here are manufactured by vendors
independent of Microsoft; we make no warranty, implied or otherwise,
regarding these products’ performance or reliability.

Microsoft released three updated files that may affect whether you receive
error messages when you run Setup or when you use a Microsoft Office
program. Download the Windows 95 Service Pack 1, the Kernel32.dll update,
and the Ole32.dll updates from the Microsoft Web Site. Also, determine
whether other updates that may pertain to your system configuration are
available. To check for updated files on the Microsoft Web site, use the
following address:

NOTE: Because the Microsoft Web site is regularly updated, the site
address may change without notice. If this occurs, link to the Microsoft
home page at the following address:
For more information about hardware and software vendor contact information, visit the following Microsoft Web site:
-

Scan the Computer for Viruses

If a virus is present on your computer and has damaged some files,
Kernel32.dll error messages may appear when you use a program. Scan the
hard disk and floppy disks with a virus detector. If the virus detector
finds a virus on your computer, remove the virus before you run the Office
program again. If a virus is found on your Setup disk, you must obtain a
new set of disks.

NOTE: Do not run a virus detector terminate-and-stay-resident (TSR) program
while you run any of the Microsoft Office programs, including the Setup
program. Run a virus detector before you run the Setup program, and then
disable it.

For additional information, please see the following article in the
Microsoft Knowledge Base:

135648

(http://support.microsoft.com/kb/135648/EN-US/
)

Troubleshooting Win95 application floppy disk problems

If you determine that you have a Setup disk that was damaged by a virus,
you can order a new set of disks. To obtain replacement disks, call the
Microsoft Order Desk at (800) 360-7561 and request a replacement set of
disks. If you are outside the United States, contact the Microsoft
subsidiary for your area. To locate your subsidiary, see the Microsoft
World Wide Offices Web page at:
IMPORTANT: Microsoft Office 97 Service Release CD-ROMs and replacement CD-ROMs are no longer available from Microsoft.

For more information about obtaining the Microsoft Office 97 Service Release 1 (SR-1) and Microsoft Office 97 Service Release 2 (SR-2), click the following article number to view the article in the Microsoft Knowledge Base:

192874

(http://support.microsoft.com/kb/192874/
)

An overview of Microsoft Office 97 Service Release 2 (SR-2)

Reinstall Windows in a New Folder

Use this method only after you try all of the troubleshooting steps in this
article. If you reinstall Windows in a new folder, you must reinstall all
Windows-based programs under the new Windows 95 installation.

For additional information, please see the following article in the
Microsoft Knowledge Base:

178400

(http://support.microsoft.com/kb/178400/EN-US/
)

Installing Windows 95 to new folder to troubleshoot Office problems

Check Hardware

If you exhaust all other troubleshooting steps and you are still receiving
error messages, it is possible that one or more pieces of your hardware are
incompatible with Windows 95 or are damaged. To identify a problem with
your computer hardware, contact your computer vendor.

Badly seated memory or bad memory has been reported to cause Kernel32.dll
error messages. Switching memory around in the motherboard memory banks has
been known to correct some of these issues.

It has also been reported that running the Atron 380 Bus Mastering Ethernet
Card can cause Kernel32.dll errors. Removing this card from the computer
may resolve these error messages.

Excerpt from:
Troubleshooting Office Kernel32.dll errors under Windows 95

Troubleshooting Office Kernel32.dll errors under Windows 98

This article contains information about troubleshooting and eliminating
invalid page faults that occur in module Kernel32.dll when you work with a
Microsoft Office program under Microsoft Windows 98. A Kernel32.dll message
will be similar to the following:

Program name caused an invalid page fault in module Kernel32.dll

where Program name is the name of the Microsoft Office program you are using.

For additional information about troubleshooting Microsoft Office
Kernel32.dll issues under Microsoft Windows 95, please see the following
article in the Microsoft Knowledge Base:

164519

(http://support.microsoft.com/kb/164519/EN-US/
)

Troubleshooting Office Kernel32.dll Errors Under Windows 95

When an invalid page fault occurs, an unexpected event occurs in the
Microsoft Windows operating system. An invalid page fault indicates that a
program improperly attempted to use random access memory (for example, when
a program or a Windows component reads or writes to a memory location that
is not allocated to it). When this occurs, the program can potentially
overwrite and corrupt other program code in that area of memory.

An invalid page fault may occur when parameters are passed between programs
and the Windows 98 operating system. An invalid parameter may cause a
program to run invalid instructions, which results in an invalid page
fault. This behavior usually occurs because a program incorrectly passes
data that Windows or a Windows-based program cannot interpret.

IMPORTANT: Follow the steps in each of the sections in this
article in the order in which they are presented. Because invalid page
faults are typically caused when two or more programs interact, skipping
steps may increase the time it take to identify the problem.

Determine If the Problem Is Documented

Many Kernel32.dll errors are already documented in the Microsoft Knowledge
Base and have solutions. For more information, query on the following words
in the Microsoft Knowledge Base:

“invalid page fault” kernel32.dll

NOTE: It may be helpful to add the program name in which the problem occurs at the end of the query to narrow your search.

For additional information on related Kernel32.dll error messages, please
see the following articles in the Microsoft Knowledge Base:

162398

(http://support.microsoft.com/kb/162398/EN-US/
)

First Aid 97 causes invalid page fault

166125

(http://support.microsoft.com/kb/166125/EN-US/
)

Problems with Millennium and Mystique video cards when you use Office 97 programs

162153

(http://support.microsoft.com/kb/162153/EN-US/
)

Problems after returning computer from suspended state

Do Not Install ClipArt, Binder, and Find Fast

On some systems, cancellation of the installation of ClipArt, Binder, and
Find Fast will resolve this problem during Setup.

These components are installed with a Typical or Custom installation. You
must perform a Custom installation and choose not to install these
components. To do this, follow these steps:

  1. Quit all programs.
  2. On the Start menu, click Run.
  3. Type the following to start Setup:

    Drive:Setup

    where Drive is the drive letter that you are
    installing from. If you are installing from a CD-ROM drive (typically,
    drive D), the command will resemble the following:

    D:Setup

  4. Proceed through Setup as you normally would, but select Custom as the type of installation.
  5. Click Office Tools, and then click Change Option.
  6. Click to clear the ClipArt Gallery, Popular ClipArt and Find Fast check boxes, and then click OK.
  7. Click to clear the Microsoft Binder check box. Click Continue. Proceed through the rest of Microsoft Office 97 Setup as you normally would.

    If the Setup program runs to completion without error, you can install ClipArt, Binder, and Find Fast by running Setup in maintenance mode.

NOTE: The availability of these components and the steps to remove these components may vary in the products listed at the beginning of this
article.

Check for a Valid Temporary Folder and Excess Temporary Files

There should be at least 10 megabytes (MB) of free space on the hard disk
drive that contains the temporary folder. To check for a temporary folder
and to delete excess files from that folder, follow these steps:

  1. Restart your computer. Hold down CTRL until the
    Microsoft Windows 98 Startup Menu appears.
  2. On the Microsoft Windows 98 Startup Menu menu, type the number for Command prompt only, and then press ENTER.
  3. Type set, and then press ENTER. Note the
    location of the TEMP variable.
  4. Change to the folder that you noted in step 3. For example, if TEMP is set to C:WINDOWSTEMP, type the following line, and then press ENTER:

    cdwindowstemp

    If the folder that you noted in step 3 does not exist, create the folder. To create the folder, type the following command, and then press ENTER:

    md c:windowstemp

  5. Delete any temporary files in this folder. Temporary files have a .tmp file name extension. To delete these files, type the following line, and then press ENTER:

    del *.tmp

    NOTE: Do not delete these files from within the Windows 98 graphical
    user interface (that is, when you are running Windows 98) because
    Windows 98 or a Windows program may be using one of these files.

Start Windows in Safe Mode

Windows 98 has a built-in troubleshooting mode called Safe mode. It
bypasses startup files and uses only basic system drivers, including basic
networking. When you start Windows in Safe mode, Windows uses only the
mouse, keyboard, and standard video graphics adapter (VGA) device drivers.
This makes Safe mode useful for isolating and resolving error conditions
that are caused by both real-mode and Windows-based drivers. Windows 98
also has troubleshooting features that may help you identify the problem.
To start Windows 98 in Safe mode and make the additional troubleshooting
features available, follow these steps:

  1. Click Start, and then click Shut Down. Click Restart and then click OK.
  2. Hold down CTRL until the Microsoft Windows 98 Startup Menu appears.
  3. On the Microsoft Windows 98 Startup Menu menu, type the number for Safe mode, and then press ENTER.

    Windows starts in Safe mode.

  4. Perform the same operation that caused the error.

    When you use Safe mode or when you disable 32-bit protected-mode disk
    drivers, Windows 98 does not process protected-mode drivers (the
    Autoexec.bat file, and the Config.sys file). Therefore, the CD-ROM drive
    is not available. To use Safe mode with CD-ROM drive support, determine
    if Windows 98 uses protected-mode drivers for the CD-ROM drive. If
    Windows 98 is using protected mode drivers, install the real-mode (MS-
    DOS) drivers for the CD-ROM drive on the computer. The real-mode drivers
    are usually located on a disk that is shipped with the CD-ROM drive or
    with the computer. The drivers are installed in the Autoexec.bat and
    Config.sys files.

For additional information about determining if Windows 98 is using protected-mode drivers, please see the following article in the Microsoft Knowledge
Base:

151634

(http://support.microsoft.com/kb/151634/EN-US/
)

Protected-mode CD-ROM drive support in Windows

For additional information about installing real-mode drivers for the
CD-ROM drive, please see the following article in the Microsoft Knowledge Base:

167069

(http://support.microsoft.com/kb/167069/EN-US/
)

Installing real mode CD-ROM drivers for Office installation

Check the Hard Disk for Disk Errors and Fragmentation

Use the ScanDisk program to check the hard disk drive for lost clusters and
other file allocation table (FAT) errors and test the hard disk drive
integrity. You can also use the ScanDisk program to repair any of these
problems. To run ScanDisk, follow these steps:

  1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click ScanDisk.
  2. Click the hard disk drive that you want to check for errors, and then
    click Start.

Hard disk drives that are very fragmented can affect the performance and
reliability of Microsoft Office programs and other tasks in Windows 98. To
resolve this problem, run Disk Defragmenter to defragment the hard disk
drive. To run Disk Defragmenter, follow these steps:

  1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click Disk Defragmenter.
  2. Click the hard disk drive that you want to defragment in the
    Which drive do you want to defragment? list, and
    then click OK.

Disable the CD-ROM Drive Cache

If the error message appears while you are reading from a CD-ROM drive, try
disabling the CD-ROM drive cache. This may make the drive more reliable but
reduces performance. To disable the CD-ROM drive cache, follow these steps:

  1. Click Start, point to Settings, and then click Control Panel.
  2. In Control Panel, double-click the System icon.
  3. Click the Performance tab, and then click File System.
  4. On the CD-ROM tab, click No Read-Ahead in the Optimize access pattern for list.
  5. Drag the Supplemental Cache Size slider to the left position (the Small setting), and then click OK.

If you are using real-mode CD-ROM drive drivers, the drive may be cached by
the Smartdrv.exe program. If this is the case, the Smartdrv.exe program
needs to be disabled in the Autoexec.bat file. To disable the Smartdrv.exe
program in the Autoexec.bat file, follow these steps:

  1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click
    System Information.
  2. On the Tools menu, click System Configuration Utility.
  3. Click the Autoexec.bat tab.
  4. Click to clear the check box that contains Smartdrv, and then click OK.
  5. When prompted to restart the computer for the change to take effect, click Yes.

Verify That the Compact Disc Is Clean and Unscratched

If the error message appears while you are installing from a compact disc,
verify that the compact disc you are using is clean. You can wipe the
compact disc with a soft, lint-free cloth. Also ensure that there are no
large scratches on the compact disc. If the compact disc is damaged and
unreadable, error messages may appear during installation.

For additional information, please see the following article in the
Microsoft Knowledge Base:

174713

(http://support.microsoft.com/kb/174713/EN-US/
)

Troubleshooting installation from compact disc media

Check for a Corrupted Swap File

The Kernel32.dll error may also appear if your Windows swap file is
corrupted. To create a new swap file, restart the computer in MS-DOS mode,
delete the Win386.swp file in the Windows folder, and then restart the
computer. To create a new swap file, follow these steps:

  1. Click Start, and then click Shut Down.
  2. In the Shut Down Windows dialog box, click
    Restart in MS-DOS Mode, and then click OK.
  3. At the MS-DOS prompt, change to the Windows folder by typing the
    following command

    cd drive:Windows

    where drive is the drive letter that contains the Windows folder. (Typically, drive is C).

    NOTE: The swap file exists in the Windows folder if Windows manages
    virtual memory settings on your computer. If you chose to manage
    virtual memory settings on the computer, the swap file exists at the
    root level of the hard disk. To determine whether Windows manages
    virtual memory settings, right-click My Computer, click
    Properties, click Performance, and then click Virtual
    Memory
    .

  4. To delete the swap file, type the following:

    del Win386.swp

  5. After you delete the swap file, restart the computer.

Corrupted Custom Profile

Corrupted custom profiles have also been known to cause Kernel32.dll
errors. Deleting and re-creating the profile can possibly resolve this
problem.

If you are using the Microsoft Office 97 system policy templates that are
included in the Microsoft Office 97 Resource Kit, you must use the version
of the System Policy Editor that is included in the Microsoft Office 97
Resource Kit or the Microsoft Windows NT 4.0 Resource Kit. Use the Office
97 Templates for Windows 95 for Microsoft Windows 98.

NOTE: You can download Policy.exe, a self-extracting executable file
containing Poledit.exe, from online services. Download this file from the
following Microsoft World Wide Web site:

Remove and Reinstall the Program

If the problem occurs after you run the Setup program, some of the dynamic
link library (DLL) files may be damaged or corrupted. To troubleshoot this
problem, completely remove the program. For additional information,
please see the following articles in the Microsoft Knowledge Base:

158658

(http://support.microsoft.com/kb/158658/EN-US/
)

How to completely remove Microsoft Office 97

133274

(http://support.microsoft.com/kb/133274/EN-US/
)

Setup “Remove All” doesn’t remove all files

After you completely remove the program, reinstall the program.

Check for Software Updates

Outdated and incompatible software may also cause error messages to appear.
Check with the manufacturer of the computer for various software updates,
such as BIOS updates, OEM Windows updates, and hardware driver updates
(such as CD-ROM drive drivers). If you are using third-party partitioning
software (for example, EZDrive, or Ontrack Disk Manager), verify that you
have the most recent versions of these products.

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

For more information about hardware and software vendor contact information, visit the following Microsoft Web site:

Scan the Computer for Viruses

If a virus is present on your computer and has damaged some files,
Kernel32.dll error messages may appear when you use a program. Scan the
hard disk drive and floppy disks with a virus detector. If the virus
detector finds a virus on your computer, remove the virus before you run
the Office program again. If a virus is found on your Setup disk, you must
obtain a new set of disks.

NOTE: Do not run a virus detector terminate-and-stay-resident (TSR) program while you run any of the Microsoft Office programs, including the Setup program. Run a virus detector before you run the Setup program, and then disable it.

If you determine that you have a Setup disk that was damaged by a virus,
you can order a new set of disks.

IMPORTANT: Microsoft Office 97 Service Release CD-ROMs and replacement CD-ROMs are no longer available from Microsoft.

For more information about obtaining the Microsoft Office 97 Service Release 1 (SR-1) and Microsoft Office 97 Service Release 2 (SR-2), click the following article number to view the article in the Microsoft Knowledge Base:

192874

(http://support.microsoft.com/kb/192874/
)

An overview of Microsoft Office 97 Service Release 2 (SR-2)

Check for Registry Corruption

When you start Windows 98 in Safe mode, Windows does not read the entire
registry. Therefore, damage to the registry may not be evident when you run
Windows in this mode. It may be necessary to replace the existing registry
(System.dat) with a backup to determine whether the problem is caused by a
damaged registry. Use one of the following methods to troubleshoot a
damaged registry.

Method 1: Use Registry Checker

Windows 98 includes a tool called Registry Checker that can scan your
registry for corruption, and, if necessary, restore a backup of the
registry. Follow these steps to use Registry Checker to scan your
registry:

  1. Click Start, point to Programs, point to Accessories, point to System Tools, and then click System Information.

    Microsoft System Information starts.

  2. On the Tools menu, click Registry Checker.

    You may receive the following error message:

    Windows encountered an error accessing the system registry.
    Windows will restart the computer and repair the system registry
    for you.

    If you received this error message, proceed to step 3.

    If you do not receive the error message, then your registry is OK.

  3. To restart your computer, click OK.
  4. Press ENTER when the Windows 98 Startup menu appears.
  5. At the command prompt, type Scanreg, and
    then press ENTER.
  6. Press ENTER in the Check Your Registry dialog box. You should receive the following message:

    Windows found an error in your system files and restores a recent
    backup of the files to fix the problem.

  7. Press ENTER to restart your computer.

Windows 98 stores five backups of your registry. If the
registry has been damaged for a long period of time, then you may need
to use “Method 2: Restore the System.1st File” to determine whether or
not your registry is damaged.

For additional information about Registry Checker, please see the
following
articles in the Microsoft Knowledge Base:

183887

(http://support.microsoft.com/kb/183887/EN-US/
)

Description of the Windows Registry Checker Tool (Scanreg.exe)

183603

(http://support.microsoft.com/kb/183603/EN-US/
)

How to customize Registry Checker Tool settings

184075

(http://support.microsoft.com/kb/184075/EN-US/
)

Description of Microsoft System Information (Msinfo32.exe) Tool

Method 2 – Restore the System.1st File

To restore your System.1st file, follow these steps:

  1. Restart your computer. Hold down CTRL until
    the Microsoft Windows 98 Startup Menu appears.
  2. On the Microsoft Windows 98 Startup Menu menu, select the option for Command prompt only, and then press ENTER.
  3. To remove the file attributes from the backup of the registry, type the following command, and then press ENTER:

    c:windowscommandattrib -h -s -r c:system.1st

  4. To remove the file attributes from the current registry, type the
    following command, and then press ENTER:

    c:windowscommandattrib -h -s -r c:windowssystem.dat

  5. To rename the registry, type the following command, and then press
    ENTER:

    ren c:windowssystem.dat *.dax

  6. To copy the backup file to the current registry, type the following command, and then press ENTER:

    copy c:system.1st c:windowssystem.dat

  7. Restart the computer. If the Windows 95 Startup Menu appears, select Safe Mode, or Safe Mode With Network Support if you need network connectivity.

NOTE: The System.1st file is a backup of the registry that is created during the final stage of a Microsoft Windows 98 installation. When you restart your computer, Windows 98 Setup starts at the “Setting up
hardware and finalizing settings” phase of setup.

If replacing the System.dat file with the System.1st file resolves the
issue, the problem may be related to registry damage. Note that you may
have to reinstall programs and device drivers that you installed after
you installed Windows 98 to update the new registry.

If the issue is not resolved, restore the original registry. To do this,
follow these steps:

  1. Restart your computer. Hold down CTRL until
    the Microsoft Windows 98 Startup Menu appears.
  2. On the Microsoft Windows 98 Startup Menu menu, select the option for Command prompt only, and then press ENTER.
  3. Type the following commands:
    c:windowscommandattrib -s -h -r c:windowssystem.dat


    copy c:windowssystem.dax c:windowssystem.dat

    Press Y and then press ENTER when you are asked to overwrite the
    existing System.dat file.

  4. Restart the computer.

Disable DMA for the CD-ROM During Installation

There are unconfirmed reports that disabling Direct Memory Access in
Device Manager for some CD-ROM drives may prevent Kernel32.dll errors.

For additional information, please see the following article in the
Microsoft Knowledge Base:

190630

(http://support.microsoft.com/kb/190630/EN-US/
)

Kernel32.dll and other error messages when you install Office 2000 products with Direct Memory Access (DMA) enabled on Windows 95 or Windows 98

Reinstall Windows in a New Folder

Use this method only after you have tried all of the troubleshooting steps in this article. If you reinstall Windows in a new folder, you must reinstall all Windows-based programs under the new Windows 98 installation.

For additional information, please see the following article in the
Microsoft Knowledge Base:

190040

(http://support.microsoft.com/kb/190040/EN-US/
)

Installing Win 98 to new folder to t-shoot Office problems

Disable Enhanced BIOS Features

Most computers have several enhanced settings that allow the computer to
fully use the computer hardware. These high-speed settings can cause
the system to become unstable; disabling these features may make the
computer more stable. Contact your computer manufacturer for information
about entering the basic input/output system (BIOS) and changing the BIOS
settings. You can enter the BIOS on most systems immediately after turning
on the power. Usually a keystroke (such as DEL) is required to enter the
BIOS. Below are the common features that can interfere with Microsoft
Office programs:

Memory Shadow RAM
Video Shadow RAM
Internal Cache
External Cache
Built-in Virus Protection

Newer chipsets may have more advanced features (such as memory wait states)
that may cause errors. Most BIOS installation programs have an option to
load the BIOS default settings. This option usually disables all advanced
features.

WARNING: Incorrectly altering hardware BIOS settings can cause serious problems that may cause your computer to fail to start or function
properly. Microsoft cannot guarantee that problems that result from the
incorrect setting of hardware BIOS options can be solved. Alter the
hardware BIOS settings at your own risk.

Check Hardware

If you exhaust all other troubleshooting steps and you are still receiving
error messages, it is possible that one or more pieces of your hardware are
incompatible with Windows 98 or are damaged. To identify a problem with
your computer hardware, contact your computer vendor.

Badly seated memory or bad memory has been reported to cause Kernel32.dll
error messages. Switching memory around in the motherboard memory banks has
been known to correct some of these issues.

See more here:
Troubleshooting Office Kernel32.dll errors under Windows 98

INFO: Getting Started with Active Server Pages

This article describes how to get started with Active
Server Pages (ASP). This article is one of a series of articles that discuss an
important “Getting Started” topic.

Audience

This article is intended for novice and intermediate customers
who are familiar with computer programming. Although prior experience with a
Web development language such as HTML is helpful, you do not have to have prior
experience to complete the provided steps.

What is ASP?

ASP is a set of software components that run on a Web server and
allow Web developers to build dynamic Web pages. The advantage of ASP over
static HTML Web pages is that an ASP page is like a computer program that runs
on a Web server and can calculate results, process user input, read from or
write to databases and files, and insert “live” updated content every time a
user browses the page.

Related Technologies

ASP runs with a Web server on the Microsoft Windows platform. The
Web server that is used is Internet Information Server (IIS). It is also
possible to run ASP with a limited feature set on Microsoft Personal Web Server
(PWS), which runs on Microsoft Windows 95, Microsoft Windows 98, and Microsoft
Windows NT Workstation. ASP can also run on Unix operating systems by using
special extensions that are created by software vendors.

Because ASP
is frquently used to create business applications on the Web, it is regularly
used with databases such as Microsoft Access, Microsoft SQL Server, or
databases from other vendors. When used in conjunction with a database, ASP
pages can even run transactional applications, such as those used by banks, by
using the features of COM+ or Microsoft Transaction Server (MTS). A number of
tools can be used to create ASP pages, ranging from simple text editors such as
Notepad, popular Web site creation tools by Microsoft and other vendors, or a
full-featured programming tool such as Microsoft Visual InterDev.

Step-by-Step Instructions

Step 1: Install ASP

Windows 2000

ASP version 3.0 is included with all versions of the
Microsoft Windows 2000 operating system. ASP is installed automatically when
you install the Internet Information Services option with Windows 2000. To
install this option, follow these steps:

  1. In Control Panel, click Add/Remove Programs.
  2. Click Add/Remove Windows Components, and then select the Internet Information Services check box.
  3. In the Windows Component Wizard, click Next, and follow the on-screen instructions.

Windows NT 4.0 Server

The older version of ASP, version 2.0, runs on
Microsoft Windows NT 4.0 Server, which requires you to install the Windows NT
4.0 Option Pack. To install ASP, select Internet Information Server from the setup dialog box in which you to select components to
install. Also, install the latest Windows NT 4.0 Service Pack with the Option
Pack.

To install the Windows NT 4.0 Option Pack and the latest
Windows NT 4.0 Service Pack, visit the following Microsoft Web sites:

Windows 95, Windows 98, and Windows NT 4.0 Workstation

ASP version 2.0 also runs on Windows 95, Windows 98,
and Windows NT 4.0 Workstation by installing Personal Web Server (PWS). PWS is
included with the Windows NT Option Pack. When the download wizard runs, select
the appropriate operating system (for example, select Windows 95).

To download the Windows NT Option Pack, visit the
following Microsoft Web site:

Windows Millennium Edition (Me)

ASP is not supported on Windows Millennium Edition.

Step 2: Configure a Web Application on the Web Server

After you install IIS or PWS, you must configure a Web
application on the Web server. This article assumes that you are running IIS
version 5.0 on Windows 2000. These instructions also work with IIS version 4.0
on Windows NT 4.0 Server, and the ASP code works on both IIS and PWS. For
instructions on configuring a Web application for PWS, see the documentation
that is included with PWS.NOTE: Microsoft Visual InterDev version 6.0 and Microsoft FrontPage
2000 can automatically perform application setup for you on the Web server. If
you are using one of these programs to create Web sites, you can skip the
following manual setup instructions and continue directly to step 3.

  1. On a Windows 2000-based computer, open the Internet
    Services Manager (ISM). To do this, on the Start menu, click Run, type inetmgr, and then click OK. The Internet Information Services (ISM) console
    opens.
  2. Expand the top-level node that contains your computer name.
    Right-click Default Web Site, click New, and then click Server Extensions Web.
  3. The New Subweb Wizard begins. Click Next to continue. In the Directory Name text box, type the name of the Windows folder to be created for
    your Web application. In the Title box, type an alias that points to the underlying physical Windows
    folder. The title is what users see as part of the URL path when they are
    browsing this Web application (for example,
    http://www.microsoft.com/MyWebTitle). The title can
    be different from the underlying physical Windows folder name, but for this
    example, just type MyWeb for both the folder name and
    the title. Click Next, accept the default for Access Control, click Next again, and then click Finish.
  4. In the left pane of the ISM, select Default Web Site again, and press the F5 key to refresh the list of virtual
    folders. Note that your newly created application’s virtual folder appears
    under the default site.
  5. Right-click the folder for your application, then click Properties. On the Directory tab, follow these steps:
    • Select Read access.
    • Make sure that Execute Permissions is set to Scripts only.
    • If the Create button is available, click it.
  6. Close the Properties dialog box. In the ISM, notice that the icon for your virtual
    folder does not appear as a yellow folder but as a green symbol in a gray box.
    This means that your application is set up and ready to host ASP pages, so you
    can close the ISM.

Step 3: Create Your First ASP Page

NOTE: For this example, do not use Visual InterDev or FrontPage to
create an ASP page. Although both applications can create ASP pages easily, it
is better for learning purposes to hand-code the ASP page in a simple text
editor such as Notepad.

  1. Click Start, point to Programs, point to Accessories, and then click Notepad.
  2. In Notepad, paste the following code for the basic page
    structure:
    <%@ Language="Vbscript" %>
    
    
    
    
    
    
    
    
    
    					

  3. Type some ASP identifier tags and ASP code in the page.
    Note that for ASP code to run, it must be identified by one of the following
    sets of tags. The Web server uses these tags to identify the code that must be
    processed on the server before it returns the page to a browser.
    • ASP identifier tag 1: <% Your ASP code goes here %>

      In this
      approach, you create an opening tag with the less than (<) and percent (%)
      symbols, a closing tag with the percent (%) and greater than (>) symbols,
      and you write your ASP code between the opening and closing tags.

    • ASP identifier tag 2:

      In this approach, the script tags are the same as
      the HTML script tags, except that the opening script tag has an attribute
      called runat=’Server’.

    As an example, put a pair of ASP tags between the body tags
    in your ASP page. Between the ASP tags, input the following VBScript code
    sample so that the completed version of your ASP page resembles the following:

    <%@ Language="Vbscript" %>
    
    
    
    
    
    
    
    <%
    	'Use an apostrophe to delimit code comment lines like this one.
    	'Declare variables.
    	Dim strGreeting, strTime, strTotal
    
    	'Process and calculate.
    	strTotal = 10 * 21
    	strTime = Now()
    
    	'Create a string that inserts the value of the two earlier
    	'variables.
    	strGreeting = "Hello World!  The current date and time are:  " & strTime & ".
    " & _ "The result of our calculation is: " & strTotal 'Output the results to the browser Response.write strGreeting %>

Step 4: Save the ASP Page to the Web Application

Now save your ASP page to the Windows folder that is created for
your Web application in step 1. When you used the Server Extensions Web Wizard
in step 1, you typed a folder name for the physical Windows folder that
contains your Web application’s content, and then the wizard created the folder
for you. By default, the wizard creates the new folder and subweb in the root
site for IIS. Because you used the name MyWeb for your folder and your title
alias, the typical path to it on your system resembles the following:

C:InetpubWwwrootMyWeb

When the MyWeb application is running under IIS, and you use a
Web browser to view the application, the URL path for the application starts
with the Web protocol (http://). Next, if this is a local Web that is only on
your computer or on your company intranet, use your Windows computer name (for
example, MyServer), or for publicly accessible
Internet sites, use your domain name (for example,
www.MyCompany.com). Finally, append the alias or
title of your Web application’s subfolder. The resulting URL resembles the
following URL:

http://MyServer/MyWeb

-or-

http://www.MyCompany.com/MyWeb

To save the ASP page that you created in the previous step and
put it in your Web application, follow these steps:

  1. In Notepad, on the File menu, click Save.
  2. In the Save As dialog box, use the Save In drop-down list box to locate your application’s physical folder
    (for example, C:InetpubWwwrootMyWeb).
  3. In the Save as type drop-down list box, select All Files.
  4. In the File Name text box, delete any default file extensions that you see, and
    then type your file name with the ASP extension (for example,
    Default.asp).
  5. Click Save.

Step 5: Use the Web Server to View the Page

Open a Web browser, such as Microsoft Internet Explorer. In the
address line, type the URL to your new ASP page. For example, if your server is
running locally (that is, it is not serving pages on the Internet), the URL
resembles the following:

http://MyComputerName/MyWeb/Default.asp

Or, if your server is serving pages on the Internet, the URL
resembles the following:

http://www.MyCompany.com/MyWeb/Default.asp

Note that new Web applications in IIS are automatically set to
use either Default or Index as a default file in the virtual folder for your
Web application. In other words, if you use Default.asp as the name for your
home page or the first page in your application, you do not have to use the
file name in the URL. You can just locate the virtual folder that contains the
Default.asp page, as follows:

http://MyComputerName/MyWeb/

Additional Assistance with ASP

For more information, visit the ASP Newsgroup for peer-to-peer
questions and answers. It is located under “Internet Server Programming”, which
located under “Web Development” at the following Microsoft Developer Network
(MSDN) Online Newsgroups Web site: For more information, visit the following Microsoft Web site: For help with technical questions, visit the following Microsoft
Web site to search the Microsoft Knowledge Base: To get help directly from Microsoft, visit the following
Microsoft Web site and open a technical support incident: For ASP tutorials, code samples, and references, visit the
following Microsoft Web sites: For third-party ASP references and tutorials, visit the following
Web sites: Microsoft
provides third-party contact information to help you find technical support.
This contact information may change without notice. Microsoft does not
guarantee the accuracy of this third-party contact
information.

Microsoft ASP.NET

Microsoft ASP.NET is build on .NET technology and has many
advanced features. For more information about ASP.NET, visit the following
Microsoft Developer Network (MSDN) Web site:

Follow this link:
INFO: Getting Started with Active Server Pages

Error message when you try to create a user in the Microsoft Online Administration Center: "The user name or alias that you entered is already in use"

Consider the following scenario. You try to create a user in the Microsoft Online Administration Center (MOAC). To do this, you use the user name of another user from a different Simple Mail Transfer Protocol (SMTP) domain in the same company. In this scenario, you receive the following error message:

User creation failed. We were unable to create the user requested. The user name or alias that you entered is already in use. Enter a unique name. Please use the Previous button to resolve the problem and try again.

You may also experience the following issues:

  • You cannot synchronize or activate a User Account.
  • You cannot add or Synchronize a Conference Room.
  • You cannot add or Synchronize a Distribution List.
  • You cannot add an alternative email address to a user account.
These issues may occur if one or more of the following conditions are true:
  • The alias is being used for another object, such as an enabled user, a disabled user, a distribution list, or a conference room.
  • The email address already exists in another Microsoft Online Services company.
  • The email address already exists in the customer’s Live Meeting Conference Center, such as a Microsoft account. 
  • Network issues occurred on-premise or in the Microsoft Online Services Environment.

Note The Microsoft Online user name uses the User_name@CompanyGUID format. Therefore, it is not important what the SMTP domain is. If you use another user’s user name, you must also use that user’s GUID. Because the GUID must be unique, the process is unsuccessful in the scenario that is described in the “Symptoms” section.

To resolve this issue, you can use the Microsoft Online Services Directory Synchronization tool to synchronize user accounts that use the same alias.

For example, when you use the MOAC to create a user account that is named jimbob@contoso.com, and a similar user account that is named jimbob@fabrikam.com already exists, you may receive the error message that is mentioned in the “Symptoms” section. In this scenario, you can use the Microsoft Online Services Directory Synchronization tool.

Article ID: 956981 – Last Review: July 24, 2012 – Revision: 15.0


Applies to
  • Microsoft Business Productivity Online Standard Suite
vkbportal238 vkbportal221 kbexpertisebeginner kbtshoot vkbportal230 KB956981

See more here:
Error message when you try to create a user in the Microsoft Online Administration Center: "The user name or alias that you entered is already in use"

You are prompted for a username and for a password even though you do not turn on security or set up security in Access

When you run Microsoft Access 2000 or a later version, you are prompted for a username and for a password. This behavior occurs even though you do not turn on security or set up security. You are prompted for a username and
for a password for every database. This includes even a brand new database.
This behavior occurs if you install “Typing Tutor Deluxe” by
Global Software Publishing.
To resolve this behavior, use the Workgroup Administrator tool
to rejoin the original default workgroup information file. To do this, you can use one of the following methods. The method that you use depends on your version of Access.

Office Access 2007

To use the Workgroup Administrator tool in Microsoft Office Access 2007, use Microsoft Visual Basic code. To do this, use one of the following methods.

Method 1: Run the Visual Basic code in the Immediate window

  1. In Access 2007, open a trusted database, or enable macros in the existing database.
  2. Press CTRL+G to open the Immediate window.
  3. Type the following line of code, and then press ENTER.
    DoCmd.RunCommand acCmdWorkgroupAdministrator

  4. In the Workgroup Administrator dialog box,
    click Join, and then click Browse.
  5. Locate and then click the following file, and
    then click Open:

    C:Program FilesCommon FilessystemSystem.mdw

  6. In the Workgroup Administrator dialog box, click OK, and then click Exit.

Method 2: Create a module that contains the Visual Basic code

  1. In Access 2007, open a trusted database, or enable macros in the existing database.
  2. On the Create tab, click Macro in the Other group, and then click Module.
  3. Create a subroutine, and then paste the following Visual Basic code in the subroutine.
    DoCmd.RunCommand acCmdWorkgroupAdministrator

  4. Press F5 to run the code.
  5. In the Workgroup Administrator dialog box,
    click Join, and then click Browse.
  6. Locate and then click the following file, and
    then click Open:

    C:Program FilesCommon FilessystemSystem.mdw

  7. In the Workgroup Administrator dialog box, click OK, and then click Exit.

Office Access 2003

  1. Start Office Access 2003.
  2. Click Tools, point to
    Security, and then click Workgroup
    Administrator
    .
  3. Click Join, click Browse, browse to C:Documents and Settingsyour user nameApplication DataMicrosoftAccessSystem.mdw
  4. , and then click
    OK.
  5. In the Workgroup Administrator
    dialog box, click OK.
  6. In the Workgroup Administrator dialog box,
    click OK.

    Note The Workgroup Administrator dialog box in step 5 is a different dialog box than the dialog box in step 4. Both dialog boxes have the same name.

Access 2002

  1. Start Access.
  2. Click Tools, point to Security, and then click Workgroup Administrator.
  3. In the Workgroup Administrator dialog box, click Join, click Browse, browse to C:Documents and Settingsyour user nameApplication DataMicrosoftAccessSystem.mdw, and then click OK
  4. In the Workgroup Administrator dialog box, click OK, and then click Exit.

Access 2000

  1. Click Start, and then click
    Search.
  2. In the Search Results dialog box, click All files
    and folders

    under What do you want to search for.
  3. Type Wrkgadm.exe under All or part of the file name, and then click
    Search.
  4. In the Search Results dialog box,
    double-click WRKGADM.
  5. In the Workgroup Administrator dialog box,
    click Join, click Browse, browse to C:Program FilesCommon FilessystemSystem.mdw, and
    then click OK.
  6. In the Workgroup Administrator
    dialog box, click OK, and then click
    Exit.
When you install “Typing Tutor Deluxe,” your workgroup security for Access is reset to point to a workgroup
information file that is created for “Typing Tutor Deluxe.”

For more information about another possible cause for this behavior, click the following article number to view the article in the Microsoft Knowledge Base:

815278

(http://support.microsoft.com/kb/815278/
)

How to troubleshoot the User Authentication dialog box while opening a non-secure database

Article ID: 888734 – Last Review: July 24, 2012 – Revision: 5.0


Applies to
  • Microsoft Office Access 2007
  • Microsoft Office Access 2003
  • Microsoft Access 2002 Standard Edition
  • Microsoft Access 2000 Standard Edition
kbdatabase kbpermissions kbpasswords kbtshoot KB888734

Other Support Sites

Community

Get Help Now

Article Translations

Related Office 2000 Web Sites

Visit site:
You are prompted for a username and for a password even though you do not turn on security or set up security in Access

Emergency message purge and transport rule processing in a dedicated Office 365 environment

In a dedicated Microsoft Office 365 environment, a user may experience one of the following issues:
  • Many prolems with mail queuing or performance 
  • An email message that includes incorrect or sensitive content was sent to multiple mailboxes
The first issue may occur if many email messages or very large email messages are sent to multiple users. This may be related to a denial of service attack.
To resolve these issues, Microsoft can take the following two kinds of actions:
  • Emergency transport rule
    • Removes instances of an email message from transport queues. 
    • Keeps new instances of an email message from being delivered to users.
  • Emergency message purge
    • Removes instances of an email message from mailboxes.

In some scenarios, it may be appropriate to request both an emergency transport rule and an emergency message purge. The following three examples illustrate some common scenarios.

Scenario 1

A user reports that an email message that includes an attachment was incorrectly sent to a distribution group that has thousands of members. The attachment contains salary information for several hundred users. This issue occurred 30 minutes earlier, and the sender of the email message engaged their service desk to request that the email message be removed from the recipients’ mailboxes.

Scenario 1: Resolution

To resolve the issue in scenario 1, contact Microsoft to request an emergency message purge. Customers should complete the EXCHANGE – EMERGENCY MESSAGE PURGE AND/OR TRANSPORT RULE REQUEST escalation template and provide as much information about the email message as possible. The information should include the sender, the recipients, the subject, the day or time that the email message that was sent, and the fact that the email message contains an attachment.

Scenario 2

Users report that they are receiving many copies of an email message from an external sender. Some users reply all and forward the email message. There are some reports of internal messages taking a long time to be received.

Scenario 2: Resolution

To resolve the issue in scenario 2, contact Microsoft to request an emergency message purge and an emergency transport rule. Customers should complete the EXCHANGE – EMERGENCY MESSAGE PURGE AND/OR TRANSPORT RULE REQUEST escalation template and provide as much information about the email message as possible. The information should include the sender, the recipients, the subject, the day or time of the email message that was sent, and the evidence that is available to indicate that other email messages are delayed. This lets us determine whether an emergency transport rule is necessary.

Scenario 3

An internal process generated many email messages, and all mail delivery is delayed.

Scenario 3: Resolution

To resolve the issue in scenario 3, contact Microsoft to request an emergency transport rule to delete these email messages. Customers should complete the EXCHANGE – EMERGENCY MESSAGE PURGE AND/OR TRANSPORT RULE REQUEST escalation template and provide as much information about the email message as possible. The information should include the sender, the recipients, the subject, the day or time of the email message that was sent, and the evidence that is available to indicate that other email messages are delayed.

Emergency transport rule

If it is necessary, an emergency transport rule will be created based on the characteristics that are provided, and corresponding email messages will be deleted.

Emergency message purge

The emergency message purge process removes email messages from a user’s mailbox based on specific characteristics. These characteristics can include sender, day or time that the message was sent, subject line, and whether there is an attachment. The emergency message purge searches for email messages that match the criteria and then removes these email messages from the mailbox. The email messages in the Recoverable Items folder of the mailbox are also removed. However, the email message is not removed from the Purges folder. This means that the purged item can be recovered individually by an administrator. However, the purged item is not recoverable from Microsoft Outlook and cannot be recovered in a bulk process.

For more information about deleted item retention and recovery, go to the following Microsoft TechNet website:

An emergency message purge can be completed by O365 Dedicated Support. The process involves multiple steps to make sure that the correct content is removed from users’ mailboxes. This process is optimized to make sure that the correct information is removed in as timely a manner as possible. 

Limitations and risks

The customer should be aware that they have to work closely with O365 Dedicated Support throughout the following process:

  1. An authorized requestor submits a completed escalation template. The completed escalation template provides O365 Dedicated Support with the characteristics that are needed to identify the target email message. These include include the sender, the subject line, and the date or time that the email message that was sent. If a customer other than the authorized requestor should work with O365 Dedicated Support, this should be specified in the “Primary Contact” section of the escalation template. If the customer knows from which recipients’ mailboxes they want the email message purged, they should include a list of recipients in the escalation.
  2. If the case is a Severity A escalation, the customer must call O365 Dedicated Support after they submit the escalation template.
  3. The O365 Dedicated Support agent will work to obtain a complete list of the recipients if the customer did not provide this or if the customer is not sure of who should be included in the list of recipients. The agent will do this by searching the message-tracking logs for the message in question and exporting all recipients. This lets the purge process be run against as few mailboxes as possible. Message tracking expedites the process and avoids unexpected consequences. However, message-tracking logs are maintained for only ten days. If the email message was sent more than ten days earlier, the requestor must provide a list of recipients.

    Note An environment-wide purge can be run against all mailboxes. Depending on the number of mailboxes in the environment and the size of the mailboxes, this process can take up to 48 hours. Such a purge should be done only in situations in which O365 Dedicated Support and the customer requestor agree that this is the method of choice. 

  4. The O365 Dedicated Support agent will engage the authorized requestor (or the customer contact who is specified by the authorized requestor) to confirm the recipient list before they go to the next step.
  5. A pre-purge process is run against the recipient list or all mailboxes. During this process, a search is run against the mailboxes to identify the email message that fits the criteria of the target email message. O365 Dedicated Support will provide the requestor with a spreadsheet that includes a list of the users and the number of messages that were found that meet the criteria of the target email message. There may be a strong business reason to skip this part of the process. If this is the case, skipping the pre-purge search process should be approved by the authorized requestor. Even if the pre-purge search process is skipped, a check should be made to make sure that the SIR feature is enabled for all recipients and all mailboxes. If the SIR feature is not enabled, the support agent will enable the SIR feature. This feature makes sure that messages can be recovered for a specific mailbox from the mailbox Purges folder. 

    For more information about the SIR feature, go to the following Microsoft TechNet website: 

    It will take an hour to confirm that SIR is set on the mailbox. The process can continue for the mailboxes that are found to have SIR enabled. The purge can then be run against the remaining mailboxes. If there is a strong business reason to continue the purge process on all mailboxes immediately, the customer contact should communicate this to the O365 Dedicated Support agent.

    After the pre-purge process is complete and the customer reviews the spreadsheet, the requestor must provide their approval to O365 Dedicated Support through an email message. Then, the purge will continue.

  6. When O365 Dedicated Support receives the approval, the purge will be run, and a spreadsheet that contains the recipients and the number of email messages that were found will be sent to the customer. 

Article ID: 2736413 – Last Review: July 23, 2012 – Revision: 2.0


Applies to
  • Microsoft Business Productivity Online Dedicated
  • Microsoft Business Productivity Online Suite Federal

Continued here:
Emergency message purge and transport rule processing in a dedicated Office 365 environment

Page 322 of 728« First...102030...320321322323324...330340350...Last »

Recent Comments

    Archives

    Categories