Microsoft

You encounter printing issues after a new OEM print driver, a printer hotfix, or a service pack is installed on a Windows Server 2003-based clustered printer server

On a Windows Server 2003-based clustered printer server, you install one of the following: A new OEM printer driver A printer hotfix A service pack that updates the Unidrv.dll file or the Ps5ui.dll file After you take this action, you may experience one or more of the following symptoms: The printing performance is decreased. Print jobs take a long time to be completed. Delays occur when you try to view printer properties. Failures occur during a cluster node join process. This problem may occur if you install a new OEM printer driver, a printer hotfix, or a service pack on a Windows Server 2003-based clustered printer server that has many Microsoft Universal Print driver (Unidrv)-based Printer Control Language (PCL) printer drivers or many PostScript (PScript5)-based PS printer drivers installed. When you install a new OEM printer driver, a printer hotfix, or a service pack that updates the Unidrv.dll file or
Read more …

You cannot restore a database from a backup file when you use a SQL Server login ID that has the dbcreator server role to connect to an instance of SQL Server 2005

Consider the following scenario: In SQL Server Management Studio, you use a SQL Server login ID that has the dbcreator server role to connect to an instance of Microsoft SQL Server 2005. You try to restore a database from a database backup file. In the Specify Backup dialog box, you specify File as the backup media, and then you click Add. You receive an error message that resembles the following: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackupCannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists. If you know that the service account can access a specific file, type in the full path for the file in the File Name control in the Locate dialog box. You click OK to dismiss the error message. In the Locate Backup File dialog box, you specify the database backup and file
Read more …

Changes to the IP restriction list of an FTP site are not applied until you restart the FTP service in IIS 6.0

In Internet Information Services (IIS) 6.0, changes to the IP restriction list of an FTP site are not applied until you restart the FTP service. For example, suppose that you deny all users permission to access an FTP site, and then you allow a particular IP address to access the site. When you then use the ftp command to try to access the site, you may receive an error message that resembles the following: 530 Connection refused, unknown IP address.421 Service not available, closing control connection.Connection closed by remote host. However, after you restart the FTP service, the command-line interaction resembles the following: Connected to ftp.servername.domain220 Microsoft FTP ServiceUser: domainuser331 Password required for domainuser.Password:230 User domainuser logged in. In IIS 6.0, changes to the IP restriction list are applied only after you restart the FTP service. However, the FTP service will re-read and apply changes to the IP restriction list
Read more …

USB Isochronous Transfers Not Accessed by Hardware

Source: Microsoft Support RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION. USB Isochronous transfers to a High-Speed USB device may complete later than scheduled, often with no packets transferred.  This may occur when the StartFrame value is explicitly set to a large value after current frame (for example, more than 16ms from the Current Frame). To help reduce the amount of power consumed by USB host controllers, Windows Vista disables the periodic scheduler for the USB 2.0 Enhanced (EHCI) host controller if there are no periodic transfers pending.  USB Periodic Transfers include Isochronous and Interrupt transfer types.  On the RTM version of Windows Vista, a check is scheduled every 500ms (1/2 second) to re-enable the periodic scheduler if any periodic transfers have been queued. If periodic transfers are queued while the periodic scheduler is disabled, they will not
Read more …

USB Device Using Bulk Transfers Experiences Buffer Overflows

Source: Microsoft Support RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION. A USB device which transfers data using the USB Bulk transfer type (Bulk Endpoint) may lose data due to a buffer overflow on the device.  This may occur if the device has data that must be transferred to the host computer in a timely manner (such as streaming video/audio data, or continuously-generated serial or telemetry data), and will experience a buffer overflow and loss of some data if the USB Bulk transfers do not occur within a specific time. This symptom may occur when the USB device is connected to a computer running Windows Vista or Windows Server 2008, even if no similar buffer overflows and loss of data occur when the USB device is connected to a computer
Read more …

FIX: The Inetinfo.exe process terminates unexpectedly under high stress when IIS hosts many application pools

When Internet Information Server (IIS) 6.0 hosts many application pools, the Inetinfo.exe process terminates unexpectedly under high stress. When this problem occurs, you receive an error message that resembles one of the following messages in the event log: Message 1Message 2Message 3 This problem occurs because of an issue in the Coadmin.dll file. The cleanup code for the initialization of IIS configuration metadata is not thread safe. Therefore, the Web server can encounter a race condition under heavy stress. The race condition causes heap corruption in the Inetinfo.exe process. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: 824684 Description of the standard terminology that is used to describe Microsoft software updates

FIX: Message type MT051 and message type MT081 fail the BRE validation when you use Microsoft BizTalk Accelerator for SWIFT Message Pack 2008

When you use Microsoft BizTalk Accelerator for SWIFT 2008 Message Pack, message type MT051 and message type MT081 fail the Business Rule Engine (BRE) validation. When this problem occurs, you receive an event error message that resembles the following: This problem occurs because Microsoft BizTalk Accelerator for SWIFT Message Pack 2008 was released before the MT Standards Release 2008 (SR2008) update was received. Per the SR2008 update, the SystemNewsVersion_209 field should no longer exist in the SWIFT message schemas or in SWIFT InfoPath forms for message type MT051 and for message type MT081. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. For more informations, click the following article number to view the article in the Microsoft Knowledge Base: 925731 BizTalk Accelerator for SWIFT 2008 Message Pack is available For more information about software update terminology, click the following
Read more …

FIX: A Stop error or a crash occurs on the operating system when you profile an application by using Visual Studio 2008 Service Pack 1

You may experience a Stop error, or the operating system may crash when you create a profile of an application by using Microsoft Visual Studio 2008 Service Pack 1 (SP1). The problem occurs when the following conditions are true: You use the sampling profiling method. The computer is running on the Intel Nehalem processor. This problem occurs because the sampling profiler uses a driver in the operating system. However, the Intel Nehalem processor was created after the release of the 2008 version of the profiler. Because the sampling feature of the profiler is specific to the driver per processor, it was not possible to be completely compatible with the Nehalem processor before the release. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section. If you experience the same error when you use Microsoft Visual Studio 2005 SP1, apply hotfix
Read more …

FIX: The execution plan does not use the forced index when you use the INDEX optimizer hint in a query that runs against a synonym in SQL Server 2005

Microsoft distributes Microsoft SQL Server 2005 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2005 fix release. In Microsoft SQL Server 2005, you create a synonym for a table. You run a query against the synonym. The query uses the INDEX optimizer hint to force an index. If you examine the execution plan that is generated for the query, you may find the execution plan does not use the forced index. The fix for this issue was first released in Cumulative Update 2 for SQL Server 2005 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 961930 Cumulative update package 2 for SQL Server 2005 Service Pack 3 Note Because the builds
Read more …

A Terminal Server smartcard logon using RDP 6.0 may fail with error code 0x507

Source: Microsoft Support RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION. A Terminal Server smartcard logon using RDP 6.0 may fail with error code 0x507 (authentication error).   Error code details: Hex: 0x507 Decimal: 1265 Symbolic Error:  ERROR_UNIDENTIFIED_ERROR Friendly Error: Insufficient information exists to identify the cause of failure. For smartcard authentication to work over terminal services, the user certificate must be present in the certificate store, and it must match the selected certificate on the smartcard. This is unlike local logon where the certificate only needs to be present on the smartcard. If the Certificate Propagation service (certpropsvc) is not running on the client machine, the certificate is not propagated to the user store. This leads to the error condition. This is usually seen
Read more …


  • Instructions
    Windows 10, Windows 7, Windows XP & 2000

    To Fix this issue you need to follow the steps below:

    Step 1:

    Download Repair Tool

    Step 2:

    Click the "Scan" button

    Step 3:

    Click 'Fix All' and you're done!

    Compatibility: Windows 10, Windows 7, Vista, XP

    Download Size: 1.5MB

    Requirements: 300 MHz Processor, 256 MB Ram, 22 MB HDD

    Limitations:trial version offers an unlimited number of scans, backup, restore of your windows registry for FREE. registration for the full version is $29.95 USD for 1-year subscription to use all the features.