Puzzled by Config files

I created a package, created an XML Config file, created a deployment utility and then deployed to server. I scheduled it with agent and I get this error (changed the package name in the error to IMPORT to make it more readable):

Description: The configuration file name "C:\Documents and Settings\chris\My Documents\Visual Studio 2005\Projects\IMPORT\IMPORT\IMPORT.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2006-07-12 13:11:39.96 Code: 0x80012059 Source: IMPORT Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Progress: 2006-07-12 13:11:40.56 Source: Import Data Validating: 0% complete End Progress Progress: 2006-07-12 13:11:40.56 Source:... Process Exit Code 1. The step failed.

So basically its trying to point to a config file on my dev workstation. When I created the deploy utility it created a config file in the Deployment directory with the Manifest and the package. I installed from the deployment directory. When installing it asked where I wanted to install and I left it the default of "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\IMPORT" and if I look in that folder the IMPORT.dtsconfig is there.

Ideas of where I went wrong? I want to make sure I understand the whole configuration file notion correctly as I am starting to roll a bunch of packages with config files out to production. I've done the tutorial and thought it was straightforward and made sense. I can fix it by editing the xml of the package and removing the line pointing to my dev box - just want to know what I am doing wrong :)

Nevermind... Found lots of other people with similar issues in diff threads on this forum. This whole config file thing is pretty confusing. When you do the install from the deployment folder it will show all the values from the config file in the deployment directory - but it doesn't use any of them when you actually run the package.

I am really not sure why they put the dtsconfig file in the deployment folder at all - all that does is confuse things. I had been placing the production config file over the one in the deployment folder and assumed it would use it... not so.

Push Binaries after installation SQL Server 2000 virtual server

I forget to set Client Network Utility to Create a Named Pipes Alias for
installation of a named instance of SQL Server 2000 virtual server on a
Windows 2003-based cluster fails to push binaries to the other node. SQL
Server 2000 virtual server installed fine on the present node but was unable
to push the binaries to the other node.
I have corrected the Named Pipes Alias problem. Is there away to push the
binaries to the other node that the cluster we recognize?
Thanks,
Treat it like a failed node. Run the installer to remove then re-add the
node. BOL topic 'Maintaining a Failover Cluster' has details.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Joe K." <JoeK@.discussions.microsoft.com> wrote in message
news:6F653B39-BBAA-4619-AEBA-3B8B6AD87037@.microsoft.com...
> I forget to set Client Network Utility to Create a Named Pipes Alias for
> installation of a named instance of SQL Server 2000 virtual server on a
> Windows 2003-based cluster fails to push binaries to the other node. SQL
> Server 2000 virtual server installed fine on the present node but was
unable
> to push the binaries to the other node.
> I have corrected the Named Pipes Alias problem. Is there away to push the
> binaries to the other node that the cluster we recognize?
> Thanks,
>
|||The need to create the named pipes alias has nothing to do with pushing the
binaries. Without the alias setup cannot connect to SQL Server to run the
necessary scripts. Without the alias I would be suspect that SQL Server
successfully installed on either node. I would run a complet setup again.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Publishing from RS 2000 to RS 2005

I want to publishing many reports from RS 2000 to RS 2005. These reports have
several server parameters. In order to do it I have used the utility
RSScripter, but this application produces .rss and .cmd files for RS 2000. I
have modified their code to do to function them to publish to RS 2005. Does
exist another version of this utility to do this migration? Does exist
another manner to solve this issue?
Many thanksI prefer to deploy using the report designer. The utility you are speaking
of has a version that supports both 2000 and 2005.
http://www.sqldbatips.com/showarticle.asp?ID=62
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Pasquale" <Pasquale@.discussions.microsoft.com> wrote in message
news:40E876D4-4EE6-4236-A3B3-03EA3960FE3E@.microsoft.com...
>I want to publishing many reports from RS 2000 to RS 2005. These reports
>have
> several server parameters. In order to do it I have used the utility
> RSScripter, but this application produces .rss and .cmd files for RS 2000.
> I
> have modified their code to do to function them to publish to RS 2005.
> Does
> exist another version of this utility to do this migration? Does exist
> another manner to solve this issue?
> Many thanks|||I have tried the version 2.0.0.10 and I have downloaded the next version of
RSScripter. When I launch the cmd files produces for RS 2000 to publish to RS
2005 I have some errors if before I don't modified the scripts. In particular,
I can lost the server parameters of RS 2000 reports. Moreover, there are two
different manners between RS 2000 and RS 2005 to set the data source for a
report. I don't see any option inside RSScripter to produce rdl, rds and cmd
files to RS 2005 but reading RS 2000 reports.
"Bruce L-C [MVP]" wrote:
> I prefer to deploy using the report designer. The utility you are speaking
> of has a version that supports both 2000 and 2005.
> http://www.sqldbatips.com/showarticle.asp?ID=62
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Pasquale" <Pasquale@.discussions.microsoft.com> wrote in message
> news:40E876D4-4EE6-4236-A3B3-03EA3960FE3E@.microsoft.com...
> >I want to publishing many reports from RS 2000 to RS 2005. These reports
> >have
> > several server parameters. In order to do it I have used the utility
> > RSScripter, but this application produces .rss and .cmd files for RS 2000.
> > I
> > have modified their code to do to function them to publish to RS 2005.
> > Does
> > exist another version of this utility to do this migration? Does exist
> > another manner to solve this issue?
> >
> > Many thanks
>
>|||Ahh, it probably works mostly for moving between the same versions.
If you are going between RS 2000 and RS 2005 I suggest you do not do it this
way. Although RS 2005 will run RS 2000 reports I recommend that you convert
your reports to RS 2005 first. I had a few weird little problems that went
away once I did this.
To convert you have to pull up the report in RS2005 report designer, let it
convert and then save. It is a little bit of a pain but the process is
quick. I kept a copy of my RS 2000 version reports around.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Pasquale" <Pasquale@.discussions.microsoft.com> wrote in message
news:6ED58430-5A33-4DC5-B5EE-1C7FB9F1D8D5@.microsoft.com...
>I have tried the version 2.0.0.10 and I have downloaded the next version of
> RSScripter. When I launch the cmd files produces for RS 2000 to publish to
> RS
> 2005 I have some errors if before I don't modified the scripts. In
> particular,
> I can lost the server parameters of RS 2000 reports. Moreover, there are
> two
> different manners between RS 2000 and RS 2005 to set the data source for a
> report. I don't see any option inside RSScripter to produce rdl, rds and
> cmd
> files to RS 2005 but reading RS 2000 reports.
>
> "Bruce L-C [MVP]" wrote:
>> I prefer to deploy using the report designer. The utility you are
>> speaking
>> of has a version that supports both 2000 and 2005.
>> http://www.sqldbatips.com/showarticle.asp?ID=62
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Pasquale" <Pasquale@.discussions.microsoft.com> wrote in message
>> news:40E876D4-4EE6-4236-A3B3-03EA3960FE3E@.microsoft.com...
>> >I want to publishing many reports from RS 2000 to RS 2005. These reports
>> >have
>> > several server parameters. In order to do it I have used the utility
>> > RSScripter, but this application produces .rss and .cmd files for RS
>> > 2000.
>> > I
>> > have modified their code to do to function them to publish to RS 2005.
>> > Does
>> > exist another version of this utility to do this migration? Does exist
>> > another manner to solve this issue?
>> >
>> > Many thanks
>>

PSSDiag Utility Questions

Would anyone can told me following about PSSDiag ?

1. The Performance Monitor output is default set to output as .BLG file, would it be other format like CSV or TXT ?

2. For SQL Trace log gathering location, even those we set to drive other than C:\ , it still need some spaces for temporary storage in C:\ under setting of TEMP and TMP path, so is PSSDIAG still need temporary spaces in dirve C:\

3. Does this utility also support monitor on SQL 2005 server ? Pls

Many Thanks First.

1. You cannot change the default output for PERFMON.

2. Yes it access the TEMP directory to perform few computations.

3. http://www.microsoft.com/downloads/details.aspx?familyid=5564386A-28C2-4483-8293-76FFF67B9EB3&displaylang=en refers :

System Requirements

Supported Operating Systems: Windows 2000; Windows NT; Windows Server 2003; Windows XP|||

how about if my server cannot install MSXML 4.0 SP2 ? Can I use alternative method that use ini instead of xml configuration file ?

Also, can I find some example of the ini file format somewhere as I can't find any in the web especially those with some calling custom utility function as I want to start the Performance Monitor myself which can stored as csv format?

Many Thanks.

|||

Have you tested the installation of MSXML SP in thsi case?|||

Satya SKJ wrote:

Have you tested the installation of MSXML SP in thsi case?

yes. if using MSXML4.0SP2, I can start the PSSDIAG but my production server not allow me to apply them. If so, need to go through a complex QC cycle. So, only test on testing server but cannot apply them into Production Server.

|||

Then I believe we are out of option, either you can open a case with Microsoft Support to have desired facility or follow whatever is available.

PSSDiag Utility Questions

Would anyone can told me following about PSSDiag ?

1. The Performance Monitor output is default set to output as .BLG file, would it be other format like CSV or TXT ?

2. For SQL Trace log gathering location, even those we set to drive other than C:\ , it still need some spaces for temporary storage in C:\ under setting of TEMP and TMP path, so is PSSDIAG still need temporary spaces in dirve C:\

3. Does this utility also support monitor on SQL 2005 server ? Pls

Many Thanks First.

1. You cannot change the default output for PERFMON.

2. Yes it access the TEMP directory to perform few computations.

3. http://www.microsoft.com/downloads/details.aspx?familyid=5564386A-28C2-4483-8293-76FFF67B9EB3&displaylang=en refers :

System Requirements

Supported Operating Systems: Windows 2000; Windows NT; Windows Server 2003; Windows XP|||

how about if my server cannot install MSXML 4.0 SP2 ? Can I use alternative method that use ini instead of xml configuration file ?

Also, can I find some example of the ini file format somewhere as I can't find any in the web especially those with some calling custom utility function as I want to start the Performance Monitor myself which can stored as csv format?

Many Thanks.

|||

Have you tested the installation of MSXML SP in thsi case?|||

Satya SKJ wrote:

Have you tested the installation of MSXML SP in thsi case?

yes. if using MSXML4.0SP2, I can start the PSSDIAG but my production server not allow me to apply them. If so, need to go through a complex QC cycle. So, only test on testing server but cannot apply them into Production Server.

|||

Then I believe we are out of option, either you can open a case with Microsoft Support to have desired facility or follow whatever is available.