Actually, as the conflict was with a Microsoft product for point of sale or retail operations (I am not sure which) they simply inserted a script that blocks both Vista SP1 and XP SP3 from trying to install if it detects that product on the machine.
They promise a real fix shortly. Meanwhile, the installing public does not have to worry.
Jack, the fix is out. Hot Fix available for XP SP3 and Vista SP1 - BTW, this problem also affects Windows server 2008.
Problem is a conflict with SQL Server that causes incorrect data to be returned under certain circumstances. Also causes problems with MDAC and the runtime version of MS-SQL (MSDE) that is embedded in a number of programs (one that I'm aware of is "Neat Receipts", which uses an SQL database to catalog receipts you've scanned in).
Look at Knowledge Base Article 951937 for the gory details. You can submit an online request for the Hot Fix if you require it.
Actually, as the conflict was with a Microsoft product for point of sale or retail operations (I am not sure which) they simply inserted a script that blocks both Vista SP1 and XP SP3 from trying to install if it detects that product on the machine.
ReplyDeleteThey promise a real fix shortly. Meanwhile, the installing public does not have to worry.
Jack
Jack, the fix is out. Hot Fix available for XP SP3 and Vista SP1 - BTW, this problem also affects Windows server 2008.
ReplyDeleteProblem is a conflict with SQL Server that causes incorrect data to be returned under certain circumstances. Also causes problems with MDAC and the runtime version of MS-SQL (MSDE) that is embedded in a number of programs (one that I'm aware of is "Neat Receipts", which uses an SQL database to catalog receipts you've scanned in).
Look at Knowledge Base Article 951937 for the gory details. You can submit an online request for the Hot Fix if you require it.