Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts

Friday, March 30, 2012

recent SQL 2005 hotfix creates problem

Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
Hi
"fj" wrote:

> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sql run_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John
|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
....
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
....
|||Hi
"fj" wrote:

> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E, Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a 1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget, Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John
|||"John Bell" wrote:

> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ
|||Hi
"fj" wrote:

>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John
|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ
|||Hi
"fj" wrote:

> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John
sql

recent SQL 2005 hotfix creates problem

Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in th
e
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.Hi
"fj" wrote:

> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. Th
e
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 140
6
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in
the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB
932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_
dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:

> Here is the part I found that might cause the problem. The specified Featu
re
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_non
e_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object
:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Too
ls
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found i
n
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:

> Hi
> "fj" wrote:
>
> SQL Express is not one of the products that have been listed as affected b
y
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:

>
> "John Bell" wrote:
>
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix
is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need thi
s
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:

> Thanks John,
> Actually I found the problem is because I didn't install the client tool a
nd
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need t
his
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is
a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John

recent SQL 2005 hotfix creates problem

Here are the errors in event log. The installation packeage keeps trying
every 3 hours. How shouyld I fix it.
Microsoft SQL Server 2005 Tools Express Edition -- Install started.
Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
installer has encountered an unexpected error. The error code is 2711. The
specified Feature name ('SQL_Documentation') not found in Feature table.
Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
not be installed. Error code 1603. Additional information is available in the
log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.Hi
"fj" wrote:
> Here are the errors in event log. The installation packeage keeps trying
> every 3 hours. How shouyld I fix it.
>
> Microsoft SQL Server 2005 Tools Express Edition -- Install started.
> Product: Microsoft SQL Server 2005 Tools Express Edition -- Error 2711. The
> installer has encountered an unexpected error. The error code is 2711. The
> specified Feature name ('SQL_Documentation') not found in Feature table.
> Product: Microsoft SQL Server 2005 Tools Express Edition - Update 'GDR 1406
> for SQL Server Tools and Workstation Components 2005 ENU (KB932557)' could
> not be installed. Error code 1603. Additional information is available in the
> log file C:\Program Files (x86)\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB932557_sqlrun_tools.msp.log.
What does this log say?
It may be similar to http://support.microsoft.com/kb/916760/en-us
or http://support.microsoft.com/kb/834484/en-us i.e. the permissions or
folders expected may not exist or have the wrong permissions or the account
doing the install may not have enough permissions.
John|||Here is the part I found that might cause the problem. The specified Feature
name ('SQL_Documentation') not found in Feature table.
...
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
Express Edition -- Error 2711. The installer has encountered an unexpected
error. The error code is 2711. The specified Feature name
('SQL_Documentation') not found in Feature table.
Error 2711. The installer has encountered an unexpected error. The error
code is 2711. The specified Feature name ('SQL_Documentation') not found in
Feature table.
Action ended 9:51:03: CostFinalize. Return value 3.
Action ended 9:51:03: INSTALL. Return value 3.
Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\
...|||Hi
"fj" wrote:
> Here is the part I found that might cause the problem. The specified Feature
> name ('SQL_Documentation') not found in Feature table.
>
> ...
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> Express Edition -- Error 2711. The installer has encountered an unexpected
> error. The error code is 2711. The specified Feature name
> ('SQL_Documentation') not found in Feature table.
> Error 2711. The installer has encountered an unexpected error. The error
> code is 2711. The specified Feature name ('SQL_Documentation') not found in
> Feature table.
> Action ended 9:51:03: CostFinalize. Return value 3.
> Action ended 9:51:03: INSTALL. Return value 3.
> Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> Property(S): ProductLanguage = 1033
> Property(S): Manufacturer = Microsoft Corporation
> Property(S): ProductVersion = 9.00.1399.06
> Property(S): MEDIAPACKAGEPATH = \Setup\
> ...
SQL Express is not one of the products that have been listed as affected by
the hotfix!
http://support.microsoft.com/kb/932557/en-us
John|||"John Bell" wrote:
> Hi
> "fj" wrote:
> > Here is the part I found that might cause the problem. The specified Feature
> > name ('SQL_Documentation') not found in Feature table.
> >
> >
> >
> > ...
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > Express Edition -- Error 2711. The installer has encountered an unexpected
> > error. The error code is 2711. The specified Feature name
> > ('SQL_Documentation') not found in Feature table.
> >
> > Error 2711. The installer has encountered an unexpected error. The error
> > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > Feature table.
> > Action ended 9:51:03: CostFinalize. Return value 3.
> > Action ended 9:51:03: INSTALL. Return value 3.
> > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > Property(S): ProductLanguage = 1033
> > Property(S): Manufacturer = Microsoft Corporation
> > Property(S): ProductVersion = 9.00.1399.06
> > Property(S): MEDIAPACKAGEPATH = \Setup\
> > ...
> SQL Express is not one of the products that have been listed as affected by
> the hotfix!
> http://support.microsoft.com/kb/932557/en-us
> John
Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
installed by auto-update.
Now it seems like there is a scheduled job at somewhere, how I can stop or
remove it?
Is the hotfix referred by your link a fix to the problem?
Thanks
-FJ|||Hi
"fj" wrote:
>
> "John Bell" wrote:
> > Hi
> >
> > "fj" wrote:
> >
> > > Here is the part I found that might cause the problem. The specified Feature
> > > name ('SQL_Documentation') not found in Feature table.
> > >
> > >
> > >
> > > ...
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key:
> > > payload_ul.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E , Object:
> > > C:\WINDOWS\winsxs\x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1\
> > > MSI (s) (80:34) [09:51:03:575]: Dir (target): Key: VSRetarget , Object:
> > > C:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\
> > > MSI (s) (80:34) [09:51:03:575]: Note: 1: 2711 2: SQL_Documentation
> > > MSI (s) (80:34) [09:51:03:887]: Product: Microsoft SQL Server 2005 Tools
> > > Express Edition -- Error 2711. The installer has encountered an unexpected
> > > error. The error code is 2711. The specified Feature name
> > > ('SQL_Documentation') not found in Feature table.
> > >
> > > Error 2711. The installer has encountered an unexpected error. The error
> > > code is 2711. The specified Feature name ('SQL_Documentation') not found in
> > > Feature table.
> > > Action ended 9:51:03: CostFinalize. Return value 3.
> > > Action ended 9:51:03: INSTALL. Return value 3.
> > > Property(S): ProductCode = {2750B389-A2D2-4953-99CA-27C1F2A8E6FD}
> > > Property(S): ProductLanguage = 1033
> > > Property(S): Manufacturer = Microsoft Corporation
> > > Property(S): ProductVersion = 9.00.1399.06
> > > Property(S): MEDIAPACKAGEPATH = \Setup\
> > > ...
> >
> > SQL Express is not one of the products that have been listed as affected by
> > the hotfix!
> > http://support.microsoft.com/kb/932557/en-us
> >
> > John
> Yeh, the VS 2005 is installed on the box but SQL Express is not. This fix is
> installed by auto-update.
> Now it seems like there is a scheduled job at somewhere, how I can stop or
> remove it?
> Is the hotfix referred by your link a fix to the problem?
> Thanks
> -FJ
It looks like you may have something left over then, if you have removed it.
You may want to check out:
http://msdn2.microsoft.com/en-us/vstudio/aa718704.aspx
or http://support.microsoft.com/kb/909967
John|||Thanks John,
Actually I found the problem is because I didn't install the client tool and
documents from the original 2005 SQL Server(64bit). BUT, the auto-update
downloaded the hotfix for the SQL server 2005 without checking if I need this
fix. This hotfix (MSDN article number 932557) has "hardwired" update for
those tools and docs whch I don't have so the update failed.
Since the update is scheduled to launch every 3 hours, I am keep getting
this annoying errors.
Now my question still remains, how I can terminate the remaining update
manually? Is there a way to intercept MicroSoft's auto-update?
I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
bug in this hotfix and Microsoft needs to know that.
Thanks
-FJ|||Hi
"fj" wrote:
> Thanks John,
> Actually I found the problem is because I didn't install the client tool and
> documents from the original 2005 SQL Server(64bit). BUT, the auto-update
> downloaded the hotfix for the SQL server 2005 without checking if I need this
> fix. This hotfix (MSDN article number 932557) has "hardwired" update for
> those tools and docs whch I don't have so the update failed.
> Since the update is scheduled to launch every 3 hours, I am keep getting
> this annoying errors.
> Now my question still remains, how I can terminate the remaining update
> manually? Is there a way to intercept MicroSoft's auto-update?
> I don't think I need to re-install or remove VS2005 or SQL 2005. There is a
> bug in this hotfix and Microsoft needs to know that.
> Thanks
> -FJ
Why not install the tools, allow the update or manually install the update
and then remove the tools?
Automatic updates are not something you would want on a production system so
you may want to turn them off, but the problem could still occur if you
turned them on at some point.
John

Receiving errors when using foreach loop and excel connection manager...

Purpose: Need to import excel source data into SQL Server 2005 tables. Excel source data comes in nulitple excel files with the same structure but different data. I would appreciate someone taking a look at the following information and notifying me of what I am doing incorrectly.

I Inserted a foreach loop container, a data flow task located inside the foreach loop contaiiner, an excel and SQL Server 2005 connections.

After trying multiple times I went the following URL and followed step by step direction on how to connect excel workbooks dynamically: http://msdn2.microsoft.com/en-us/library/ms345182.aspx . I also used http://www.sqlstrings.com/ as a reference when creating the connection string.

Creating a Foreach Loop Container:

1. Opened foreach loop container 2.Set the Enumerator to 'Foreach File Enumerator" and configured the enumerator by setting the directory location and file base name to E:\Clients\Dep Comm\BEA\BEA_Test_Source and *PersonnelExpense*.xls respectively. 3. Clicked Variable Mapping; created two variables called, "ExcelFile", and "ExtProperties" and closed out of the foreach loop container.

I. Created Excel Connection:

  1. Created excel connection called, “Dynamic Excel Connection Manager,” that initially pointed to one of the excel workbooks.
  2. Went to the connection properties by right clicking the connection manager.
  3. Expanded Expressions and clicked the ellipsis button to bring up property expressions
  4. Chose Connection String in the Property.
  5. Clicked the Expression Ellipsis button.
  6. Put the following inside the Expression multi line text box:

A. "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" +@.[User::ExcelFile] + ";Extended Properties=\"" + @.[User::ExtProperties] + "\""

  1. Clicked the Evaluate Expression button to get the following:
    1. Provider=Microsoft.Jet.OLEDB.4.0;Data Source=;Extended Properties=""
  2. Clicked Ok button
  3. Inserted a Data flow task inside the foreach loop container.

II. Configured Tasks that is associated with Dynamic Excel Connection Manager or Package:

  1. Set the Foreach loop container Delay Validation to true.
  2. Set the Data Flow Task Container Delay Validation to true.
  3. Set the Dynamic Excel Connection Manager Delay Validation to true.
  4. Set the SQL Server Connection Manager Delay Validation to true.
  5. Set the Package Delay Validation to true.
  6. Package Locale ID set to English

Ran the package after connecting the excel source data flow to the OLEDB destination and have inserted part of the error in this post. Please see below.

Error: 0xC0202009 at Package, Connection manager "Dynamic Excel Connection Manager": An OLE DB error has occurred. Error code: 0x80004005.

An OLE DB record is available.Source: "Microsoft JET Database Engine"Hresult: 0x80004005Description: "Could not find installable ISAM.".

I modified the connection string after receiving the error by removing the extended properties. The following is the modified connection string: "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" +@.[User::ExcelFile]

I repeated step I.6 above and received the following expression: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=

I ran the package and received the following error in part: OLE DB record is available.Source: "Microsoft JET Database Engine"Hresult: 0x80004005Description: "Unrecognized database format 'E:\Clients\Dep Comm\BEA\BEA_Test_Source\PersonnelExpense_OCCs_051007.xls'."

I did not find anything helpful when I searched for the above errors and would very much appreciate anyone’s assistance on this issue as this issue needs to be taken care of ASAP.

Does anyone have any ideas as to why I received this error and what can I do to resolve this issue?

Your assistance in this matter is truly appreicated!

Thanks!!

Lee

Are there headers on the Excel spreadsheets?

The error is looking for a database format where the headers are matched as column headers.

If there are no headers, it doesnt' know how to match it.

Just my twist on it,

Adamus

|||

Hi Adamus,

I appreciate your feedback. To answer your question, the first row does contain column headers.The data flow task has an excel source file which uses the Dynamic Excel Connection manager that I mentioned in my original post. The excel source file connects to a derived column data task that creates derived columns and changes the data type to reflect that of the destination. The derived columns is then connected to the SQL Server destinationation table that matches the excel header columns to the destination table columns.

What should I do with the connection string that I mentioned in my first post? I have provided it here for you or anyone else to review.

"Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" +@.[User::ExcelFile] + ";Extended Properties=\"" + @.[User::ExtProperties] + "\""

Can you or anyone else tell me what I am doing wrong here?

Thanks!!

Lee

|||

Can you actually import at least one single file? forget about the foreach loop and the expression in the connection manager.

I just did a search on 'Could not find installable ISAM ' and found this:

http://support.microsoft.com/kb/209805

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=477902&SiteID=1

So, before going deeper, try to connect to a single execel file.

BTW, I just found a test package I created long time ago, and I see some differences with your approach:

I have only one variable in my for each loop container to hold the file name; and since I configured the loop container to retrive 'Fully Qualified" file name; the variable contains the path and the file name. In the excel connection manager I applied an expression to the ExcelFilePath property (not to the Connection String). The expression is just: @.{User::VarFileName] ; which is the variable I use in the loop container. I don't mess with the extended properties.sql

Monday, March 26, 2012

recbase.cpp:1378 & somerge.c:1616 Errors

Hi,
I am trying to implement a DTS to copy data from one server to another
(both servers are identical), Windows 2000 server and have installed
SQL Server 2000 sp3a.
The DTS in question has the two server connections defined as
"Microsoft OLE DB Provider for SQL Server" and there are several
"Transform Data Tasks" that copy data from tables on one server to
tables on the other. Unfortunately I have to run these steps often as
I am in the process of developing/debugging and I am experiencing one
of the following errors, always when the DTS arrives at the task of
copying the same large table:
Location somerge.c:1616
Expression: mrP->mrStatus!=MERGERUN::NONE
SPID: 78
Process ID: 724
Location recbase.cpp:1378
Expression: m_offBeginVar < m_sizeRec
SPID: 64
Process ID: 840
These errors do not always occur but either one or the other pops up
on a regular basis.
I have run DBCC checkDB and DBCC checktable on the affected Databases
and tables several times and have never found any errors.
Has anyone got any idea of what is causing this? Any suggestions of
what I can do to solve this?
Any help is much appreciated.
Regards
Rekkie
Dear ,
While executing this particular process both servers "sa" passwords should be same,Other wise it never work.
Regards
Faheem Latif
Netsol Pvt Ltd

recbase.cpp:1378 & somerge.c:1616 Errors

Hi,
I am trying to implement a DTS to copy data from one server to another
(both servers are identical), Windows 2000 server and have installed
SQL Server 2000 sp3a.
The DTS in question has the two server connections defined as
"Microsoft OLE DB Provider for SQL Server" and there are several
"Transform Data Tasks" that copy data from tables on one server to
tables on the other. Unfortunately I have to run these steps often as
I am in the process of developing/debugging and I am experiencing one
of the following errors, always when the DTS arrives at the task of
copying the same large table:
Location somerge.c:1616
Expression: mrP->mrStatus!=MERGERUN::NONE
SPID: 78
Process ID: 724
Location recbase.cpp:1378
Expression: m_offBeginVar < m_sizeRec
SPID: 64
Process ID: 840
These errors do not always occur but either one or the other pops up
on a regular basis.
I have run DBCC checkDB and DBCC checktable on the affected Databases
and tables several times and have never found any errors.
Has anyone got any idea of what is causing this' Any suggestions of
what I can do to solve this?
Any help is much appreciated.
Regards
RekkieDear ,
While executing this particular process both servers "sa" passwords should b
e same,Other wise it never work.
Regards
Faheem Latif
Netsol Pvt Ltd|||Both passwords are the same. I don't see however what has
to do with the problem as each OLEDB server connection is
defined separately with the user to use for that
connection.

>--Original Message--
>Dear ,
>While executing this particular process both servers "sa"
passwords should be same,Other wise it never work.
>Regards
>Faheem Latif
>Netsol Pvt Ltd
>.
>

Friday, March 9, 2012

reasons for allocation/consistency errors

What are the reasons for why me may see allocation or consistency errors
when we run DBCC CHECKDB ? Using SQL 2000.
Basically looking for all possible causes
That is kind of a big question, and is probably why no one answers... None
of us have a list of all of the reasons...
In my experience, if you run your DBCC without going to read only or single
user mode, and others are using the system for insert, update, delete during
the dbcc, you will probably get some errors. These are probably due to
changes made by the other users... If you get such an error, rerun dbcc on
the table in question... if the error disappears, or moves to another page,
consider it a transient error and ignore it... If the same error occurs on
the same page, it is a hard error and work to fix it..
Otherwise the most common reasons for DBCC errors is hardware failures.
These can include memory chip failures, disk controllers, and disk drives...
Often re-occuring dbcc errors are the first warning you will get regarding
an impending hardware failure...
Software bugs in the OS and SQL can also cause corruptions, but this occurs
less frequently.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:unQs66aIEHA.2688@.tk2msftngp13.phx.gbl...
> What are the reasons for why me may see allocation or consistency errors
> when we run DBCC CHECKDB ? Using SQL 2000.
> Basically looking for all possible causes
>
>

reasons for allocation/consistency errors

What are the reasons for why me may see allocation or consistency errors
when we run DBCC CHECKDB ? Using SQL 2000.
Basically looking for all possible causesThat is kind of a big question, and is probably why no one answers... None
of us have a list of all of the reasons...
In my experience, if you run your DBCC without going to read only or single
user mode, and others are using the system for insert, update, delete during
the dbcc, you will probably get some errors. These are probably due to
changes made by the other users... If you get such an error, rerun dbcc on
the table in question... if the error disappears, or moves to another page,
consider it a transient error and ignore it... If the same error occurs on
the same page, it is a hard error and work to fix it..
Otherwise the most common reasons for DBCC errors is hardware failures.
These can include memory chip failures, disk controllers, and disk drives...
Often re-occuring dbcc errors are the first warning you will get regarding
an impending hardware failure...
Software bugs in the OS and SQL can also cause corruptions, but this occurs
less frequently.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:unQs66aIEHA.2688@.tk2msftngp13.phx.gbl...
> What are the reasons for why me may see allocation or consistency errors
> when we run DBCC CHECKDB ? Using SQL 2000.
> Basically looking for all possible causes
>
>

reasons for allocation/consistency errors

What are the reasons for why me may see allocation or consistency errors
when we run DBCC CHECKDB ? Using SQL 2000.
Basically looking for all possible causesThat is kind of a big question, and is probably why no one answers... None
of us have a list of all of the reasons...
In my experience, if you run your DBCC without going to read only or single
user mode, and others are using the system for insert, update, delete during
the dbcc, you will probably get some errors. These are probably due to
changes made by the other users... If you get such an error, rerun dbcc on
the table in question... if the error disappears, or moves to another page,
consider it a transient error and ignore it... If the same error occurs on
the same page, it is a hard error and work to fix it..
Otherwise the most common reasons for DBCC errors is hardware failures.
These can include memory chip failures, disk controllers, and disk drives...
Often re-occuring dbcc errors are the first warning you will get regarding
an impending hardware failure...
Software bugs in the OS and SQL can also cause corruptions, but this occurs
less frequently.
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:unQs66aIEHA.2688@.tk2msftngp13.phx.gbl...
> What are the reasons for why me may see allocation or consistency errors
> when we run DBCC CHECKDB ? Using SQL 2000.
> Basically looking for all possible causes
>
>