New Guy Question: Which came first ... the chicken or the checkpoint file?

Hello all...here's a question from a newbie ...

I'm attempting to configure my SSIS package to use a checkpoint file. I've checked the docs, and I believe I've set all the package properties for this ... except they are looking for the name of the checkpoint file. I've tried a couple of experiments such as c:\myCheckpoint.txt and c:\myCheckpoint.xml ... just for grins ... to see if SSIS would generate a checkpoint file for me at the start of the package ... no luck:

Message: Checkpoint file "C:\myCheckpoint.xml" failed to open due to error
0x80070002 "The system cannot find the file specified.".

From these runtime errors I've seen, it appears the checkpoint file should be an XML file that is created w/ specific nodes, etc. My question is ... how do I create the checkpoint file in advance so that when the package is executed it will find it and run?

SSIS ... pretty cool stuff!

Thanks!This is controlled by Package.CheckpointUsage property.
You probably have it set to 'Always' which causes package
to require the checkpoint file. You need to set it to 'IfExists' -
then the checkpoint file will be used if it exists.|||Yeah, that's what I figured too. The property options are Always, IfExists and Never. The doc doesn't specify that a file is created for you if you use Always, and on practical experimentation this didn't seem to help. Perhaps there's another property I missed; I did try to follow all the Package property settings that appeared to relate to checkpoints.

Thank you very much for trying!

DB|||The checkpoint is created automatically when the package fails (if it is configured to use checkpoints).

When you set CheckpointUsage=Always, you tell package that it has to start from previously saved checkpoint, i.e. the checkpoint file is expected to exist.

If you don't have checkpoint file yet, set CheckpointUsage=IfExists and run the package. It will run fine, and if it fails the package will create a checkpoint file. Next time when you run this package it will use that checkpoint.|||Thank you very, very much for your help! That makes sense!

Doug|||

Being another newbe, this post has been exceedingly helpful - I ran into the same issue!

Thanks! :-)

New Guy Question: Which came first ... the chicken or the checkpoint file?

Hello all...here's a question from a newbie ...

I'm attempting to configure my SSIS package to use a checkpoint file. I've checked the docs, and I believe I've set all the package properties for this ... except they are looking for the name of the checkpoint file. I've tried a couple of experiments such as c:\myCheckpoint.txt and c:\myCheckpoint.xml ... just for grins ... to see if SSIS would generate a checkpoint file for me at the start of the package ... no luck:

Message: Checkpoint file "C:\myCheckpoint.xml" failed to open due to error
0x80070002 "The system cannot find the file specified.".

From these runtime errors I've seen, it appears the checkpoint file should be an XML file that is created w/ specific nodes, etc. My question is ... how do I create the checkpoint file in advance so that when the package is executed it will find it and run?

SSIS ... pretty cool stuff!

Thanks!This is controlled by Package.CheckpointUsage property.
You probably have it set to 'Always' which causes package
to require the checkpoint file. You need to set it to 'IfExists' -
then the checkpoint file will be used if it exists.|||Yeah, that's what I figured too. The property options are Always, IfExists and Never. The doc doesn't specify that a file is created for you if you use Always, and on practical experimentation this didn't seem to help. Perhaps there's another property I missed; I did try to follow all the Package property settings that appeared to relate to checkpoints.

Thank you very much for trying!

DB|||The checkpoint is created automatically when the package fails (if it is configured to use checkpoints).

When you set CheckpointUsage=Always, you tell package that it has to start from previously saved checkpoint, i.e. the checkpoint file is expected to exist.

If you don't have checkpoint file yet, set CheckpointUsage=IfExists and run the package. It will run fine, and if it fails the package will create a checkpoint file. Next time when you run this package it will use that checkpoint.|||Thank you very, very much for your help! That makes sense!

Doug|||

Being another newbe, this post has been exceedingly helpful - I ran into the same issue!

Thanks! :-)

New fresh 2005 cluster and SCC error

I am trying to setup an active/passive cluster (everything on 32bit
plateforme) on a virtualized environment. I followed several docs provided by
microsoft especially the one on /prodtechnol/virtualserver/deploy/cvs2005.mpx.
Regarding the w2k3 itself it seems everything is correct, I did all
necesary tests for testing the failover from one node to another and
evrything works correctly.
When I launch SQL 2005 setup on node1 (node 2 of course is on), Setup stops
indicating that some requirements are not met, an SCC Error.
I have an AMD Athlon 64 proc 3000 2.00GHz with and each VM was granted 512 G
of Ram.
I understand that min req is 600Htz for Procs and 512. When I open the
summary.txt file I have the following :
********************************************
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition
Service Pack 1 (Build 3790)
Time : Sat Mar 31 15:55:30 2007
SQLCLUST11 : The current system does not meet minimum hardware requirements
for this SQL Server release. For detailed hardware requirements, see the
readme file or SQL Server Books Online.
SQLCLUST11 : There was an unexpected failure during the setup wizard. You
may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Sat Mar 31 15:55:59 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core(L ocal).log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Datast ore.xml
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core.l og
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows
Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows Installer
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Suppor t.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_SCC.lo g
************************************************** ***
In fact I remember that I had an alert (! inside Yellow triangle) in the
final step of adding the second node. So the alert indicated the following :
**************************
Reanalyzing cluster
sqlclust12: c omparing cluster and node configurations...
sqlclust12: Collecting managed resources...
Triangle yellow : Status 0x00138f: The cluster resource could not be found
*****************************
As said, the cluster works like a charm (several failover tests)
Thank you for your help
"SalamElias" wrote:

> I am trying to setup an active/passive cluster (everything on 32bit
> plateforme) on a virtualized environment. I followed several docs provided by
> microsoft especially the one on /prodtechnol/virtualserver/deploy/cvs2005.mpx.
> Regarding the w2k3 itself it seems everything is correct, I did all
> necesary tests for testing the failover from one node to another and
> evrything works correctly.
> When I launch SQL 2005 setup on node1 (node 2 of course is on), Setup stops
> indicating that some requirements are not met, an SCC Error.
> I have an AMD Athlon 64 proc 3000 2.00GHz with and each VM was granted 512 G
> of Ram.
> I understand that min req is 600Htz for Procs and 512. When I open the
> summary.txt file I have the following :
> ********************************************
> Microsoft SQL Server 2005 9.00.1399.06
> ==============================
> OS Version : Microsoft Windows Server 2003 family, Enterprise Edition
> Service Pack 1 (Build 3790)
> Time : Sat Mar 31 15:55:30 2007
> SQLCLUST11 : The current system does not meet minimum hardware requirements
> for this SQL Server release. For detailed hardware requirements, see the
> readme file or SQL Server Books Online.
> SQLCLUST11 : There was an unexpected failure during the setup wizard. You
> may review the setup logs and/or click the help button for more information.
>
> SQL Server Setup failed. For more information, review the Setup log file in
> %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
>
> Time : Sat Mar 31 15:55:59 2007
>
> List of log files:
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core(L ocal).log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Datast ore.xml
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core.l og
> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0 LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows
> Installer.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows Installer
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Suppor t.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_SCC.lo g
> ************************************************** ***