Deserialization failed error. Trying to automate an RDL file.

Whenever I try to change the SQL query on the RDL (which is an XML doc) and save it under a different name (to keep the original) I get the error...
"Deserialization failed: This is an unexpected token. The expected token is 'NAME'. Line 3325 position 28"

I am checking that line number and cannot fine any correlation.

One way to replicate this error is to create a new rdl file querying any number of fields. Save it and try to edit the sql using notepad inside the <CommmandText> section of the XML file. All I am doing is adding a union query so the fields stay the same, but I keep getting that error.

My purpose behind this is to generate rdl files with different sql criteria from an orignal template rdl.

Can any of you gurus figure this out?

No anwers on this yet?|||Still waiting...

Deployment + XML Config file problem

Hello

I am using XML config file to store the values e.g. Server name.... it runs fine with BIDS (Development enviroment)... but when I deploy and run it to test that XML config files values are being read by e.g. giving the wrong server name, it runs fine (may be retrieving some old values). then I come bak and test it again in the development enviroment to test, it fails ( as it supposed to be caz server name is wrong in config file)

can ne one tell me wr is the problem?

ur help and support is appreciated

regards,

Anas

Sorry to bother you but that was the problem with my config file...

it is so pathetic that package running does not show ne error or warning that's y wasted a lot of time.... fortunately i was able to solve the problem b4 I go on my holidays... i big sigh of reliefs...

regards,

Anas

Deploying RS reports with XML datasources?

Hello-

We've been developing RS 2005 reports which consume XML data from several webservices we've written.

Now comes the issue of deployment. Our production server is not our development server. We've been using the development server URL for our connection string when we built our datasets... how does that work when we want to deploy these reports?

I suppose we can edit the RDL of each report and manually change the connection strings to reflect the the production server address. Is there a better practice that we can implement to handle this problem?

Thanks.

Have you tried to use Shared Datasources? This typically eliminates having to store the information in the report.

deploy SQL2000 database to other server

hi,
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!
This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/default...46&Product=sql
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.c om...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!

deploy SQL2000 database to other server

hi,
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546&Product=sql
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.com...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!

deploy SQL2000 database to other server

hi,
I am sorting data from all different sources, xml, access, text..etc
to my own sql2000 server. (computer name is "testingmachine")
atfter I clean up the database, I will give the final database to the
client and install in their server (computer name is "SQLS")
1) what's the best way to move database structure and data over to
their server? there are few different methods, which one is the best
solution in my situation. thank you!
PS. I use *.adp ("access running time" as frontend client interface)
thank you!This KB article should give you a few methods. You can decide which way is
best for your situation:
http://support.microsoft.com/defaul...546&Product=sql
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"Bob Yang" <bobyang3@.hotmail.com> wrote in message
news:35582154.0406301458.2553431b@.posting.google.com...
> hi,
> I am sorting data from all different sources, xml, access, text..etc
> to my own sql2000 server. (computer name is "testingmachine")
> atfter I clean up the database, I will give the final database to the
> client and install in their server (computer name is "SQLS")
> 1) what's the best way to move database structure and data over to
> their server? there are few different methods, which one is the best
> solution in my situation. thank you!
>
> PS. I use *.adp ("access running time" as frontend client interface)
> thank you!

Deploy Problem

I created a package, created an XML Config file, created a deployment utility and then deployed to server.

Changed Connection Managers Data Source and Initial catalog properites during deplyment. Config file in the deployment folder have the right data source and initial catalog properties value.

But when i run the package..I see wrong connection string(still showing dev server name) even though I changed during these properties during deployement and shows it right in configuration file in deployment folder.

From where the package is reading connection properties....very confusing

I will appreciate any help!!!

Amar

Don't use the data source and initial catalog properties. Use the ConnectionString property instead. At least, that's worked good for me.|||

Thanks Phil for you reply.

I have used Data Source and Initial Catalog properites in another pacakge and it worked fine...but not this time;)

|||

I even tried ConnectionString property..but still not working. I am missing something here

|||Are you sure that when you deploy the SSIS package can find the *correct* config file? It's not grabbing values from a duplicate config file sitting somewhere, is it?|||

SSIS package should use config file in deployment folder...i dont think SSIS is doing that. I cannot find any other config file.

Anything else i should check.

|||

When you right-click on the background of the control flow, do you have the XML Configuration file listed under "Package Configurations"? If yes, what directory does it point to?

Are you receiving any errors when you open up the package on the second server?

|||

Yes XML configuration file is listed under Package configurations. I am not specifying any directory path..just providing name of the config file..so that the config file is placed in deployment folder.

No..I am not getting any error on the second server.Just the connection string is wrong.

|||

Amar Khaira wrote:

Yes XML configuration file is listed under Package configurations. I am not specifying any directory path..just providing name of the config file..so that the config file is placed in deployment folder.

No..I am not getting any error on the second server.Just the connection string is wrong.

Here's the deal. I believe you *need* to specify a path. Here's why. When I opened up and saved a new XML configuration file without a full path, my config file got stored in: C:\Program Files\Microsoft Visual Studio 8\Common7\IDE.

Then I deployed the package, and opened the package from the deployment folder (C:\Documents and Settings\Phil Brammer\My Documents\Visual Studio 2005\Projects\Test01\Test01\bin\Deployment), and the values were picked up from the IDE folder, not the deployment folder.

Check into that and use absolute paths, where possible.|||I can confirm Phil's answer, we ran into a similar problem recently. To use XML config files without the full path, you have to make sure the current working directory is the same as the directory to package is located in. If you are running DTEXEC directly, you could use a batch file to change the directory (CD) before calling DTEXEC. If you are running it from SQL Agent, the only work-around we found was to have Agent call a batch file to run DTEXEC instead of running it directly.|||

I specified path while creating XML config file...but it still does not work after deployment.I am deploying the package in File System.

But here is what i noticed. When I open package from deployment folder by clicking C:\Program Files\Microsoft SQL Server\90\DTS\Packages\Some_FolderName\Package_Name.dtsx it shows right connection properties.

But I try to run the package from IS by right clicking the package->Connection Manager it shows wrong server name.

I am doing something terribly wrong. Please HELP!!

Amar

|||Unless you have the full SSIS client installed, when you right-click and execute a package, it is using your local machine's properties, not the remote machine's.|||I have full SSIS Client Installed.