I was hoping that someone may be able to help me with an issue that I am having while trying to deploy my projects using MSI. Here is what I am trying to do.
I have two programs that are using MS SQL CE to share information. The first program is a windows service. The second program is a windows application that I am using mainly as a UI for the service. Each program has a seperate MSI setup program. I am using windows vista and VS 2005 on my developement machine.
The issue that I am having is when I deploy the programs. The windows service is working fine. It reads and writes to the database as expected. I know this because when I debug the UI program through VS 2005, I can read and write from the common SQL CE database with no issues. I am also pretty confident in the MSI program for the UI program because if I install the UI program on the developement computer and run the UI program as administrator it runs fine.
The issue arises when I simply open the UI program or when I try to run the UI program on a windows xp sp2 machine. I am no longer able to access the database file. I have tried many diffent things, but so far with no luck. Most of the attempts to fix this so far have been concerning the location of the database file these have had little or no effect. Again if I open the UI program using the right click option of 'Run as Administrator' in windows vista, the problem disappears.
Thanks in advance for any help. Even a push in the right direction would be helpful at this point. I will keep working on this issue, if I find a solution myself I will repost it here.
I'm using an XML file to configure my dataBase connection string. I try to deploy my package on a new server and it works perfectly.
Then I made a second package which also need a configuration for the dataBase connection string. (I made the connection with the connection manager inside packages). The configuration is the same that for my first package, so I thought to use the same configuration file.
I can use the same configuration file but the problem is when I try to generate a deployment for my solution. I got an error which tell me that the xxx.dtsConfig file already exist and can not be copy again.
When I made the configuration in the second package I said that I want to reuse the file ... and I thought that for the deployment SSIS would know that it has to include that file only once ...
Hi,I have some database files (.MDF, .LDF,...) on the server. When I tryto delete them, the warning "Cannot delete file: There has been asharing violation. The source or destination file may be in use."appears.Since I am new to the environment I don't know where the files comefrom and where they might be used.Can anybody tell me what to do to delete those files?Thank you.
This seems like a no brainer, but it's driving me nuts. I want one XML file for the entire solution. There are multiple packages in the solution which have different Connections in the conntion Managers. The packages share some connection names, and some are unique to the package.
Example:
LoadData.dtsx would have a source database connection named (SourceDB_OLEDB) and a oledb connection (DataWarehouse_OLEDB).
LoadDataMart.dtsx would use the same name for the (DataWarehouse_OLEDB) connection and have another oledb connection (DataMart_OLEDB)
I want one XML config file that has all the connection strings, but the problem is that the LoadDataMart.dtsx will throw an error:
Error 1 Error loading LoadDataMart.dtsx: The connection "SourceDB_OLEDB" is not found. This error is thrown by Connections collection when the specific connection element is not found. c:ssisLoadDataMart.dtsx 1 1
Hi, I am facing a wierd problem working with SQL Server Mobile edition database. The code works fine for some time and then it suddenly starts throwing "There is a file sharing violation. A different process might be using the file." I am disposing and closing the connection after each operation. Please find the function code below which is being used for any database operation.
I experienced a weird error while deploying my SSIS package. After running the manifest file, i noticed that one of the configuration file's path was not updated in the dtsx file. My solution has 8 packages and almost every package has 2 configuration files. Except 1 file every other config file's path is being updated. Has anybody experieced such a problem?
I have packages with the execute process task. I have included the exe-file from path A using add->existing item to the SSIS-project so that it lies under miscellaneous files. Deploying these packages using the deployment utility the file gets in the deployment folder that I copy to the server. Running the package installer and installing to SQL Server all files get copied to the B path (dtspackages under sql server by default). Trying to run the package however results in complaints about the file not being at location A. I thus changed the path in the execute process task to a relative one and then I get a complaint that the file "is not in path". So how do I do to make sure it finds the executable at location B where it actually is? I thought the deployment utility would handle this on it's own?
i created a solution that is working fine in development. I would now like to deploy it on an other server.
We have choosen for a file system -based deployment because this seems to require the least specialized SQL Server-knowledge from the user who will be utilizing this system. I changed the properties of the solution to
CreateDeploymentUtility: true
DeploymentOutputPath : binDeployment
Subsequently I build the solution and in the binDeployment-folder dtsx-files have been created.
Can anyone tell me what I need to do next to deploy them on an other machine?
Do I need to deploy a complete version of SQL SERVER 2005 Devenv included or is there a lighter installation possible that only contains what I need to run the packages?
Can I shedule the packages to run at a specified moment without DTultil coming up?
When you once found an answer to these many questions i would be most gratefull if you woulkd let me know.
I had VS2005 in my machine and was working with a mobile device using Sql Server CE. While compiling and deploying device application to my mobile device it used to deploy the Sql Server CE cab files also. But now i have migrated to another machine ( Vista OS ) and installed VS2005 newly etc., Now when i try out the deployment of device application to my mobile device it is not deploying the Sql Server CE cab files but just copies the SqlServerCe dll file. So when my application launches in the mobile device i get an error can't PInvoke sqlceme30.dll etc.,
I know that i can manually copy the cab files to my device and work. Its little tedious. Can anyone tell me how to achieve the behavior of my old VS2005 wherein it automatically deploys the SqlServer CE cab files? Is there a setting in VS2005 to enable this. I read in one of the posts that we can go modify the option Tools->Options->Smart device and enable an option to deploy the latest updates etc., But i couldn't find such an option in my VS2005.
P.S: I have installed my SqlServer Mobile edition 3.0 SDK to the default path under program files. Should i install it under VS2005 smartdevices SDK or something like that? I tried that also but still no success.
I am using XML config file to store the values e.g. Server name.... it runs fine with BIDS (Development enviroment)... but when I deploy and run it to test that XML config files values are being read by e.g. giving the wrong server name, it runs fine (may be retrieving some old values). then I come bak and test it again in the development enviroment to test, it fails ( as it supposed to be caz server name is wrong in config file)
I've read quite a few KB articles on deploying SQL Express silently using the command line and a .ini file. Unfortunately I still have some questions before I can make my own .ini file. This is for a local sql server.
What is the INSTANCENAME attribute meant to be? If it is different from the server installed on my local machine which I have coded the application on, would it be an issue? What should USERNAME/SQLACCOUNT and SQLPASSWORD be? I can't remember having to setup these for the local database so I can't imagine what it's meant to be set as. What is the PIDKEY?Thank you in advance.
Trying to build a deployment package. I have a number of dtsx in a project that share a connection config file. When I build, the error states: 'Could not copy file "whatever.dtsconfig" to the deployment utility output directory. ... The file already exists'
My parent package calls packages stored in the file system. While developing, I would like to call packages in the project bin directory. In production, I would like to call packages in a different development. Is this possible?
I can change the package connection string with an expression that refers to user variables PackageLocation1 or PackageLocation2. I would like to do this automatically. Is this something that should be done at deployment time? Or is there a run time value that I can check and conditionally use PackageLocation1 or PackageLocation2?
Development and deployment is done on the same server, so the same enivronment variable value would be used in an indirect configuration. Same thing applies to a file configuration.
Another question: Is it possible to set up a different Installation Folder for use during deployment? Every time I deploy, I have to navigate the folders, you can't even paste in the folder name.
I have a doubt in file system deployment in ssis. I read msdn articles like "MsDtsSrvr.ini.xml" will decide the default folder for ssis packages those are deployed to "File System".Â
I have installed SQL server 2012 of 64 bit in my system. My "MsDtsSrvr.ini.xml" file was reside in the path"C:Program FilesMicrosoft SQL Server110DTSBinn". This means when we try to deploy my packages to File System default path should come like "C:Program FilesMicrosoft SQL Server110DTSPackages".Â
But in my case path was coming like "C:Program Files (x86)Microsoft SQL Server100DTSPackages" even though my "MsDtsSrvr.ini.xml" reside in "C:Program FilesMicrosoft SQL Server110DTSBinn". i can't able to see my packages in SSMS when i connected to integration services.
I am trying to utilize DTUtil command to automate deployment of SSIS Package from the Build Server to Dev Server. I am getting an invalid option error, when I try to run the following command:
Currently I have a .CMD file, in which I have the above command, and I am trying to run the CMD file and it returns an error. Can someone help me the DTUtil switches. My goal is to move a DTSX file from Server A(Build Server) to Server B(Dev Server). Also is there a switch to specify the server name, if UNC path is not supported. Also I am using File System Deployment, and running the file as an Administrator. I have admin privs on both Build and Dev Server. Thanks and I appreciate some help on this.
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.
Not sure this is the correct forum, but I'll give it a go. I am in the process of deploying a series of databases from a development environment to a production environment. I've done some searching around best practices, but haven't found anything specifically calls out what is best. I am looking to find out the best approach for moving the code/tables/views/SP's, well everything from my dev environment to the production environment. Due to the complexity and large number of objects to be created, would a backup/restore to the production server be more prudent than creating a batch file type thing that creates all the objects through a series of scripts?
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 ?
We are setting up a new box and when we deploy the cube we are getting the error "File system error: The following error occured during a file operation: Access is denied. ."
We are part of an AD group that is a member of the administrators group on the box, and it looks like we have rights to the data directory where AS deploys cube data to. The account that AS service runs as is also an administrator on the box. It is a domain account. The cube does have one assembly - might that be the problem? We have set up a few boxes in the past without problems - we didn't have control over how this box was setup, so obviously we are missing a permission. If anyone has any insights / ideas, I'm all ears.
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.
I will be moving my website from my local dev server to the live environment soon. I've been using SQL 2000 to develop, but the live DB is SQL 2005. My app uses exclusively stored procedures for all data access. What suprises are in store for me when I migrate the site?! Thanks, Jamie
I€™m interested in reading about best practices or recommended deployments for MS SQL 2005. Currently our company owns 8 x SQL 2005 Enterprise Processor licenses. We have 4 HP DL380€™s with the following configurations:
6GB RAM
Mirrored 72GB drives for OS (Windows 2003 Ent R2)
4TB Shared storage (SAN) (15K Fiber Channel)
Dual 3.6GHz Processors
We would like to create a highly available data warehouse. We considered running the SQL engine on one set of servers (Cluster 1) and running the reporting, analysis, browser, etc., services on the other set of servers (Cluster 2).
Is this possible with MS SQL 2005?
How do we install and link all the servers together?
Is this a poor design?
With the above hardware and software, what would be the best deployment for availability, distributed processing, speed, and reliability and scalability?
Do we need to perform any special checks when we deploy SQL Server application developed using 32 bit SQL 2005 Edition in 64 bit SQL 2005 Edition?
To my understanding, 64 bit SQL Server 2005 provides better memory management and provides high performance when compared to 32 bit and it should not be an issue in deploying the application developed in 32 bit SQL Server 2005 in 64 bit environment.
Any help/hints on deploying in 64 bit SQL Server (for a product[SPs, TSQL Stmts] developed using 32 bit SQL Server) is appreciated.
I'm a beginner of database. I have some really "novice" questions here.
Currently I'm trying to upload my database to a share windows host server. I have problems uploading my database files.
I'm using Visual Studio 2005 and SQL 2005 express version. I was told that in order to upload my database, I need to have.bak file of my database.
The problems are:
1. under my visual studio server explorer, it seems I have two databases, one is ASPNETDB.MDF, another one is (mycomputername)sqlexpress.(databasename).dbo. I dont know from which one I can create the .bak file, and how?
2. I can not find where the phsyical location of my files (such as tables or stored procedures) from my (mycomputername)sqlexpress.(databasename).dbo database.
Hi- I am trying to use the same SQL Server 2005 express DB with two different project. I am using the Data Source=.SQLEXPRESS;AttachDbFilename syntax in the connection string. The first project can attach and connect just fine. The second project is a windows service that uses the same connection string. The windows service cannot connect to the DB though. It looks like it is trying to attach the DB again even though it is already attached. Shouldn't it only try to attach it if it isn't already attached? Here is the error: System.Data.SqlClient.SqlException: CREATE DATABASE permission denied in database 'master'.Cannot attach the file 'C:path' as database 'dbname'.
Is there another way for users to access reports online besides the Report Manager? Or is there a way for users to go to a URL that does not include the server? The same question goes for Report Models and Report Builder. Can they access these features without access to the server and databases?
i have SSRS project which has 40 reports and one datasource. I have deployed my reports to report server and tested. every thing is working fine. but recently when i made changes to the reports and tried to deploy them, they are not getting overwritten. although the data source is getting overwritten as i set the Overwrite property to true. can any one help me?
C:Program FilesMicrosoft BizTalk Server 2006Tracking>bm.exe deploy-all -Defin itionFile:testtype.bam.xml Microsoft (R) Business Activity Monitoring Utility Version 3.5.1602.0 Copyright (C) 2006 Microsoft Corporation. All rights reserved.
Using 'BAMPrimaryImport' BAM Primary Import database on server 'MOHSASLPT13719S QLEXPRESS'...
Deploying Activity... ERROR: The BAM deployment failed. The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Clien t unable to establish connection). The SQL statement issued has failed.
The ExistsOnSQLServer method has encountered OLE DB error code 0x80004005 (Clien t unable to establish connection). The SQL statement issued has failed.
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 built an application that connect to MS SqlServer2005 using Native driver (sqlncli.msi) I install that file from MS site, I need to deply my application to the end-user, and I would like to know what files do I need to deploy to make sure the application is gona run okay on the client PC's.
I search in the registry for the driver, and I found this "sqlncli.dll", is it enough or I need to include more files !!
Has anybody ever had VS2005 sometimes crash when deploying reports? It only happens once and awhile, but it is annoying. I was hoping this would go away with service pack 1, but it didn't.
Another problem that I thought would be fixed is when you try to close VS2005 after working on reports and it states "Cannot close because an active modal is active" occasionally.
