Errors During Building Project With Deployment Utility And Configuration File
Sep 28, 2005
I am getting following error when "CreateDeploymentUtility" is set to true and I try building the solution. It tries to copy a file that already exits in inDeployment folder. I am using Sept. CTP.
We are trying to create a deployment utility for a solution. The issue we are facing is, we are using a single package configuration file and when we try to build the solution to create the deployment utility, the build process fails saying that the package configuration file already exists. THe reason for this is while trying to build, the utility copies the configation fiel for the packages, it copies for one, but for the second onward, when it tries to copies, it fails saying the file already exists.
Any idea how to overcome this, or else any suggestions how to perform the similar steps to create a deployment utility for a solution in which the packages share a single package configuration file.
We deployed the ssis package to SQL server and now trying to configure but it only allow use to change environmental variables there is no option to browse and select XML configuration file. Does this mean when you  are using SQL server deployment mode u can only use environmental variable ?
i want to create single xml configuration file which should include the details to configure all the files in all packages.
Usually as u know whenever we configure the package one xml config file is created where we can change the path name for file or database details. Like that we will create a xml config file for each package.
but i want the solution as on xml config file for multiple packages
#1 Anyone seen any good BLOGs on building solutions and what occurs? BOL is pretty thin in this area. Does it just spin through all the projects in the solution, validate them, copy the packages to their respective in folder, and add them to the manifest?
I am getting the following error when trying to run a deployment utility. The server only has .net framework 2.0 and sql server 2005 (rtm) installed.
If it's any help, this server was recently upgraded from the june ctp to rtm.
This is a production server, so a solution involving as little disturbance to it's current state would be preferrable.
Thanks in advance for any suggestions.
-Jeremy
TITLE: Package Installation Wizard
------------------------------
Unexpected error occurred.
------------------------------
ADDITIONAL INFORMATION:
Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
------------------------------
Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154. (Microsoft.SqlServer.ManagedDTS)
I'm looking at creating a sample utility script that will invoking scripts to deploy some SQL code. For example, a utlity script that will run a SQL script, and on successful completion, execute the next script.
Having not used SQLCMD at all before, and being very new to SQL2005 (< 1 month) please guide me if there is a better way of invoking this... For example, a way of avoiding the xp_cmdshell invocation!
The following code invokes a script, but I'm trying to find a way of getting a return code back from sqlcmd, so I can progress and do the next, or fail if the return code <> 0 (success).
[code]
--Process to create DB, Tables, and Stored Procedures
set nocount on
DECLARE
@Error int,
@ExecCommand varchar(512),
@FullFilePath varchar(255)
--create the database
BEGIN TRY
SET @FullFilePath = 'D:DocumentationProjectsIntegration ServicesBIDS ProjectsTesco DNF Integration ServicesTescoDNF ProductPromoSQL CodeOBJECTSCreate DB TescoDNF_SSISPackageManager.sql'
SET @ExecCommand = 'xp_cmdshell ''sqlcmd -S RgalbraithSQL2005_1 -i "'+@FullFilePath+'"'' '
In reference to the question raised in this thread http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1460591&SiteID=1
Since I'm not able to create a deployment utility, when a config file is shared among multiple packages and also I cannot get the permission from Sys Admins to use Env. Variables I'm struck.
Now I'm thinking of importing the package to Sql Server from the file system. Is there any caveats in this approach? especially regarding the config files?
[edit] Also, do I need any special permissions to view the Integeration Services node in Management Studio? We are using Integerated Authentication, neither do I'm able to run sp_start_job sp in the msdb database. [/edit]
I would like to have my developers responsible for deploying their SSIS packages to the Test/QA environment. I tried granting access to several of the stored procedures in msdb and the sysdtspackages90 table. The only thing that seems to work is granting sysadmin priviliges. Is there a server or database role that will grant the appropriate access? thanks
When I create a deployment utility I... - set AllowConfigurationChanges to True. - set CreateDeploymentUtility to True - DeploymentOutputPath is set to binDeployment - I click 'Build' and it creates the binDeployment directory and writes all my DTSX files and my dtsConfig file But it doesn't create a manifest file. Why not? Thanks
After moving my deployment folder to the Target Server, I run the Installation Wizard. As I move next, I am missing the window which is supposed to allow me to set package config values as stated in MSDN:
"If the package includes configurations, you can edit updatable configurations by updating values in the Value list on the Configure Packages page."
Does anyone know why I am not seeing it? In my deployment bundle which I have moved over has currently 3 files:
1) SSIS Deployment Manifest
2) SSIS Package
3) SSIS Config File
Again, I double click on SSIS Deployment Manifest, and it starts fine. I go thru the steps for File System Deployment, and then it prompts for installation folder path. After that, it takes me directly to validation. Why is it not showing me the Configure Packages Page as described in the MSDN Documentation. Please advise. Thanks.
I have created a solution which contains only 2 packages say Package1.dtsx and Pakage2.dtsx. I want to create a deployment utility to deploy onto other developers machince. I changed the project properties "CreateDeploymentUtility" to TRUE. When I do the build it is not creating the files in "Deployment" folder. It is saying Rebuild All Failed but the error is not showing.
For more information the 2 packages have 4 indirect configurations from environment variables which are storing the actual config file path.
Could someone please explain to me the client configuration utility in plain English please.
I have VB applications installed on the sales force`s laptops that log onto SQL Server through RAS and an ODBC connection. The client configuration utility is not installed on their machines, but everything works fine. The BOL say that when installing utilities, the user is given the option of selecting the net-library to use. I am not, when installing it on my NT Workstation, or W95 Operating system. The BOL also state that the control panel has an entry to allow selecting which protocol to use. I cannot see it
Who needs the client configuration utility installed, obviously not the clients, is it just the people who want enterprise manager on their desktops ?
I am completely confused by this application This is the one area of SQL Server where I am lost, help !
We had some problems in deploying the reports to the client. Previously we used to deploy the reports in our development environment through reporting project but now we need to physically deploy the reports to the client on 14 different servers. We don't have access to the reporting project on site. Is there any way to deploy the reports outside reporting project?
I have a SSIS package on my local machine, and would like to deploy it to DEV server. Which files should i be moving to the SQL DEV Server? and where? How do I modify connection managers or is there a way to do that from the Management Studio or some other way? Thanks and I would definitely appreciate some prompt advise.
I have a VS 2012 SSIS project with more and more packages being added. I've got project parameters so I'm committed to the project deployment model (which is pretty convenient BTW). My question is how we're supposed to occasionally limit the packages we want deployed. There are times when 2 or more packages may be in development and 1 is deployable and the other not. I can temporarily exclude the not ready package and then deploy. It seems cumbersome bringing it back in. BIDS complains that all the tasks have lost their connection managers; even though they're are present in the editor. And it makes a copy of the .dtsx.
what's the recommended way to work in this environment?
I've been searching for an answer to my question quite some time now and I've not been able to figure it out yet.
Situation: - I've created a SSIS package containing a bulk insert task. - I've added a package configuration containing the appropriate connection manager (i.e. dev, beta or live) - CreateDeploymentUtility = true - I've copied the deployment folder to our beta server and I started the manifest file to install the package to the sql 2005 server, after that I specified the config file location and changed the value so the approriate connection manager is used. - When I execute the package from the sql server the package doesn't read the value from the xml config file, it uses the connection which was originally specified in the package, whereas when I run the package from my BIDS it is reading the value from the xml config file?
I can't seem to figure out why this is happening? am I missing something here?
I've been doing some VB6 app development against a SqlExpress database, but have confusion with issues of deployment and configuration. It's my intention to distribute the app and db to client installations, both as stand-alone and network-ready shared access. Here's basically what's occurred thus far:
The database originated as an Access mdb file. Downloaded and installed SqlExpress, Tools, Manager, and sample database(s). Used the Upsizing Wizard in Access to create a SqlExpress db. Attached to the database in Express Manager so I could examine and access the table data. Hit the data through the application with the following connection string:
Now, some points of my confusion thus far with regard to deployment:
1. Named Instance and User Instance. I assume I'm using a Named instance with the preceding connection string. Honestly, I don't recall doing any kind of adminstative setup/configuration of the db except attaching to it in Express Manager, so I'm confused over why I would need a User Instance for a local copy of the database. Are there setup steps I've missed or did the Upsizing Wizard do them for me? I've read the white paper on user instance usage, but it raises as many questions to me as it answers. I do understand User instance is intended for local copy of the db, even though I'm not using it that way in development.
2. Do I distribute both the MDF and LDF files? I saw mention somewhere not to distribute the LDF log file, but the app doesn't work without it being there.
3. What has to be done for deployment to a server for shared acccess. Aside from installing SqlExpress, and possibly Manager, I'll need to configure for remote connection usage using Configuration Manager or Surface Area Configuation tools. Does this need an administrator to create and establish users accounts, rights, and such?
4. Are there any reference books out on this stuff yet, besides books online, which I don't find satisfactory.
5. Can SqlExpress coexist on Sql 2000 server? I realize SqlExpress is essentially Sql 2005, but our existing server is Sql 2000. Should it go on a different server?
Sorry for the myriad of newbie questions, but I'm a programmer and not a db admin.
We have an SSAS project that we want to auto deploy. I am not sure how to handle the external data sources in the project. This one in particular has a single external data source defined to Microsoft SQL Server.
I would like to be able to change the data source based on the environment. In SSIS projects I can do this by setting up environments in the SSISDB and linking them to project parameters in the SSIS project but SSAS projects don't seem to have a similar mechanism.
How to handle this? I would like to be able to have the build/deployment agent pass in server / database information to the data source based on environment (dev, QA, production).
The only way to automate this that I've discovered is to have an intermediary process that executes after the build that updates the generated .asdatabase and .configsettings files in the bin folder replacing the connection string information.
I had a package that was deployed to the SSIS server. That server went away. I would like to now deploy the package to a file system. What settings do I need to change in the package so that it will not attempt to deploy to a non-existant server?
Currently within the Configuration manager you are able to set the Target Deployment parameters such as serverurl , folder etc.. However is there a way to set the Datasource within these configuration settings. For example we have Dev,Demo, and Production sql servers that ideally would be set to to switch with their corresponding deployment target areas DEV,Prod,Demo Reporting service servers. However as it stands I find myself having to manually change the datasets to point to different Servers for testing and then back to the production when its ready to roll out.
did I miss some feature that allows me to do this within the vs ide or does this have to be done programatically?
I have deployed a project with multiple packages to SSIS 2012 db. I am able to configure the project parameters fine. But, I am not able to replace the package variable values with the 'Environment' variables.
I have an existing project that I have added a simple text file. I am using the Project Deployment Model for this project. I save the project, close it and open the project and the file is there under the Miscellaneous folder. I successfully deployed the project to the server. When I retrieve the project using the Integration Services Import Project Wizard, all of my package modifications are there and the packages up to date but the txt file I added to the Miscellaneous folder is not there.
I have 4 packages in one solution. I have created one configuration table in SQL server for all the packages. For each package, I have a different configuration filter in the same table. Everything works fine in the development environment.But when I create a deployment utility and deploy the packages, the values are not picked from the configuration table although I have re-created the configuration table in the new database.It tries to pick up the values from the database used in the development environment and thus it fails. I have changed all the connection strings in the package after deployment but still of no use.
I am not getting where I am going wrong. Any help would be highly appreciated.
I am going to have around 20 databases of size 75 MB, each database for a company and many users may access the database simultaneously because it is a web based project. I would like to know the system configuration. ie
Processors, memory
SQL Server configurations like. dedicated memory, open objects, locks, user connections, tempdb size and other factors.
If possible suggest me any site name where I can more info on that, or any other nice book on Admin and optimisation.
I have an reporting services (SSRS 2005) installed locally and I am trying to access it locally through : http://localhost/reportserver, but all I get back is this page.
localhost/ReportServer - /
Microsoft SQL Server Reporting Services Version 9.00.3054.00
Also when I try to connect to reporting services through SSMS I get the following error message.
Cannot Connect to Server ServerNameSQL2005
Unable to connect to the remove server (Microsoft.SQLServer.Management.UI.RSClient)
No connection could be made because the target machine actively refused it(System).
About my set up, I have SQL Server 2005 (SP2) installed in a named instance called SQL2005, I have reporting services set up to run under local system and I have gone through the RS config tool and everything in there appears to be correct. U double checked in IIS that the report server folder is "ReportServer" and not "ReportServer$SQL2005". I have set up full read write permissions to all the virtual directories, to my domain account which is also a local administrator. The user logs in under windows authentication (marked in the directory security tab in IIS, for the virtual directory & the default website).
Whenever I start the service however I get the following errors in the windows application log:
Report Server (SQL2005) cannot create the trace log C:Program FilesMicrosoft SQL ServerMSSQL.3Reporting ServicesLogFilesReportServer__05_15_2008_10_27_52.log.
Also I am unable to deploy my SSRS 2005 project from BI studio with more errors, I get the following exception thrown in a windows. (I am trying to deploy to the root "ReportServer" folder, not a sub folder.
A connection could not be made to the report server http://localhost/reportserver.
System.Web.Services.Protocols.SoapException: Server was unable to process request ---> System.InvalidOperationException: Unable to generate a temporary class (result=1) error: CS2001 "Source File "C:WindowsTempc-zsc7th.0.cs" could not be found.....
I don't have sharepoint installed, I do have the dashboard designer for Performance Point Server 2007 installed though.
I have been on this thing for hours, I have tried appending "$SQL2005" on to the end, stopping and starting RS Service multiple times. Change all the permssions in IIS so that the user can full control over the IIS virutal directory. I am at a loss at what else I could try.
I have stumbled on a problem with running a large number of SSIS packages in parallel, using the €œdtexec€? command from inside an SQL Server job.
I€™ve described the environment, the goal and the problem below. Sorry if it€™s a bit too long, but I tried to be as clear as possible.
The environment: Windows Server 2003 Enterprise x64 Edition, SQL Server 2005 32bit Enterprise Edition SP2.
The goal: We have a large number of text files that we€™re loading into a staging area of a data warehouse (based on SQL Server 2k5, as said above).
We have one €œmain€? SSIS package that takes a list of files to load from an XML file, loops through that list and for each file in the list starts an SSIS package by using €œdtexec€? command. The command is started asynchronously by using system.diagnostics.process.start() method. This means that a large number of SSIS packages are started in parallel. These packages perform the actual loading (with BULK insert).
I have successfully run the loading process from the command prompt (using the dtexec command to start the main package) a number of times.
In order to move the loading to a production environment and schedule it, we have set up an SQL Server Agent job. We€™ve created a proxy user with the necessary rights (the same user that runs the job from command prompt), created an the SQL Agent job (there is one step of type €œcmdexec€? that runs the €œmain€? SSIS package with the €œdtexec€? command).
If the input XML file for the main package contains a small number of files (for example 10), the SQL Server Agent job works fine €“ the SSIS packages are started in parallel and they finish work successfully.
The problem: When the number of the concurrently started SSIS packages gets too big, the packages start to fail. When a large number of SSIS package executions are already taking place, the new dtexec commands fail after 0 seconds of work with an empty error message.
Please bear in mind that the same loading still works perfectly from command prompt on the same server with the same user. It only fails when run from the SQL Agent Job.
I€™ve tried to understand the limit, when do the packages start to fail, and I believe that the threshold is 80 parallel executions (I understand that it might not be desirable to start so many SSIS packages at once, but I€™d like to do it despite this).
Additional information:
The dtexec utility provides an error message where the package variables are shown and the fact that the package ran 0 seconds, but the €œMessage€? is empty (€œMessage: €œ). Turning the logging on in all the packages does not provide an error message either, just a lot of run-time information. The try-catch block around the process.start() script in the main package€™s script task also does not reveal any errors. I€™ve increased the €œmax worker threads€? number for the cmdexec subsystem in the msdb.dbo.syssubsystems table to a safely high number and restarted the SQL Server, but this had no effect either.
The request:
Can anyone give ideas what could be the cause of the problem? If you have any ideas about how to further debug the problem, they are also very welcome. Thanks in advance!
I am trying to load Project Real. I get warnings when opening the RecurringETL package. However I created the two environment variables it's looking for and have confirmed these variables are functional. I am unsure how to troubleshoot this and am afraid to do anything given these warnings. Where is the configurations collection??????:
Warning 1 Warning loading TestHarness.dtsx: The configuration environment variable was not found. The environment variable was: "REAL_Configuration". This occurs when a package specifies an environment variable for a configuration setting but it cannot be found. Check the configurations collection in the package and verify that the specified environment variable is available and valid. C:Microsoft Project REALETLTestHarness.dtsx 1 1
Warning 2 Warning loading TestHarness.dtsx: The configuration environment variable was not found. The environment variable was: "REAL_Root_Dir". This occurs when a package specifies an environment variable for a configuration setting but it cannot be found. Check the configurations collection in the package and verify that the specified environment variable is available and valid. C:Microsoft Project REALETLTestHarness.dtsx 1 1
Warning 3 Warning loading TestHarness.dtsx: 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. C:Microsoft Project REALETLTestHarness.dtsx 1 1 Thanks
I am trying to configure log shipping on same server with different instances/I am facing the below error//Cannot open backup device.Operating system error 67(The network name cannot be found)Restore filelist is terminating abnormally (Microsoft sql server Error 3201)
Hi All,I've been struggling with this for hours...Could someone please advise me on how to convert my current File based SQL Server Express website to a Server based SQL Express one.Particularly interested in what I need to do in the SQL Express management tool, changes I need to make the projecvt itself and changes needed to get IIS to understand things have been changed.Thanks,Martin.
dear list can anyone figure out a workaround as to why OLEDB Provider MSDORA cannot store passwords I have all the info stored in a table (Project Real Best Practise) The user id I have stored in string ConfiguredValue gets transfered to OLEDB Provider MSDORA named (SQL_REAL_Source_myoradb) but not the password To workaround this bug only with MSDORA can aynonne sugest a setting I should use in package security ie the default is EncryptSensitiveWithUserKey?
thanks Dave
CREATE TABLE [admin].[Configuration]( [ConfigurationFilter] [nvarchar](255) NOT NULL, [ConfiguredValue] [nvarchar](255) NULL, [PackagePath] [nvarchar](255) NOT NULL, [ConfiguredValueType] [nvarchar](20) NOT NULL ) ON [PRIMARY]