Fixes a problem when you can create a duplicate serial number in the same site but a different warehouse bin location for an inventory ID. This occurs when you do a return in the "Inventory Issues (10.020.00)" screen.

Resolves a problem in which the QtyOnHand field in the LotSerMst table is updated incorrectly when a shipper is processed for a lot-numbered item when multiple records are entered in the Bin/Lot/Serial (40.110.06) screen for the same InvtId, Lot, Whse Bin Loc combination.

When this issue occurs, the following error message is logged in the SQL Server setup log file: Detail_ComponentUpdate.txt. { Slp: MSI Error: 1935 An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'.

Learn how to scan and repair missing or corrupted system files using the System File Checker tool (SFC.exe) and the Deployment Image Servicing and Management tool (DISM.exe). Follow the steps to run the commands, view the details, and replace the corrupted files manually.

To provide the hotfix for when the Manifest Entry (40.115.00) screen allows for "Shipping Confirmed" when there's insufficient inventory, even though the Shippers (40.110.00) screen produces System Message 6678 in Microsoft Dynamics SL.

Fixes a system message 18, "Entry must be greater than or equal to zero," error when you copy a revenue schedule that will cause the percent to go negative in Microsoft Dynamics SL environments.

When you try to post a purchase credit memo for an item that is used in a job and has a bin mandatory location code specified, you receive the following error message: Quantity (Base) must be greater than 0 in Bin Content Location Code=' location code '; Bin Code=' bin code ';Item No.=' item ';Variant Code='',Unit of Measure Code=' PCS '.

Fixes a problem in which you receive a “Could not load file or assembly 'Microsoft.AnalysisServices.AdomdClientUI” error message when a Process Full operation is run in SQL Server.

1: Logs errors only. 2: Verbose logging. The default value for the Log File Max Size entry is 64 kilobytes (KB). When a log file reaches this size, the log file will be backed up to Log_file_name.lo_, and a new log file starts collecting entries. The only exception to this is the Framework.log file.

Learn how to fix the error code 1619 that occurs when you run an unattended setup to upgrade to Exchange Server from PowerShell by using Setup.exe. The problem is caused by the wrong path to the setup file and the language pack file.