Page 323 of 734« First...102030...321322323324325...330340350...Last »

OFF2000: Some Shortcuts Are Not Removed When You Upgrade from Localized Office 97

When you upgrade from a localized (non-U.S.) version of Microsoft Office 97 to the United States version of Office 2000, it is possible that not all of the shortcuts and files are removed from the Start menu and the Programs menu, even though the English equivalent shortcuts are added to the menus. For example, the Apri documento Office and the Nuovo documento Office shortcuts of the Italian version of Office 97 are left on the Start menu, and the equivalent English shortcuts for Office 2000, New Office Document and Open Office Document, are added. Also, the Raccoglitore Office shortcut is left on the Programs menu and there is no English equivalent shortcut.
This behavior may occur because Start menu items and Program menu items are only automatically removed if the previous version of Office is the same language as Office 2000.
To remove the localized shortcuts when you upgrade from a localized version of Office to U.S. Office 2000, you need to use the localized version of the Office Removal Wizard from the localized version of the Office Resource Kit (ORK) Core Tool Set. The U.S. English version of the ORK Core Tool Set, ORKTools.exe can be downloaded and installed from the following address:

ORK Tools

(http://download.microsoft.com/download/0/e/d/0eda9ae6-f5c9-44be-98c7-ccc3016a296a/ork.exe)

You can find the localized version of the ORK Core Tool Set by starting at the following address:

After you download and run ORKTools.exe, you can run the Office Removal Wizard to remove the files from the localized version of Office.

NOTE: It may be necessary to reinstall Office 2000 after you remove files by using the Office Removal Wizard.

Article ID: 229476 – Last Review: August 9, 2012 – Revision: 3.0


Applies to
  • Microsoft Office 2000 Premium Edition
  • Microsoft Office 2000 Professional Edition
  • Microsoft Office 2000 Standard Edition
  • Microsoft Office 2000 Small Business Edition
  • Microsoft Office 2000 Developer Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Excel 2000 Standard Edition
  • Microsoft FrontPage 2000 Standard Edition
  • Microsoft Outlook 2000 Standard Edition
  • Microsoft PowerPoint 2000 Standard Edition
  • Microsoft Word 2000
kbinterop kbprb kbsetup KB229476

View article:
OFF2000: Some Shortcuts Are Not Removed When You Upgrade from Localized Office 97

How to install Office 2000 to Windows NT 4.0 Terminal Server

This article explains how to install Microsoft Office 2000
to a computer that is running Microsoft Windows NT Server version 4.0, Terminal
Server Edition.
Before you install Office 2000, you must do the following
to your configuration:

  • You must install and enable Terminal Services. You must
    configure the Terminal Services mode to be in Install mode in order for multiple terminal server clients to run Microsoft
    Office.

    Note Please consult your Microsoft Windows NT 4.0 Terminal Server
    documentation and Microsoft Windows NT 4.0 Terminal Server online Help for more
    information about installing and configuring Terminal Services.

  • You must obtain the Terminal Server transform file,
    TermSrvr.mst, and place it in an accessible location for the
    installation.

    Note You can obtain the transform file from the Microsoft Office 2000
    Resource Kit (ORK). This file can be found at one of the following locations:

    • The ORKPFilesORKToolsToolboxToolsTermSrvr folder
      of the Office 2000 Resource Kit CD.
    • If you installed the ORK, the
      driveProgram FilesORKtoolsToolboxToolsTerminal
      Server Tools folder, where drive is the drive letter
      where Windows NT 4.0 Terminal Server is installed.

Note You can download the Office Resource Kit Core Tool Set from the
following Microsoft Web site:

ORK Tools

(http://download.microsoft.com/download/0/e/d/0eda9ae6-f5c9-44be-98c7-ccc3016a296a/ork.exe)

Note Before you install Office 2000, it is also recommended that you
install the latest Service Pack for Windows NT Server version 4.0, Terminal
Server Edition.

For additional
information about how to obtain the latest Windows NT 4.0 Service Pack, click
the following article number to view the article in the Microsoft Knowledge
Base:

152734

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

How to obtain the latest Windows NT 4.0 service pack

How to Install Office on a Windows NT 4.0 Terminal Server

Note You must be physically present at the computer that is running
Terminal Server in order to perform these steps. Running Office Setup from a
remote client is unsupported.

  1. Click Start, point to Settings, and then click Control Panel.
  2. Double-click Add/Remove Programs. Click Install, and then click Next.
  3. Click Browse.
  4. In the root folder of Office Disc 1, click to select Setup.exe, and then click OK.

    Setup.exe is added to the Command line for
    installation program
    box.

  5. In the Command line for installation
    program
    box, append the following parameter after Setup.exe, separated
    by a space:

    TRANSFORMS=”path:TermSrvr.mst”

    where path is the
    location of the .mst file. This command identifies the Terminal Server
    transform to use during installation.

  6. Click Next.
  7. In the Change User Options dialog box, select All users begin with common
    application settings
    , and then click Next.
  8. Type your customer information, and then click Next.
  9. Accept the End User License Agreement, and then click Next.
  10. Click Install Now.
  11. When prompted, restart the computer and log back on to
    Windows as the same user, to allow Office 2000 Setup to complete
    successfully.
For additional information about installing Office 2000 with
Terminal Server, click the following article numbers to view the articles in
the Microsoft Knowledge Base:
217640

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

Setup fails when installing Office 2000 on a Windows Terminal Server

222303

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

OL2000: Installing Outlook to Run from Terminal Server

243788

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

OFF2000: How to Install Disc 2 on Windows Terminal Server

Article ID: 262584 – Last Review: August 9, 2012 – Revision: 3.0


Applies to
  • Microsoft Office 2000 Premium Edition
  • Microsoft Office 2000 Professional Edition
  • Microsoft Office 2000 Standard Edition
  • Microsoft Office 2000 Small Business Edition
  • Microsoft Office 2000 Developer Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Excel 2000 Standard Edition
  • Microsoft FrontPage 2000 Standard Edition
  • Microsoft Outlook 2000 Standard Edition
  • Microsoft PowerPoint 2000 Standard Edition
  • Microsoft Word 2000
kbwebservices kbsetup kbhowto KB262584

See the article here:
How to install Office 2000 to Windows NT 4.0 Terminal Server

OFF2000: How to Create Windows Installer Shortcuts with One Restart

This article explains how to install Office 2000 so that you also get the Windows Desktop Update and Windows Installer shortcuts with a single restart.

The Windows Installer offers the ability to install Office programs on demand (advertising), as well as the automatic repair of Office programs whenever critical files are deleted. However, the Windows Desktop Update must be installed in order for these features of the Windows Installer to work. Even if you install the Windows Desktop Update after you install Office, you cannot take advantage of these two Windows Installer features. This is because you would not have Windows Installer shortcuts for your Office programs. To have Windows Installer shortcuts created when you install Office, the Windows Desktop Update must be installed first.

NOTE: Windows Installer shortcuts are automatically supported on Microsoft Windows 98 and Microsoft Windows 2000. They are only supported on installations of Microsoft Windows 95 and Microsoft Window NT 4.0 that have an updated version of the Windows shell (Windows Desktop Update) installed. This updated shell is included with later versions of Microsoft Internet Explorer, and it can be added to existing installations of the operating systems.

To install Office 2000 and the Windows Desktop Update in a single installation, so that Windows Installer shortcuts are created for the Office programs, follow these steps:

  1. Download the transform O9WIS_1.mst, which is created specifically for this scenario. Click the following link

    and then download this file by clicking the link.

    NOTE: You can download another transform, O9WIS_2.mst, for installations of Office 2000 CD2.

  2. If you want to customize either transform, you must use version 1.00.00.3217 or later of the Custom Installation Wizard to make the modifications. Click the following link
    ORK Tools

    (http://download.microsoft.com/download/0/e/d/0eda9ae6-f5c9-44be-98c7-ccc3016a296a/ork.exe)

    and then click the link for ORKTools.exe. After you expand and install ORKTools.exe, the Custom Installation Wizard will be installed.

  3. Download the enhanced version of Setup.exe that provides the ability to chain Windows Installer installations. Click the following link

    and then click the link for Setupsr1.exe. Save this file to your hard disk, and then expand Setup.exe from this download.

  4. Rename Setup.exe on your administrative installation for Office 2000 CD1.
  5. Copy the version of Setup.exe that you downloaded in step 3, and place it on the root of your administrative installation.
  6. Click Start, point to Programs, point to Microsoft Office Tools, point to Microsoft Office 2000 Resource Kit Tools, and then click Custom Installation Wizard.
  7. In the Open the MSI File dialog box, click Browse. Locate and select Data1.msi from your administrative installation, and then click Open.
  8. Click Next.
  9. In the Open the MST File dialog box, click Open an existing MST file, and then click Browse. Locate and select O9WIS_1.mst, and then click Open.
  10. Click Next.

    NOTE: You can save the transform as a different file name if you want.

  11. When the Add Installations and Run Programs dialog box appears, click Add.
  12. In the Add/Modify Program Entry dialog box, type the following command line, and then click OK:


    .Setup.exe /fms data1.msi /chained

  13. Complete the remaining dialog boxes in the Custom Installation Wizard.
  14. Install Office by using a command line similar to the following:

    servershareSetup.exe transforms=O9WIS_1.mst

For more information about the special transforms, the enhanced version of Setup.exe, and Windows Installer shortcuts, please browse to the following Microsoft Web site:

Article ID: 236428 – Last Review: August 9, 2012 – Revision: 3.0


Applies to
  • Microsoft Office 2000 Premium Edition
  • Microsoft Office 2000 Professional Edition
  • Microsoft Office 2000 Standard Edition
  • Microsoft Office 2000 Small Business Edition
  • Microsoft Office 2000 Developer Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Excel 2000 Standard Edition
  • Microsoft FrontPage 2000 Standard Edition
  • Microsoft Outlook 2000 Standard Edition
  • Microsoft PowerPoint 2000 Standard Edition
  • Microsoft Word 2000

Visit link:
OFF2000: How to Create Windows Installer Shortcuts with One Restart

You receive a "Some default settings in Microsoft Office 2000 setup do not work properly on a Windows Terminal Server" error message when you install Office 2000 on a Windows Terminal Server

When you try to install Microsoft Office 2000, or insert
the CD-ROM into the CD-ROM drive, you may receive the following error message:

Some default settings in Microsoft Office 2000 setup do
not work properly on a Windows Terminal Server. To install Office on Terminal
Server, you must use the instructions and tools available in your Office 2000
Resource Kit or at http://www.microsoft.com/Office/ORK/.

When you
click OK, another error message appears:

Installation ended prematurely because of an error.

When you click OK again, Setup quits.

This problem occurs when you install Office on Microsoft
Windows Terminal Server and you have not used the transform (.mst file)
provided with the Microsoft Office 2000 Resource Kit. When you insert the CD-ROM into the CD-ROM drive, Setup
automatically starts from the Autorun.inf file, but Setup fails because you
have not used the transform.
When installing Office on Windows Terminal Server, you must
use a transform (.mst file). The Microsoft Office 2000 Resource Kit provides a transform called Termsrvr.mst. You must specify this
transform by using a command-line switch during Setup.

Note ORKTools.exe is a self-extracting executable file that contains
the TermSrvr.mst file. You can download ORKTools.exe from Online Services. To
download ORKTools.exe, visit the following Microsoft Web site:

ORK Tools

(http://download.microsoft.com/download/0/e/d/0eda9ae6-f5c9-44be-98c7-ccc3016a296a/ork.exe)

To install Office on a Windows Terminal Server, follow these
steps.

Windows
Terminal Server 4.0

  1. Click Start, point to Settings, and then click Control Panel.
  2. In Control Panel, double-click the Add/Remove Programs icon. Click Install, and then click Next.
  3. Click Browse.
  4. In the root folder of Office Disc 1, click to select Setup.exe, and then click Open.

    Setup.exe is added to the Command line for
    installation program
    box.

  5. In the Command line for installation
    program
    box, append the following parameter after Setup.exe, separated
    by a space:

    TRANSFORMS=”path:TermSrvr.mst”

    where path is the
    location of the .mst file. This command identifies the Terminal Server
    transform to use during installation.

  6. Click Next.
  7. In the Change User Options dialog box, select All users begin with common
    application settings
    , and then click Next.
  8. Follow the prompts on the screen to install
    Office.
  9. When setup is complete, restart the computer and log back
    on to Windows as the same user to allow Office 2000 Setup to complete
    successfully.

Windows
2000 Server with Terminal Services Installed

  1. Click Start, point to Settings, and then click Control Panel.
  2. In Control Panel, double-click the Add/Remove Programs icon.
  3. Click Add New Programs, and then click CD or Floppy.
  4. Click Browse.
  5. In the root folder of Office CD-ROM 1, click to select Setup.exe, and then click OK.

    Setup.exe is added to the Command line for
    installation program
    box.

  6. In the Command line for installation
    program
    box, append the following parameter after Setup.exe, separated
    by a space:

    TRANSFORMS=”path:TermSrvr.mst”

    where path is the
    location of the .mst file. This command identifies the Terminal Server
    transform to use during installation.

  7. Click Finish.
  8. Follow the prompts on the screen to install
    Office.
  9. When you receive the prompt, restart the computer, and then
    log back on to Windows as the same user to allow Office 2000 Setup to complete
    successfully.

Windows Server 2003 with Terminal Services Installed

  1. Click Start, and then click Control Panel.
  2. Double-click Add or Remove Programs.
  3. Click Add New Programs, and then click CD or Floppy.
  4. Click Next.
  5. Click Browse.
  6. In the root folder of Office CD-ROM 1, click to select Setup.exe, and then click OK.

    Setup.exe is added to the Command line for
    installation program
    box.

  7. In the Command line for installation
    program
    box, append the following parameter after Setup.exe, separated
    by a space:

    TRANSFORMS=”path:TermSrvr.mst”

    where path is the
    location of the .mst file. This command identifies the Terminal Server
    transform to use during installation.

  8. Click Next.
  9. Follow the prompts on the screen to install
    Office.

For additional information about installing
Office 2000 on Windows Server 2003 with Terminal Services installed, or for
more information about how to install Office 2000 from the run line on Windows
Server 2003 with Terminal Services installed , click the following article
number to view the article in the Microsoft Knowledge Base:

283675

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

Installing Office 2000 on Terminal Server on a Windows Server 2003-Based Computer

For more information about installing Office on a Windows
Terminal Server, check the Microsoft Office 2000 Resource Kit. For more information, visit the following Microsoft Office 2000
Resource Kit Web page at the following Microsoft Web site:

Article ID: 217640 – Last Review: August 9, 2012 – Revision: 1.0


Applies to
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Office 2000 Premium Edition
  • Microsoft Office 2000 Professional Edition
  • Microsoft Office 2000 Standard Edition
  • Microsoft Office 2000 Small Business Edition
  • Microsoft Office 2000 Developer Edition
  • Microsoft Access 2000 Standard Edition
  • Microsoft Excel 2000 Standard Edition
  • Microsoft FrontPage 2000 Standard Edition
  • Microsoft Outlook 2000 Standard Edition
  • Microsoft PowerPoint 2000 Standard Edition
  • Microsoft Word 2000
kbtshoot kbwebserver kbsetup kberrmsg kbenv kbnofix kbprb KB217640

More:
You receive a "Some default settings in Microsoft Office 2000 setup do not work properly on a Windows Terminal Server" error message when you install Office 2000 on a Windows Terminal Server

INFO: Techniques for Returning a Recordset Through RDS

There are several techniques for returning data in a disconnected recordset
using the Remote Data Service (RDS). There are two objects on the client,
the RDS.DataControl and RDS.DataSpace, and one object on a server,
RDSServer.DataFactory, which you can manipulate in different ways to
generate a recordset, and to submit changes made to the data it contains.
The correct method for your application depends upon the design and
functionality you want.
The Remote Data Service allows you to remote an ActiveX Data Objects (ADO)
Recordset across HTTP, HTTPS or DCOM to a client computer. If using the HTTP/HTTPS protocal it assumes that you have a server running either Internet Information Server 3.0 (or greater),
or Personal Web Server. In either case, you will have installed the RDS Server components on that server. The client computer requires the RDS components, and the client application can be written in any
language that supports COM and manipulation of COM Objects (C++, Java,
Visual Basic For Applications, VBScript, and so forth).

There are two types of ADO Recordsets that you see used in conjunction with
RDS. The ADODB recordset comes from Msado15.dll, and is part of the entire
ADO object hierarchy. However, when marshalling a recordset across the
wire, in order to provide a thin client, (minimal DLL’s and memory
footprint), RDS converts that recordset into an ADOR recordset. ADOR (from
Msado15r.dll) comes without the rest of the ADO object model. For the
purposes of this discussion (as well as any code you write) ADOR.Recordset
and ADODB.Recordset are synonymous. You should reference ADOR.Recordset in
your client application and whether you use ADOR.Recordset or
ADODB.Recordset in your server-side custom business object is irrelevant.
However, if you use ADODB, you can use the Connection and Command objects
which offer functionality not available just opening a recordset “stand-
alone.”

Technique #1 – The DataControl

You can use the RDS.DataControl to retrieve a recordset from the RDS Server
via the Refresh method. You could also assign an existing recordset to the
SourceRecordset property.

Within the Active Server Pages page (ASP) environment, you can bind
graphical controls to the RDS.DataControl.

Whether in ASP or any other development environment, you can easily use the
RDS.DataControl programmatically to retrieve, sort, and filter data. Most
of the properties and methods of the DataControl resemble a subset of the
ADO Recordset (either ADOR or ADODB.) The RDS.DataControl also offers
asynchronous processing that is currently not offered within ADO 1.5. With the release of ADO 2.0 asynchronous processing is available.

The RDS.DataControl uses a business object on the server, provided by RDS,
called the RDSServer.DataFactory. The DataFactory generates a recordset and
also receives changes made to the data it contains. You cannot override
(directly) the DataControl to use a different business object.

The following code demonstrates this technique using Visual Basic for
Applications:

  Dim dc As RDS.DataControl

   Set dc = New RDS.DataControl
   ' ASP Set dc = CreateObject("rds.datacontrol")
   dc.Connect = "DSN=RDSDemo;UID=admin;PWD=;"
   dc.SQL = "SELECT * FROM Authors"
   dc.Server = "http://"
   dc.ExecuteOptions = adcExecAsync
   dc.Refresh
   While dc.ReadyState = 2
      DoEvents             ' User has control during asynchronous query.
   Wend
				

NOTE: Starting with RDS 2.0, the functionality of the RDS DataFactory may be enhanced by writing a custom handler object that implements a specific interface called IDataFactoryHandler. For more information, please see ADO Help for the topic “Handler Property (RDS).”

Technique #2 – Using the DataSpace with the Default Business Object

You may use the RDS.Dataspace object to invoke a business object on the
server. If you provide the ProgID of the default business object
(RDSServer.DataFactory), then you use the business object that RDS provides for
you. This business object can provide a Recorsdet, but offers no conflict
resolution (or any information) regarding a failure if the changes you post
to the data are not accepted.

The following code demonstrates this technique using VBA:


   Dim ds
   Dim df
   dim rs

   Set ds = CreateObject("RDS.DataSpace")
   Set df = ds.CreateObject("RDSServer.DataFactory", _
                            "http://" )
   Set rs = df.Query("DSN=RDSDemo;UID=admin;PWD=;", _
                     "SELECT * FROM Authors")
				

Technique #3 – Using the DataSpace to a Custom Business Object

A business object is nothing more than an ActiveX DLL registered on the RDS
Server (and perhaps on the client, if you are using DCOM as your protocol).
The advantage of this technique is that you can implement conflict
resolution, data validation or other functionality within your business
object.

There are three protocols you can use to marshall a recordset to the
client, HTTP, HTTPS, and DCOM.

When using a custom business object you must add a registry setting to the server where the business object is registered. In the following example the VBCustBusObj.OBJ would need to be added to the following registry key:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServices
W3SVCParametersADCLaunchVBCustBusObj.OBJ
				

Consult the RDS Online documentation for details about registry settings that may be required for any custom business object.

The following code demonstrates this technique using VBA:

   Dim ds
   Dim bo
   dim rs

   Set ds = CreateObject("RDS.DataSpace")
   Set bo = ds.CreateObject("VBCustBusObj.OBJ", _
                            "http://")
   Set rs = bo.Test3_ReturnRS("DSN=RDSDemo;UID=admin;PWD=;", _
                              "SELECT * FROM Authors")
				

Technique #4 – Using the MS Remote Provider

Starting with RDS 2.0, you can use the MS Remote provider along with standard ADO code to return an RDS recordset. The advantage is that you may use ADO code similar to the code you would use with any other provider; the only difference is the connection string. Although your code looks like ADO, it is actually using RDS. So, you must use clientside recordsets with the MS Remote provider.

The connection string for the MS Remote provider must specify the following:

Provider		MS Remote
------------------------------------------------
Remote Server	Server that you want to process your requests

Remote Provider	Provider that you want the server to use
                   (The default is the OLE DB Provider for ODBC)
				

The following code demonstrates this technique using VBA:

Dim cn
     Dim rs

     Set cn = CreateObject("ADODB.Connection")
     Set rs = CreateObject("ADODB.Recordset")

     cn.Open "Provider=MS Remote;Remote Provider=MSDASQL;" & _
             "Remote Server=http://;" & _
             "DSN=RDSDemo;UID=admin;PWD=;"

     rs.CursorLocation = adUseClient
     rs.Open "SELECT * FROM Authors", cn
				

You can find the latest documentation on RDS at the following site:

You can download the latest version of the Microsoft Data Access Components, including the Remote Data Services, from the following site:

Please visit the Microsoft Universal Data Access Web site for more information:

The code in the following Microsoft Knowledge Base article was taken
from the RDSVB sample, which demonstrates using RDS within Visual Basic:

183609

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

FILE: Rdsvb.exe Demonstrates How to Use RDS with Visual Basic

Article ID: 183294 – Last Review: August 9, 2012 – Revision: 7.0


Applies to
  • Microsoft Data Access Components 2.5
  • Microsoft Data Access Components 2.6
  • Microsoft Data Access Components 2.7
kbdatabase kbinfo KB183294

See the article here:
INFO: Techniques for Returning a Recordset Through RDS

ACC97: Using Microsoft Jet with IIS

When you need unlimited users, 24×7 support, and ACID
transactions, Microsoft strongly recommends that you use Microsoft SQL Server
with Internet Information Server (IIS). Although Active Server Pages (ASP)
works with any OLEDB and ODBC-compliant database, IIS has been extensively
tested and is designed to work with Microsoft SQL Server when doing high
transaction traffic and unlimited users that can occur in an Internet
scenario.

NOTE: “ACID” is an acronym for the four properties of
transaction-processing systems: Atomicity, Consistency, Isolation, Durability.

ASP also supports using the Microsoft Jet database engine as a valid
data source. The Access ODBC Driver and Microsoft OLE DB Provider for Microsoft
Jet are not intended to be used with high-stress, high-concurrency, 24×7 server
applications, such as web, commerce, transactional, messaging servers, and so
on.

When running Microsoft Jet in an IIS environment, it is
recommended that you use the native Jet OLE DB Provider in place of the
Microsoft Access ODBC driver. The Microsoft Access ODBC driver (Jet ODBC
driver) can have stability issues due to the version of Visual Basic for
Applications that is invoked because the version is not thread safe. As a
result, when multiple concurrent users make requests of a Microsoft Access
database, unpredictable results may occur. The native Jet OLE DB Provider
includes fixes and enhancements for stability, performance, and thread pooling
(including calling a thread-safe version of Visual Basic for Applications).

Both the ODBC driver and OLE DB Provider provide a wrapper around
the Microsoft Jet database engine, which provides the core functionality of
both the Access ODBC driver and Jet OLE DB Provider. While Microsoft Jet is
consciously (and continually) updated with many quality, functional, and
performance improvements, it was not intended (or architected) for the
high-stress performance required by 24×7 scenarios, ACID transactions, or
unlimited users, that is, scenarios where there has to be absolute data
integrity or very high concurrency. Microsoft has performed very robust
Multi-User/Stress scenarios that are designed to verify functionality in the
appropriate usage space of Microsoft Jet, and addresses any issues that may be
revealed.

The latest OLE DB provider for Microsoft Jet can be
obtained from the following sources.
The OLE DB provider for Microsoft Jet is included in the
following products:
  • Microsoft Visual Basic 6.0 Enterprise
  • Microsoft Visual Studio 6.0 Enterprise
  • Microsoft Visual C++ 6.0 Enterprise
For additional information about using the Microsoft Jet
database engine and the native Jet OLE DB Provider, please see the following
articles in the Microsoft Knowledge Base:
191754

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

How to Open Secured Microsoft Access Database In ADO 2.0 Through OLE DB

185033

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

Adoacc.exe Demonstrates Using ADO with MS Access 97

172403

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

ADOVB.exe Demonstrates How to Use ADO with Visual Basic

Information about Microsoft Jet and the native Jet
OLE DB Provider can also be found in the following documentation:

  • “The Microsoft Jet Database Engine Programmer’s guide (2nd
    Edition)” offers extensive discussion on the tuning, usage, and limitations of
    the Microsoft Jet database engine.
  • The file, JOLTREAD.TXT, which ships with the products
    listed in the “More Information” section earlier in this article.

Article ID: 222135 – Last Review: August 9, 2012 – Revision: 7.0


Applies to
  • Microsoft Access 97 Standard Edition
  • Microsoft Internet Information Server 3.0
  • Microsoft Internet Information Services 5.0

View article:
ACC97: Using Microsoft Jet with IIS

Error message when you print a batch edit list or post a batch in General Ledger in Microsoft Dynamics GP: "The stored procedure glpBatchCleanup returned the following results: DBMS 0, Great Plains 20488"

When you print a batch edit list or post a batch in General Ledger in Microsoft Dynamics GP, you receive the following error message:

The stored procedure
glpBatchCleanup returned the following results: DBMS 0, Great Plains
20488

Cause 1

This problem may occur if the SY00500 – Posting Definitions Master table is damaged. To resolve this problem, see
Resolution
1
.

Cause 2

The stored procedure for glpBatchCleanup may be corrupted. To re-create the stored procedures, see Resolution
2
.

Cause 3

Third-party products may be altering the stored procedures incorrectly. For information about how to disable third-party products, see Resolution 3.


Resolution 1

To resolve this problem, re-create the SY00500 – Posting
Definitions Master table. To re-create this table, use one of the following
methods.

Note If the SY00500 table contains a trigger, the trigger must be
re-created after you follow these steps.

Method 1: Use SQL Maintenance
  1. Make a full backup of Microsoft Dynamics GP.
  2. From the Microsoft Dynamics GP menu, point to Maintenance, and then click SQL.
  3. Click the company database that is receiving the
    error.
  4. In the Table list, click Posting
    Definitions Master
    .
  5. On the right side of the window, click to select every
    check box, and then click Process.
  6. Click
    Yes when you receive the following message:

    You have selected to drop tables;
    this will delete any data in them. Are you sure you want to
    continue?

This procedure re-creates the SY00500 – Posting Definitions Master table. However, you will temporarily lose all unposted batches. To retrieve these unposted batches, run the Check Links program on the sub modules. Then, reconcile the batches for General Ledger. However, this sets any batches that are set to Recurring to
Single Use. You must change these batches back to
Recurring.

To retrieve the batches, follow these
steps.

Note If you use the Multicurrency option in Payables Management in Microsoft Dynamics GP, run the Check Links
program on the Payables Transaction History Logical file before you run the
Check Links program on the Payables Transaction Logical file.

  1. To run the Check Links program on the following files,
    from the Microsoft Dynamics GP menu, click Maintenance, click
    Check Links, click one of the following series names, and then
    type the corresponding file name. Follow this step for the following files:

    • Series name: Payables Management

      File name: Purchasing Series – Payables Transaction Logical
    • Series name: Purchase Order Processing

      File name: Purchasing Series – Purchasing Transaction Logical
    • Series name: Receivables Management

      File name: Sales Series – Receivables Open Transaction
    • Series name: Invoicing

      File name: Sales Series – Invoice Work File
    • Series name: Sales Order Processing

      File name: Sales – Sales Work File
    • Series name: Inventory

      File name: Inventory – Inventory Transaction Work file
    • Series name: Bill of Materials

      File name: Inventory – Inventory – Bill of Materials Transactions file
  2. If you use Project Accounting with Microsoft Dynamics GP, you must also run Check Links on the following files. To run
    Check Links on the following files, on the Microsoft Dynamics GP menu, point to Maintenance, click PA Check Links, click Insert, and then
    click one of the following table names. Follow this step for the following
    files:

    • Timesheet Batches – PA Timesheet Transactions
    • Miscellaneous Log Batches – PA Miscellaneous Log Transactions
    • Equipment Log Batches – PA Equipment Log Transactions
    • Inventory Transfer Batches – PA Inventory Transfer Transactions
    • Receivings Batches – PA Purchasing Transactions
    • Revenue Recognition Batches – PA Revenue Recog Transactions
    • Employee Expense Batches – PA Employee Expense Transactions
    • Billing Batches – PA Billing Transactions
  3. If any batches exist in Microsoft Great Plains General Ledger, on the Microsoft Dynamics GP menu, point to Tools,
    point to Utilities, point to Financial, and then click Reconcile.
    Click to select the Batches check box, and then click Reconcile to
    reconcile your batches.
Method 2: Use the free toolkit from Professional Services Tools Library
  1. Make a full backup of Microsoft Dynamics GP.
  2. Have all users log off from the system.
  3. Install the Professional Services Tools Library (PSTL). To
    do this, visit the following CustomerSource website:Note This download is located under Downloads and Updates, Service Packs & Product Releases, Professional Services Tools Library (PSTL) for Microsoft Dynamics (North America Only). Installation instructions are included with the
    download.
  4. After you install the PSTL, start Microsoft Dynamics GP.
    When you are prompted to include new code, click Yes.
  5. Log on to Microsoft Dynamics GP as the system
    administrator.
  6. To add Professional Services Tools Library to the shortcut bar, in your Home series, click Add, click Other
    Window
    , expand Technical Service Tools, expand
    Project, click Professional Tools Library,
    click Add, and then click Done.
  7. On the Home series shortcut bar, click Professional Service
    Tools
    . Wait for the SQL objects build. When you are prompted to enter
    registration keys, click Cancel. You do not have to have registration
    keys to use this tool.
  8. Click Toolkit, and then click
    Next.
  9. Under Toolkit Options, click
    Recreate SQL Objects, and then click
    Next.
  10. Next to Series, click
    Company.
  11. Next to Table, click
    SY00500.
  12. Under Maintenance Options, click to select
    the Recreate Selected Table check box, and then click to
    select the Recreate data for selected table(s) check
    box.
  13. Click Perform Selected Maintenance.
  14. When you receive the following messages, click
    OK:

    Table will be recreated with
    data

    SY00500 table will be recreated with
    data. Verify a backup has been made before proceeding

    SY00500 has been recreated


Resolution 2

Re-create the stored procedures for both glpBatchCleanup and glpBatchPost by using Database Maintenance. To do this, follow these steps:

  1. Make sure all users are logged off from Microsoft Dynamics GP.
  2. Click the Start, click All Programs, click Microsoft Dynamics GP, click the version of Microsoft Dynamics GP on which this problem occurs, and then click Database Management.
  3. Enter the Server Name for the Dynamics Server that you are using. For example, use the following:

    COMPUTER_NAMESERVER_INSTANCE

  4. Click to select the DYNAMICS Database ID check box, and then click Next.
  5. Click to select the Microsoft Dynamics GP check box, and then click Next.
  6. Click to select the Functions check box, and then click Next.


Resolution 3

Third-party products may be altering the stored procedures. Disable any third-party products from the Dynamics.set file, and test again. For more information about how to disable third-party products in the Dynamics.set file, click the following article number to view the article in the Microsoft Knowledge Base:

872087

(http://support.microsoft.com/kb/KB 872087/
)

How to disable third-party products or temporarily disable additional products in the Dynamics.set file in Microsoft Dynamics GP

Article ID: 896545 – Last Review: August 8, 2012 – Revision: 11.0


Applies to
  • Microsoft Dynamics GP 2010
  • General Ledger, when used with:
    • Microsoft Dynamics GP 10.0
    • Microsoft Dynamics GP 9.0
    • Microsoft Business Solutions–Great Plains 8.0
kberrmsg kbmbsmigrate kbprb KB896545

Other Support Sites

Community

Get Help Now

Article Translations

Link:
Error message when you print a batch edit list or post a batch in General Ledger in Microsoft Dynamics GP: "The stored procedure glpBatchCleanup returned the following results: DBMS 0, Great Plains 20488"

An error occurs on the Microsoft Dynamics CRM 2011 for Outlook client when signing in to an Office 365 Services CRM organization: "The Microsoft Online Services Sign-in Assistant is not installed"

When you try to sign in to an Office 365 Services CRM organization, you may receive the following error even though the Microsoft Online Services Sign-In Assistant is installed:

Cannot connect to Microsoft Dynamics CRM server because we cannot authenticate your credentials. Check your connection or contact your admin for more help.

In the logfile, the following message will be displayed:

The Microsoft Online Services Sign-in Assistant is not installed. To download and install the Microsoft Online Services Sign-in Assistant please download it using the following locations: 32-bit: http://g.microsoftonline.com/0BX00en/500 64-bit: http://g.microsoftonline.com/0BX00en/501

At this point, the sign-in fails.

If the organization has been moved from a Dynamics CRM Online organization with Update Rollup 6 to an Office 365 Services CRM organization without installing the Office 365 prerequisite package or without reinstalling the Update Rollup 6 slipstream update, this error will occur. This error will also occur if the Microsoft Dynamics CRM for Outlook client has had any updates applied after RTM and then being setup for the Office 365 services CRM organization. 
Note This is a “FAST PUBLISH” article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Article ID: 2696603 – Last Review: August 8, 2012 – Revision: 4.0


Applies to
  • Microsoft Dynamics CRM 2011
kbmbsmigrate kbsurveynew KB2696603

Link:
An error occurs on the Microsoft Dynamics CRM 2011 for Outlook client when signing in to an Office 365 Services CRM organization: "The Microsoft Online Services Sign-in Assistant is not installed"

Service Packs That Are Compatible with BackOffice Small Business Server

This article lists the products and service packs that are included with BackOffice Small Business Server (SBS), and lists the compatibility of individual service packs with the SBS suite.

Included Products and Services

The following products and service packs are included with BackOffice Small Business Server.

BackOffice Small Business Server 4.0

BackOffice Small Business Server 4.5

  • Microsoft Windows NT Server 4.0 with Service Pack 4
  • Microsoft Proxy Server 2.0
  • Microsoft Internet Information Server 4.0
  • Microsoft SQL Server 7.0
  • Microsoft Exchange Server 5.5

Available Add-ons

The following add-ons are available for use with BackOffice Small Business Server:

BackOffice Small Business Server 4.0

BackOffice Small Business Server 4.5

Microsoft Proxy Server 2.0:

Proxy Server service packs are fully compatible with Small Business Server 4.5. For updates, refer to the following Microsoft Web site:

Microsoft Internet Information Server 4.0:

There are no updates available for this product.

Microsoft SQL Server 7.0:

SQL Server updates are fully compatible with Small Business Server 4.5. For updates, refer to the following Microsoft Web site:

Microsoft Exchange Server 5.5:

Exchange Server service packs are fully compatible with Small Business Server 4.5. For updates, refer to the following Microsoft Web site:

Upgrades to SBS 2000

You cannot upgrade SBS 4.0 to SBS 2000. For more information about SBS 2000, visit the following Microsoft Web site. http://technet.microsoft.com/en-us/sbs/bb630247.aspx

(http://technet.microsoft.com/en-us/sbs/bb630247.aspx)

Article ID: 281925 – Last Review: August 7, 2012 – Revision: 5.0


Applies to
  • Microsoft BackOffice Small Business Server 4.0
  • Microsoft BackOffice Small Business Server 4.5

Read More:
Service Packs That Are Compatible with BackOffice Small Business Server

Combat Flight Simulator 3: Known Hardware-Related Issues

This article describes the known hardware-related issues
that you may experience when you play Microsoft Combat Flight Simulator
3.

The following describes the known hardware-related issue in
Combat Flight Simulator 3:
The
third-party products that are discussed in this article 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 Combat Flight
Simulator 3, visit the following Microsoft Web site:

For more information about Microsoft games, visit the following
Microsoft Web site:

Article ID: 331565 – Last Review: August 7, 2012 – Revision: 1.0


Applies to
  • Microsoft Combat Flight Simulator 3: Battle for Europe
kbconfig kbhardware kbinfo KB331565

View original post here:
Combat Flight Simulator 3: Known Hardware-Related Issues

Page 323 of 734« First...102030...321322323324325...330340350...Last »

Recent Comments

    Archives

    Categories