Deployment options help!

Sorry I am a newbie in SSIS.

I have got a small project that requires to feed in a .CSV flat file and load the data into SQL server 2000.

I developed a SSIS package for this and get it working in my computer, but I need to deploy it to customers that they don't have VS 2005 or SSIS installed. May any one of you give me some clues on that?

I played around with the flat file deployment and again it seems only working on my computer as I have everything installed.

Did you read BOL?

http://msdn2.microsoft.com/en-us/library/ms180167.aspx

http://msdn2.microsoft.com/en-us/library/ms137900.aspx

or the SSIS management whitepaper?

http://www.microsoft.com/technet/prodtechnol/sql/2005/mgngssis.mspx

or other sources?

http://www.databasejournal.com/features/mssql/article.php/3600201

http://blogs.conchango.com/jamiethomson/archive/2006/01/23/2702.aspx

http://blogs.conchango.com/jamiethomson/archive/2006/02/20/2902.aspx

I found these by typing "SSIS deployment" into Google. The help is there if you go and look for it.

-Jamie

deployment of applications

Hi,

I have developed several PPC apps in VS2003, which i have deployed to other PPCs using sqlce.wce4.armv4.CAB for the database runtime.

Now I developed a new app. version in Visual Studio 2005, using the free SQL server express database that came with it.

I can create a .cab file for the app using a setup project, but it eludes me what to install on the PPC of the customer, database wise.

Is there some kind of installable runtime for sql server express ?

(Or what is it called today ?)

thx in advance,

Paul.

Hi Paul,

SQL Express edition is only available for desktop and server versions of Windows, not for Windows Mobile. You must use SQL CE version 3.1 cab files, ie: sqlce30.ppc.wce4.armv4.CAB and sqlce30.repl.ppc.wce4.armv4.CAB (for Windows Mobile 2003 devices)

Deployment issue - users cannot view reports

Hi All,
I am having some difficulty allowing users to view reports. I have
developed a series of reports on RS and deployed them to Report Manager.
However It is only myself that can view the reports on report mnanager -
whenever anyone else tries to log on and view them they get a blank page -
what am i doing wrong?
Thanks and HAPPY XMAS!!
GregGreg wrote:
> Hi All,
> I am having some difficulty allowing users to view reports. I have
> developed a series of reports on RS and deployed them to Report
> Manager. However It is only myself that can view the reports on
> report mnanager - whenever anyone else tries to log on and view them
> they get a blank page - what am i doing wrong?
>
> Thanks and HAPPY XMAS!!
> Greg
It may sound like a stupid question but ... have you checked their
permissions!
If they can see the Report Manager, but not see any reports, then the
security on the reports is too tight.
As administrator you will be able to click on properties and security
of the various folders and reports and add the appropriate users or
groups.
After that you will need to make sure the Datasources have suitable
logon credentials set too.
Regards (and merry christmas!)
Chris|||Hi chris - thanks for the pointer - ill check it out and get back!
"Chris McGuigan" wrote:
> Greg wrote:
> > Hi All,
> >
> > I am having some difficulty allowing users to view reports. I have
> > developed a series of reports on RS and deployed them to Report
> > Manager. However It is only myself that can view the reports on
> > report mnanager - whenever anyone else tries to log on and view them
> > they get a blank page - what am i doing wrong?
> >
> >
> > Thanks and HAPPY XMAS!!
> >
> > Greg
> It may sound like a stupid question but ... have you checked their
> permissions!
> If they can see the Report Manager, but not see any reports, then the
> security on the reports is too tight.
> As administrator you will be able to click on properties and security
> of the various folders and reports and add the appropriate users or
> groups.
> After that you will need to make sure the Datasources have suitable
> logon credentials set too.
> Regards (and merry christmas!)
> Chris
>|||I have what may be a similar issue. All users on our local intreanet can
view the reports, but people from the outside cannot. They can browse to
the page, and see the list of reports, but when they try to view a report,
they get "The Page cannot be Displayed".
Could this be the same as Greg's problem?
Thanks,
Daniel Williams
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:48094DE4-52C0-4522-A822-352BADD676E4@.microsoft.com...
> Hi All,
> I am having some difficulty allowing users to view reports. I have
> developed a series of reports on RS and deployed them to Report Manager.
> However It is only myself that can view the reports on report mnanager -
> whenever anyone else tries to log on and view them they get a blank page -
> what am i doing wrong?
>
> Thanks and HAPPY XMAS!!
> Greg
>|||This is different. In the current version, Report Manager uses a frame to
access the reports. You probably need to set the ReportServerExternalURL
property. See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
"Daniel Williams" <daniel@.aniworld.com> wrote in message
news:eabjGuP7EHA.2568@.TK2MSFTNGP10.phx.gbl...
> I have what may be a similar issue. All users on our local intreanet can
> view the reports, but people from the outside cannot. They can browse to
> the page, and see the list of reports, but when they try to view a report,
> they get "The Page cannot be Displayed".
> Could this be the same as Greg's problem?
> Thanks,
> Daniel Williams
> "Greg" <Greg@.discussions.microsoft.com> wrote in message
> news:48094DE4-52C0-4522-A822-352BADD676E4@.microsoft.com...
>> Hi All,
>> I am having some difficulty allowing users to view reports. I have
>> developed a series of reports on RS and deployed them to Report Manager.
>> However It is only myself that can view the reports on report mnanager -
>> whenever anyone else tries to log on and view them they get a blank
>> page -
>> what am i doing wrong?
>>
>> Thanks and HAPPY XMAS!!
>> Greg
>|||Hi Daniel
Yes i think Brian is right - What Chris said helped me out - I had not
previously defined the permissions for my user group. Think yours may be a
separate issue.
Thanks Chris!
Greg
"Brian Welcker [MS]" wrote:
> This is different. In the current version, Report Manager uses a frame to
> access the reports. You probably need to set the ReportServerExternalURL
> property. See
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Daniel Williams" <daniel@.aniworld.com> wrote in message
> news:eabjGuP7EHA.2568@.TK2MSFTNGP10.phx.gbl...
> >
> > I have what may be a similar issue. All users on our local intreanet can
> > view the reports, but people from the outside cannot. They can browse to
> > the page, and see the list of reports, but when they try to view a report,
> > they get "The Page cannot be Displayed".
> >
> > Could this be the same as Greg's problem?
> >
> > Thanks,
> > Daniel Williams
> >
> > "Greg" <Greg@.discussions.microsoft.com> wrote in message
> > news:48094DE4-52C0-4522-A822-352BADD676E4@.microsoft.com...
> >> Hi All,
> >>
> >> I am having some difficulty allowing users to view reports. I have
> >> developed a series of reports on RS and deployed them to Report Manager.
> >> However It is only myself that can view the reports on report mnanager -
> >> whenever anyone else tries to log on and view them they get a blank
> >> page -
> >> what am i doing wrong?
> >>
> >>
> >> Thanks and HAPPY XMAS!!
> >>
> >> Greg
> >>
> >
> >
>
>|||You're right. Our problem was that we did not have a
<ReportServerExternalURL> value, so it was trying to use the internal
address when rendering the report. Completely different issue.
Cheers,
Daniel Williams
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:70AA6573-50BB-4D9F-BBE3-13E599B6673F@.microsoft.com...
> Hi Daniel
> Yes i think Brian is right - What Chris said helped me out - I had not
> previously defined the permissions for my user group. Think yours may be
> a
> separate issue.
> Thanks Chris!
> Greg
> "Brian Welcker [MS]" wrote:
>> This is different. In the current version, Report Manager uses a frame to
>> access the reports. You probably need to set the ReportServerExternalURL
>> property. See
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsadmin/htm/drp_deploying_v1_0h9e.asp.
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Daniel Williams" <daniel@.aniworld.com> wrote in message
>> news:eabjGuP7EHA.2568@.TK2MSFTNGP10.phx.gbl...
>> >
>> > I have what may be a similar issue. All users on our local intreanet
>> > can
>> > view the reports, but people from the outside cannot. They can browse
>> > to
>> > the page, and see the list of reports, but when they try to view a
>> > report,
>> > they get "The Page cannot be Displayed".
>> >
>> > Could this be the same as Greg's problem?
>> >
>> > Thanks,
>> > Daniel Williams
>> >
>> > "Greg" <Greg@.discussions.microsoft.com> wrote in message
>> > news:48094DE4-52C0-4522-A822-352BADD676E4@.microsoft.com...
>> >> Hi All,
>> >>
>> >> I am having some difficulty allowing users to view reports. I have
>> >> developed a series of reports on RS and deployed them to Report
>> >> Manager.
>> >> However It is only myself that can view the reports on report
>> >> mnanager -
>> >> whenever anyone else tries to log on and view them they get a blank
>> >> page -
>> >> what am i doing wrong?
>> >>
>> >>
>> >> Thanks and HAPPY XMAS!!
>> >>
>> >> Greg
>> >>
>> >
>> >
>>sql

Deploying with sql server express

I have developed a windows mobile 5.0 application that is currently syncing with sql server 2005. I want to deploy the application with sql server express for the client. What do I need to do to make this work?

Thank you.

It depends on how you're syncing. If you're using manual implementation via SQL Client on device, that would work with properly configured SQL 2005 Express as well.

If you using SQL Mobile RDA or replication, you would have to implement manual sync using SQL Client as Express offers no RDA/Replication support.

|||I am using replication. Can you direct me to some reference material that can assist me in changing to manual sync?|||Also, to test with sql server express will I need to install it on my computer? I am running sql 2005 and visual studio 2005. Can I load express in addition to what I have installed. I do not want to un-install anything that I have currently. What is your suggestion?|||

I'm not aware of any reference materials on that. The idea is very simple - you go through all records in one db and compare them with records in another db. If they are different, you'd need to synchronize them as appropriate in your particular case. For example:

Before:

SQL Mobile SQL Express Action

1-foo 1-foo Same data, do nothing

2-bar 2-foobar Data changed, copy from Express to Mobile

2-some <nothing> Record deleted, delete from Mobile

(or is it added on device? - that's for you to track)

Before:

SQL Mobile SQL Express

1-foo 1-foo

2-foobar 2-foobar

As far as I know you can run SQL Express and SQL Server side by side, though you would need to use nonstandard port.

|||

some honest, non-politically correct advice - I wouldn't install SQL Server 2005 and SQL Express on the same machine. it can cause you a lot of difficult issues - I'm not saying it can't be made to work, but you're asking for a day of searching newsgroups to resolve the issues that this introduces. either remove SQL Server and re-run the VS2005 setup, choosing SQL Express as an optional install component, or use a separate box to run SQL Express on.

-Darren

Deploying SQL Server packaged application

I developed an application using C# and SQL Server 2005. I want to
know how to package such an application so that users can download it
from my site, install it and start using it. Previously I have done
this with my VB/MS Access applications. There was no further
requirements as only blank MDB file need to be included. But I don't
know how to package an app. with SQL Server. How to configure the
setup so that on installing SQL Server along with the blank data files
are automatically installed on user's computer.It depends on variuos factors.
1. SQL Server 2005.
If your app uses SQL Server 2005 Sd or up, you probably do not distribute
SQL Server2005 itself. However, if you use SQL Server Express, you may wan
to include both SQL Server Express and the database. If you do want to
include SQL Server Express, your app being server app (such as web app) or
desktop app may make different. For desktop app, do you want to install SQL
Server Express on all user computers (so the data is not shared), or you
only need one SQL Server on the LAN and all users of youe desktop app share
the data (thus, only install one instance of SQL Server somewhere on the
LAN). You can search the net on the topic on packaging SQL Server Express
into installation package. It may not as complicated as imaging, but I never
did it and personally, I'd rather seperate the installation of SQL Server
Express from my application.
2. Database itsellf.
You can use script to create all SQL Server objects (database, views, SPs,
user logins...) during installation;
But simply including clean database file (*.mdf/*.ldf) into the package and
attach it to a ready SQL Server durinig installation would be easier.
However, after attaching database file, you may still need to run some
scripts to perform some user specific tasks, such as set/change SQL Server
login, database user...
"RP" <rpk.general@.gmail.com> wrote in message
news:1192532194.579961.226780@.e34g2000pro.googlegroups.com...
>I developed an application using C# and SQL Server 2005. I want to
> know how to package such an application so that users can download it
> from my site, install it and start using it. Previously I have done
> this with my VB/MS Access applications. There was no further
> requirements as only blank MDB file need to be included. But I don't
> know how to package an app. with SQL Server. How to configure the
> setup so that on installing SQL Server along with the blank data files
> are automatically installed on user's computer.
>

Deploying SQL Express with ASP.Net Application

I have a small ASP.Net application developed in VS 2005 that I would like to deploy with SQL Express.

I have included the MDF file in the Application and added SQL Express as a pre-requisite for the Setup and Deployment project.

It installs SQL Express but when it tries to connect I receive:
"This is not a valid login Cannot open user default database. Login failed. Login failed for user 'NT AUTHORITY\SYSTEM'."

I don't seem to have any options using the "prerequisite options in VS 2005 in terms of command line deployment parameters.

Likewise I would prefer to attach the database to the instance (because I need to write a connection string from a PDA using RDA and I have zero clue how to do RDA directly back to the file).

Thanks for any help!
If you do not impersinate the user within your Asp application, the service account which the ASP Service is running with is used to connect to the SQL Server. If this account is not priviledged to access the server, you will get the mentioned error message. I don′t know how your application design is, but if you want to leave it as it is, you will have to grant access for the SYSTEM account to the server.

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Deploying Reports to a New Server

I developed some reports on one system that I would like to move to another
system. I copied the rdl file to the new system and uploaded it via Report
Manager.
The data source the report uses is based upon SQL views which I created on
the new server.
I'm having a problem with the data source. I've tried creating a new custom
data source by going to the properties of the report and clicking on Data
Sources. I've also tried creating a new data source by clicking New Data
Source from the home page of the Reports.
I've received login errors using the sa account and I've seen that, despite
picking a new data source, it still seems to use the old data source.
What do I need to do to point the report to a the current server's data?
--
Charles Allen, MVPIf both the servers are accessible on your network, just go to report project
properties and change the server to your new server and deploy it, instead of
you doing it does the job perfectly, including datasource..
Amarnath
"Charles Allen" wrote:
> I developed some reports on one system that I would like to move to another
> system. I copied the rdl file to the new system and uploaded it via Report
> Manager.
> The data source the report uses is based upon SQL views which I created on
> the new server.
> I'm having a problem with the data source. I've tried creating a new custom
> data source by going to the properties of the report and clicking on Data
> Sources. I've also tried creating a new data source by clicking New Data
> Source from the home page of the Reports.
> I've received login errors using the sa account and I've seen that, despite
> picking a new data source, it still seems to use the old data source.
> What do I need to do to point the report to a the current server's data?
> --
> Charles Allen, MVP
>|||Thank you for replying quickly.
In this case, the machines are not on the same network. One is a test
environment I use and the other is a client's production system.
--
Charles Allen, MVP
"Amarnath" wrote:
> If both the servers are accessible on your network, just go to report project
> properties and change the server to your new server and deploy it, instead of
> you doing it does the job perfectly, including datasource..
> Amarnath
> "Charles Allen" wrote:
> > I developed some reports on one system that I would like to move to another
> > system. I copied the rdl file to the new system and uploaded it via Report
> > Manager.
> >
> > The data source the report uses is based upon SQL views which I created on
> > the new server.
> >
> > I'm having a problem with the data source. I've tried creating a new custom
> > data source by going to the properties of the report and clicking on Data
> > Sources. I've also tried creating a new data source by clicking New Data
> > Source from the home page of the Reports.
> >
> > I've received login errors using the sa account and I've seen that, despite
> > picking a new data source, it still seems to use the old data source.
> >
> > What do I need to do to point the report to a the current server's data?
> > --
> > Charles Allen, MVP
> >|||ok, MS has provided a sample script on "how to deploy the reports using
command prompt", you can have a look at that sample for your solution.
Amarnath
"Charles Allen" wrote:
> Thank you for replying quickly.
> In this case, the machines are not on the same network. One is a test
> environment I use and the other is a client's production system.
> --
> Charles Allen, MVP
>
> "Amarnath" wrote:
> > If both the servers are accessible on your network, just go to report project
> > properties and change the server to your new server and deploy it, instead of
> > you doing it does the job perfectly, including datasource..
> >
> > Amarnath
> >
> > "Charles Allen" wrote:
> >
> > > I developed some reports on one system that I would like to move to another
> > > system. I copied the rdl file to the new system and uploaded it via Report
> > > Manager.
> > >
> > > The data source the report uses is based upon SQL views which I created on
> > > the new server.
> > >
> > > I'm having a problem with the data source. I've tried creating a new custom
> > > data source by going to the properties of the report and clicking on Data
> > > Sources. I've also tried creating a new data source by clicking New Data
> > > Source from the home page of the Reports.
> > >
> > > I've received login errors using the sa account and I've seen that, despite
> > > picking a new data source, it still seems to use the old data source.
> > >
> > > What do I need to do to point the report to a the current server's data?
> > > --
> > > Charles Allen, MVP
> > >

Deploying MSSQL 2005 Express DB to MSSQL 2005 WKGP Errors

DB is developed on local computer with MSSQL 2005 Express. My host is on MSSQL 2005 workgroup. Are they compatible, because I am getting errors? Is my approach wrong?

I have tried several approaches.

A) I created a backup of database on my local, then placed a copy on the server. Then I tried to restore through Server Management Studio. I get this error.

TITLE: Microsoft SQL Server Management Studio

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

ADDITIONAL INFORMATION:

The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database.

RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3169)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476

BUTTONS:

OK

B: I also have tried copying the database. I put it in the same path as the other databases that can be read with server management studio on the server. Then, tried to get to it through server managements studio and it did not appear. So I tried to attach it. Then I received this error:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'MROACH1'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not find row in sysindexes for database ID 10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.

Could not open new database 'LodgingDB'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=602&LinkId=20476

BUTTONS:

OK

C: I have also tried opening the Database, and back up file through Server Management Studio. without success.

D: I also tried Windows and Software update at microsoft update, but no updates were recommended for Version on Server.

I'm surprised this is so hard. My original data base was created in same family of software. 2005 MS SQL Express. I could use some direct help from someone experienced with this. Am I doing it wrong or are the DB versions incompatible.

Mark Roach

Hi Mark,

The first error you mention would indicate that your hosting company is using SQL 2000 not SQL 2005. Database files are not backward compatible. You should verify with your host what version of SQL Server they have, or if they have both 2000 and 2005, that they are pointing you to a 2005 server.

Mike

|||

Thanks Mike,

The host machine is on MSSQL 2005 WorkGroup.

|||

Actually, you may be incorrect about what is running on the hosting system.

The error message from the restore:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476

indicates (ProdVer=08.00.2039) that it is running SQL 2000, not SQL 2005. Also, the error message talking about versions of databases indicates the same.

All SKUs/editions of SQL databases of the same version are compatible. There are no diffences in database format between Express and Workgroup as long as both are the same version.

|||

Hi there,

I got the same error when I tried to restore the SQL 2005 DB to SQL 2005 DB.

Were you able to figure this one out? If so, could you please let me know?

Thanks in advance,

SG.

Deploying MSSQL 2005 Express DB to MSSQL 2005 WKGP Errors

DB is developed on local computer with MSSQL 2005 Express. My host is on MSSQL 2005 workgroup. Are they compatible, because I am getting errors? Is my approach wrong?

I have tried several approaches.

A) I created a backup of database on my local, then placed a copy on the server. Then I tried to restore through Server Management Studio. I get this error.

TITLE: Microsoft SQL Server Management Studio

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

ADDITIONAL INFORMATION:

The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database.

RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3169)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476

BUTTONS:

OK

B: I also have tried copying the database. I put it in the same path as the other databases that can be read with server management studio on the server. Then, tried to get to it through server managements studio and it did not appear. So I tried to attach it. Then I received this error:

TITLE: Microsoft SQL Server Management Studio

Attach database failed for Server 'MROACH1'. (Microsoft.SqlServer.Smo)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476

ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Could not find row in sysindexes for database ID 10, object ID 1, index ID 1. Run DBCC CHECKTABLE on sysindexes.

Could not open new database 'LodgingDB'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 602)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=602&LinkId=20476

BUTTONS:

OK

C: I have also tried opening the Database, and back up file through Server Management Studio. without success.

D: I also tried Windows and Software update at microsoft update, but no updates were recommended for Version on Server.

I'm surprised this is so hard. My original data base was created in same family of software. 2005 MS SQL Express. I could use some direct help from someone experienced with this. Am I doing it wrong or are the DB versions incompatible.

Mark Roach

Hi Mark,

The first error you mention would indicate that your hosting company is using SQL 2000 not SQL 2005. Database files are not backward compatible. You should verify with your host what version of SQL Server they have, or if they have both 2000 and 2005, that they are pointing you to a 2005 server.

Mike

|||

Thanks Mike,

The host machine is on MSSQL 2005 WorkGroup.

|||

Actually, you may be incorrect about what is running on the hosting system.

The error message from the restore:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2039&EvtSrc=MSSQLServer&EvtID=3169&LinkId=20476

indicates (ProdVer=08.00.2039) that it is running SQL 2000, not SQL 2005. Also, the error message talking about versions of databases indicates the same.

All SKUs/editions of SQL databases of the same version are compatible. There are no diffences in database format between Express and Workgroup as long as both are the same version.

|||

Hi there,

I got the same error when I tried to restore the SQL 2005 DB to SQL 2005 DB.

Were you able to figure this one out? If so, could you please let me know?

Thanks in advance,

SG.

Deploying custom assemblies

Hi All,
I have developed a custom assembly and now I want to deploy it on to
the server as per the instructions mentioned in the books online
(ms-help://MS.RSBOL80.1033/RSPROG/htm/rsp_prog_rdl_8mue.htm), I want
to remove the commented portion of the RSReportServer.config file to
enable custom assemblies permission.However, I find that I dont have
any such commented portion in the file. I am using the Developer
edition of Reporting Services.
Can any one guide me if the file being edited is correct ? Does it
have to do something with the edition of RS that I am using?
Thanks in advance,
Lone CrusaderHi Loner,
Depending on what permission levels your custom assemblies need you'll need
to update your RS policy file and deply that too.
You'll need to add a PermissionSet AND CodeGroup configuration settings
(when using Report Designer, it uses it's own levels of Code Trusting (it
fakes a few things), when you do it by yourself, you'll need to define this
Code Trust (RS "trusting" your custom assembly) yourself
- peteZ
"Lone Crusader" <ravi32ful@.rediffmail.com> wrote in message
news:cc093b66.0409110001.3a1ac8bd@.posting.google.com...
> Hi All,
> I have developed a custom assembly and now I want to deploy it on to
> the server as per the instructions mentioned in the books online
> (ms-help://MS.RSBOL80.1033/RSPROG/htm/rsp_prog_rdl_8mue.htm), I want
> to remove the commented portion of the RSReportServer.config file to
> enable custom assemblies permission.However, I find that I dont have
> any such commented portion in the file. I am using the Developer
> edition of Reporting Services.
> Can any one guide me if the file being edited is correct ? Does it
> have to do something with the edition of RS that I am using?
> Thanks in advance,
> Lone Crusader|||Bryant Likes wrote a nice article on this issue - read it at
http://blogs.sqlxml.org/bryantlikes/articles/824.aspx.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"Lone Crusader" <ravi32ful@.rediffmail.com> wrote in message
news:cc093b66.0409110001.3a1ac8bd@.posting.google.com...
> Hi All,
> I have developed a custom assembly and now I want to deploy it on to
> the server as per the instructions mentioned in the books online
> (ms-help://MS.RSBOL80.1033/RSPROG/htm/rsp_prog_rdl_8mue.htm), I want
> to remove the commented portion of the RSReportServer.config file to
> enable custom assemblies permission.However, I find that I dont have
> any such commented portion in the file. I am using the Developer
> edition of Reporting Services.
> Can any one guide me if the file being edited is correct ? Does it
> have to do something with the edition of RS that I am using?
> Thanks in advance,
> Lone Crusader

Deployed reports have javascript errors?

Hello-

I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.

Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'

I get these errors also when invoking these reports through a form post.

It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.

Thanks.Solution!

The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.

There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.

This is a known issue and MS hasn't yet written a KB article for it.|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||

What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?

This is on a clean install of SQL 2k5 on Server 2k3 SP1.

Thanks.

|||

On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"

Thanks again;)

|||Anyone found a solution for this ?|||

If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.

After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".

<location path="Reserved.ReportViewerWebControl.axd">

<system.web>

<authorization>

<allow roles="RoleA, RoleB">

</allow>

</authorization>

</system.web>

</location>

Deployed reports have javascript errors?

Hello-

I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.

Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'

I get these errors also when invoking these reports through a form post.

It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.

Thanks.
Solution!

The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.

There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.

This is a known issue and MS hasn't yet written a KB article for it.
|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||

What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?

This is on a clean install of SQL 2k5 on Server 2k3 SP1.

Thanks.

|||

On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"

Thanks again;)

|||Anyone found a solution for this ?|||

If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.

After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".

<location path="Reserved.ReportViewerWebControl.axd">

<system.web>

<authorization>

<allow roles="RoleA, RoleB">

</allow>

</authorization>

</system.web>

</location>

Deployed reports have javascript errors?

Hello-

I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.

Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'

I get these errors also when invoking these reports through a form post.

It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.

Thanks.
Solution!

The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.

There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.

This is a known issue and MS hasn't yet written a KB article for it.
|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||

What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?

This is on a clean install of SQL 2k5 on Server 2k3 SP1.

Thanks.

|||

On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"

Thanks again;)

|||Anyone found a solution for this ?|||

If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.

After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".

<location path="Reserved.ReportViewerWebControl.axd">

<system.web>

<authorization>

<allow roles="RoleA, RoleB">

</allow>

</authorization>

</system.web>

</location>

Deployed reports have javascript errors?

Hello-

I have developed a number of reports on Win XP with VS2005. They run on our development server, which is running Windows Server 2003 32-bit. I then deploy these reports on our production server, which is running Windows Server 2003 64-bit edition.

Accessing any of the reports from Report Manager results in javascript errors, such as 'Line 41 Error: 'RSClientController' is undefined'

I get these errors also when invoking these reports through a form post.

It appears that some javascript code generated by the report server is missing. Could this be a 32-bit vs 64-bit issue? Report Manager seems to work fine; it is only when I run a report that I have this problem. This is the first time I've tried to deploy reports to this server.

Thanks.Solution!

The problem is the .axd file extention which is generated by the sql server on the fly when one tries to run a report.

There is an IIS setting that needs to be changed. Open IIS and go to the properties of the Reports website. Under the directory tab, click on the Configuration button. Find the .axd extension in the Mappings tab and double-click to get to its properties. Uncheck the 'Check that file exists' option, save, and that is it.

This is a known issue and MS hasn't yet written a KB article for it.|||Excellent analysis. This solved my problem with reports and the WebResource.axd file.|||

What if I'm having the same "'RSClientController' is undefined" issue, but when I go to the .axd extension properties, "verify that file exists" is already unchecked?

This is on a clean install of SQL 2k5 on Server 2k3 SP1.

Thanks.

|||

On IIS v 6.0, on the Virtual Directory tab of the ReportServer, I chose configuration, then on the mappings tab I needed to edit the Wildcard application to uncheck the box to "verify file exists"

Thanks again;)

|||Anyone found a solution for this ?|||

If you website is using forms authentication, you have to grant access to authenticated users to Reserved.ReportViewerWebControl.axd.

After I added the following location entry in my web.config file I no longer received "RSClient Controller is not defined messages".

<location path="Reserved.ReportViewerWebControl.axd">

<system.web>

<authorization>

<allow roles="RoleA, RoleB">

</allow>

</authorization>

</system.web>

</location>

DEPLOY packages from Server A to Server B.

I developed some SSIS packages in SQL2005.When developing , The connect is set with Server A.

And i know ,later we are supposed to move to SERVER B.but B's IP and machine name are both unknown for developers.

The deployment guys will be cahrge in that.

what's easiest way for me to tell the deployment guy to add a connection to SERVER B after the SSIS packages have been developed?

any suggestion? Thanks in advance.

Use package configurations to store the data that can change (database connection strings, etc...)|||

HI phil:

yes , i tried this way.

In SERVER B ,imported .dtsx file , then changed the connection value with B server in .dtsconfig file, and ran the package, i found the package still affect the A server.

what' s wrong with my steps?

|||Do you have the ConnectionString property in the .dtsconfig file? This is what you should change.|||

Hi Phil:

Please take a look at the following content in my configure file(sorry for too much lines),could u tell me where to modify?:

Thank u very much

<?xml version="1.0"?><DTSConfiguration><DTSConfigurationHeading><DTSConfigurationFileInfo GeneratedBy="ASIAPACIFIC\daij" GeneratedFromPackageName="Package" GeneratedFromPackageID="{B780B7CC-3E98-4F5D-AF9A-E70F262B6FEA}" GeneratedDate="2007-3-4 18:55:47"/></DTSConfigurationHeading><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=SCN4685;User ID=sa;Initial Catalog=DemoDB0;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Description]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[InitialCatalog]" ValueType="String"><ConfiguredValue>DemoDB0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Name]" ValueType="String"><ConfiguredValue>SCN4685.DemoDB0.sa</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Password]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ProtectionLevel]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[RetainSameConnection]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ServerName]" ValueType="String"><ConfiguredValue>SCN4685</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[UserName]" ValueType="String"><ConfiguredValue>sa</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CertificateContext]" ValueType="Int64"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CheckpointFileName]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CheckpointUsage]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CheckSignatureOnLoad]" ValueType="Boolean"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CreationDate]" ValueType="DateTime"><ConfiguredValue>3/4/2007 5:32:13 PM</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CreatorComputerName]" ValueType="String"><ConfiguredValue>SCN4685</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CreatorName]" ValueType="String"><ConfiguredValue>ASIAPACIFIC\daij</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[DelayValidation]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[Description]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[Disable]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[DisableEventHandlers]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[EncryptCheckpoints]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[FailPackageOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[FailParentOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ForcedExecutionValue]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ForceExecutionResult]" ValueType="Int32"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ForceExecutionValue]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[InteractiveMode]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[IsolationLevel]" ValueType="Int32"><ConfiguredValue>1048576</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[LocaleID]" ValueType="Int32"><ConfiguredValue>2052</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[LoggingMode]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[MaxConcurrentExecutables]" ValueType="Int32"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[MaximumErrorCount]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[Name]" ValueType="String"><ConfiguredValue>Package</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[OfflineMode]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[PackagePassword]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[PackagePriorityClass]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[PackageType]" ValueType="Int32"><ConfiguredValue>5</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ProtectionLevel]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[SaveCheckpoints]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[SQLFolder]" ValueType="String"><ConfiguredValue>\</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[SuppressConfigurationWarnings]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[TransactionOption]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[UpdateObjects]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[UpdatePackage]" ValueType="Boolean"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionBuild]" ValueType="Int32"><ConfiguredValue>7</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionComments]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionMajor]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionMinor]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[BypassPrepare]" ValueType="Boolean"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[CodePage]" ValueType="UInt32"><ConfiguredValue>1252</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Connection]" ValueType="String"><ConfiguredValue>SCN4685.DemoDB0.sa</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[DelayValidation]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Description]" ValueType="String"><ConfiguredValue>Execute SQL Task</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Disable]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[DisableEventHandlers]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[FailPackageOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[FailParentOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ForcedExecutionValue]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ForceExecutionResult]" ValueType="Int32"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ForceExecutionValue]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[IsolationLevel]" ValueType="Int32"><ConfiguredValue>1048576</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[IsStoredProcedure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[LocaleID]" ValueType="Int32"><ConfiguredValue>2052</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[LoggingMode]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[MaximumErrorCount]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Name]" ValueType="String"><ConfiguredValue>Execute SQL Task</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ResultSetType]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[SqlStatementSource]" ValueType="String"><ConfiguredValue>usp_insertSSISLOG</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[SqlStatementSourceType]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[TimeOut]" ValueType="UInt32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[TransactionOption]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration></DTSConfiguration>

|||This is the only line you should have in your configuration file for connections: (The ConnectionString property)

<Configuration

ConfiguredType="Property"

Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ConnectionString]"

ValueType="String"><ConfiguredValue>Data Source=SCN4685;User

ID=sa;Initial

Catalog=DemoDB0;</ConfiguredValue></Configuration>

But, this seems to be using an ODBC connection. So, that means the ODBC connection has to change to point to the new database, OR, you have to change the "Data Source=XXXXX" parameter in the above line to point to the different ODBC connection. (Or Oracle connection, whatever it may be.)|||

Anyway，many many thanks

|||

Hahhahhha~~~~

Sometimes it‘s really weird!
2 whole days, I can’t figure out how to change the connection when deploying SSIS to another Server.
Today, I was so disappointed that I haven’t got the right way to work it round.
Before the shift is off, I fall a snap. And after snap, I used the XML spy to modify the configure file with password adding.
Hah~~it works!
I still wonder why the password is blank when we enabled the configure file option.
Here are my tips to change connections when deploying to Pro environment.

No need to change this:
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=SCN4685;User ID=sa;Initial Catalog=DemoDB0;Persist Security Info=True;</ConfiguredValue></Configuration>

But we have to change these property’s value:
InitialCatalog:
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[InitialCatalog]" ValueType="String"><ConfiguredValue>DemoDB1</ConfiguredValue></Configuration>
Password(what is blank at first):
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Password]" ValueType="String"><ConfiguredValue>XXXXXX</ConfiguredValue></Configuration>
Servername:
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ServerName]" ValueType="String"><ConfiguredValue>SCN4685</ConfiguredValue></Configuration>

Gosh~~thanks.
It really works.

DEPLOY packages from Server A to Server B.

I developed some SSIS packages in SQL2005.When developing , The connect is set with Server A.

And i know ,later we are supposed to move to SERVER B.but B's IP and machine name are both unknown for developers.

The deployment guys will be cahrge in that.

what's easiest way for me to tell the deployment guy to add a connection to SERVER B after the SSIS packages have been developed?

any suggestion? Thanks in advance.

Use package configurations to store the data that can change (database connection strings, etc...)|||

HI phil:

yes , i tried this way.

In SERVER B ,imported .dtsx file , then changed the connection value with B server in .dtsconfig file, and ran the package, i found the package still affect the A server.

what' s wrong with my steps?

|||Do you have the ConnectionString property in the .dtsconfig file? This is what you should change.|||

Hi Phil:

Please take a look at the following content in my configure file(sorry for too much lines),could u tell me where to modify?:

Thank u very much

<?xml version="1.0"?><DTSConfiguration><DTSConfigurationHeading><DTSConfigurationFileInfo GeneratedBy="ASIAPACIFIC\daij" GeneratedFromPackageName="Package" GeneratedFromPackageID="{B780B7CC-3E98-4F5D-AF9A-E70F262B6FEA}" GeneratedDate="2007-3-4 18:55:47"/></DTSConfigurationHeading><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=SCN4685;User ID=sa;Initial Catalog=DemoDB0;</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Description]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[InitialCatalog]" ValueType="String"><ConfiguredValue>DemoDB0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Name]" ValueType="String"><ConfiguredValue>SCN4685.DemoDB0.sa</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Password]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ProtectionLevel]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[RetainSameConnection]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ServerName]" ValueType="String"><ConfiguredValue>SCN4685</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[UserName]" ValueType="String"><ConfiguredValue>sa</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CertificateContext]" ValueType="Int64"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CheckpointFileName]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CheckpointUsage]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CheckSignatureOnLoad]" ValueType="Boolean"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CreationDate]" ValueType="DateTime"><ConfiguredValue>3/4/2007 5:32:13 PM</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CreatorComputerName]" ValueType="String"><ConfiguredValue>SCN4685</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[CreatorName]" ValueType="String"><ConfiguredValue>ASIAPACIFIC\daij</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[DelayValidation]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[Description]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[Disable]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[DisableEventHandlers]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[EncryptCheckpoints]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[FailPackageOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[FailParentOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ForcedExecutionValue]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ForceExecutionResult]" ValueType="Int32"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ForceExecutionValue]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[InteractiveMode]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[IsolationLevel]" ValueType="Int32"><ConfiguredValue>1048576</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[LocaleID]" ValueType="Int32"><ConfiguredValue>2052</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[LoggingMode]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[MaxConcurrentExecutables]" ValueType="Int32"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[MaximumErrorCount]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[Name]" ValueType="String"><ConfiguredValue>Package</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[OfflineMode]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[PackagePassword]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[PackagePriorityClass]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[PackageType]" ValueType="Int32"><ConfiguredValue>5</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[ProtectionLevel]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[SaveCheckpoints]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[SQLFolder]" ValueType="String"><ConfiguredValue>\</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[SuppressConfigurationWarnings]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[TransactionOption]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[UpdateObjects]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[UpdatePackage]" ValueType="Boolean"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionBuild]" ValueType="Int32"><ConfiguredValue>7</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionComments]" ValueType="String"><ConfiguredValue></ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionMajor]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package.Properties[VersionMinor]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[BypassPrepare]" ValueType="Boolean"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[CodePage]" ValueType="UInt32"><ConfiguredValue>1252</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Connection]" ValueType="String"><ConfiguredValue>SCN4685.DemoDB0.sa</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[DelayValidation]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Description]" ValueType="String"><ConfiguredValue>Execute SQL Task</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Disable]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[DisableEventHandlers]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[FailPackageOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[FailParentOnFailure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ForcedExecutionValue]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ForceExecutionResult]" ValueType="Int32"><ConfiguredValue>-1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ForceExecutionValue]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[IsolationLevel]" ValueType="Int32"><ConfiguredValue>1048576</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[IsStoredProcedure]" ValueType="Boolean"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[LocaleID]" ValueType="Int32"><ConfiguredValue>2052</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[LoggingMode]" ValueType="Int32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[MaximumErrorCount]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[Name]" ValueType="String"><ConfiguredValue>Execute SQL Task</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[ResultSetType]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[SqlStatementSource]" ValueType="String"><ConfiguredValue>usp_insertSSISLOG</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[SqlStatementSourceType]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[TimeOut]" ValueType="UInt32"><ConfiguredValue>0</ConfiguredValue></Configuration><Configuration ConfiguredType="Property" Path="\Package\Execute SQL Task.Properties[TransactionOption]" ValueType="Int32"><ConfiguredValue>1</ConfiguredValue></Configuration></DTSConfiguration>

|||This is the only line you should have in your configuration file for connections: (The ConnectionString property)

<Configuration

ConfiguredType="Property"

Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ConnectionString]"

ValueType="String"><ConfiguredValue>Data Source=SCN4685;User

ID=sa;Initial

Catalog=DemoDB0;</ConfiguredValue></Configuration>

But, this seems to be using an ODBC connection. So, that means the ODBC connection has to change to point to the new database, OR, you have to change the "Data Source=XXXXX" parameter in the above line to point to the different ODBC connection. (Or Oracle connection, whatever it may be.)|||

Anyway，many many thanks

|||

Hahhahhha~~~~

Sometimes it‘s really weird!
2 whole days, I can’t figure out how to change the connection when deploying SSIS to another Server.
Today, I was so disappointed that I haven’t got the right way to work it round.
Before the shift is off, I fall a snap. And after snap, I used the XML spy to modify the configure file with password adding.
Hah~~it works!
I still wonder why the password is blank when we enabled the configure file option.
Here are my tips to change connections when deploying to Pro environment.

No need to change this:
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ConnectionString]" ValueType="String"><ConfiguredValue>Data Source=SCN4685;User ID=sa;Initial Catalog=DemoDB0;Persist Security Info=True;</ConfiguredValue></Configuration>

But we have to change these property’s value:
InitialCatalog:
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[InitialCatalog]" ValueType="String"><ConfiguredValue>DemoDB1</ConfiguredValue></Configuration>
Password(what is blank at first):
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[Password]" ValueType="String"><ConfiguredValue>XXXXXX</ConfiguredValue></Configuration>
Servername:
<Configuration ConfiguredType="Property" Path="\Package.Connections[SCN4685.DemoDB0.sa].Properties[ServerName]" ValueType="String"><ConfiguredValue>SCN4685</ConfiguredValue></Configuration>

Gosh~~thanks.
It really works.

deploy MS Reporting services to IIS on my own pc

How do I deploy a report developed in MS Reporting Services to an IIS
on my own pc?
FrancoOn 14 Oct 2005 10:13:45 -0700, francowell@.gmail.com wrote:
>How do I deploy a report developed in MS Reporting Services to an IIS
>on my own pc?
>Franco
You can't - at least not if you only have IIS on the machine.
You can deploy to a server running Reporting Services, which also
require IIS.
Or, if you are using Reporting Services 2005, you can also use the new
ReportViewer controls which don't require Reporting Services on a
server but have more limited functionality.
Andrew Watt
MVP - InfoPath|||My PC also has SQL 2000 and VS Studio.net 2003 installed on it. Do I
have what is needeed to deploy a report on this pc?
Franco|||On 14 Oct 2005 11:30:12 -0700, francowell@.gmail.com wrote:
>My PC also has SQL 2000 and VS Studio.net 2003 installed on it. Do I
>have what is needeed to deploy a report on this pc?
>Franco
If you have SQL Server 2000 then, assuming you obtained Reporting
Services 2000, you can deploy on the machine.
If you have SQL Server 2000 Developer Edition you can test deployment
but you are not licensed, as I understand it, to deploy for production
use.
Andrew Watt
MVP - InfoPath|||This is only for testing the reports that I am developing. How do I go
about deploying the report?
Franco|||On 14 Oct 2005 12:26:11 -0700, francowell@.gmail.com wrote:
>This is only for testing the reports that I am developing. How do I go
>about deploying the report?
>Franco
Franco,
In VS2003, open Solution Explorer, right click on the Solution name,
select Deploy Solution.
Likely it will deploy to the correct location by default if you are
deploying locally.
Try accessing the report by going to http://localhost/reports/ in
Internet Explorer.
Andrew Watt
MVP - InfoPath|||Andrew
Your suggestion is not working, but thank you anyway. I appreciate
your help.
Have a great weekend....Franco|||Hi Franco,
There are lots of possibilities for it not working.
If you describe which aspect isn't working and what error message(s)
you get, then I can suggest how you can maybe fix it.
Andrew Watt
MVP - InfoPath
On 14 Oct 2005 13:16:16 -0700, francowell@.gmail.com wrote:
>Andrew
>Your suggestion is not working, but thank you anyway. I appreciate
>your help.
>Have a great weekend....Franco|||Franco, Have you ever installed Reporting Services Server. I assume since
you have created a report you installed the tools. Did you ever install
Reporting Services. Can you go to the website and see Report Manager?
You need to make sure it is installed and working properly before trying to
deploy.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<francowell@.gmail.com> wrote in message
news:1129320976.701766.251640@.g44g2000cwa.googlegroups.com...
> Andrew
> Your suggestion is not working, but thank you anyway. I appreciate
> your help.
> Have a great weekend....Franco
>

Deploy C# Express app with SQL Server express DB

Hello Everyone,

I have developed an application in Visual C# Express Edition, that uses a SQL Server Express database. I am deploying it using ClickOnce, and I'm wondering if there are any settings I have to change to SQL Server express, in order for my application to be able to access the database, since I'm getting an error when I start the application. I consider myself a beginner developer, so please take that in mind, I'm looking for the easiest way to do this.

Any help will be highly appreciated,

Andrs

Is SQL Server Express installed as a prerequisite within the ClickOnce deployment or will a SQL Server be accessed which is not on the current client ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de