Hey,
I have copied a C# express edition project from another machine and have opened the project up and changed the connection string but the project is not updating the database when I try to insert values from textboxes in forms. They seem do be getting into the dataset but not the sql datatabase.
I am getting alot of messages saying that it could not find the schema information for the dataset. Could these errors have anything to do with the project?
What else do I have to change in the project?
I am trying to move an entire SSIS project from one machine to another (with a different directory structure) in a Development environment. In addition to the packages themselves I have Data Sources and Data Source Views defined. I also have connection managers for Excel and SQL Server that use those data sources, and connection managers for flat files for my error logs. Finally, I have saved my package configurations in an XML file.
I've followed the steps in the following post to move my packages:
What else exactly do I need to do, though, to move my complete project. My objective is to start up BIDS on the new server, File -> Open -> Project/Solution and point it to the new <project>.sln file and have it work. I know I need to edit my config XML file, but other than that, how do I properly move/recreate the data sources, data source views, and solution files in the new location. I've tried several things, but with no luck.
I posted this question in the past and did not get any answer. I put all my sources on a remote server mainly for backup purposes (the remote server is backuped every day) but when I have the .sdf file I can not open it from the visual studio 2005 configuration server here is the description of the problem: I have an application that runs on a PDA and manage a database (.sdf) file I use C# with visual studio 2005 What I want to do is to add the database file (.sdf) to my project files and open a connection to it. The problem is that all my source file are stored on remote machine and not locally on my machine and the .sdf file is also stored with the project source files. When I try to add the file to the project I get the following error fro the data source configuration wizard :
"An error occured while retrieving the information from the database"
DRIVE_REMOTE Parameter Name : N:
I get the same error also when I try to open a new connection to the file from the server explorer. When i copy the file to drive "C:" I can open a connection to it with no errors.
hello everyone. i am new to the group so i aplogize if this question hasbeen answered recently...our sql db machine is too old. we bought a new server with which to replaceit. the trick is, we want to keep the name of the machine and db instancethe same.obviously, we don't plan on having two machine with the same name on thenetwork at the same time. how do we handle this?my first thought is to name the new machine with a new name (mach2),transfer over all the db's, take the old one (mach1) off of the network.rename the machine/instance to the old one (mach1).if i do this, can i drop the original instance on the new machine(mach2)-->register the new (mach1)? will my data be there?Thanks so much for any relplies!!!
I'm a beginner user. I'd like to move the whole database from a work station to a server, how should I do it in a safe way? First of all, I have a very basic question: How could I save a database in SQL Server? Thanks in advance.
SQL Server 2005, when moving a machine to a different domain and changing the hostname the logins such as domainSQLServer2005MSSQLUSER$hostname$MSSQLSERVER are still showing the old hostname and domain name. Does anyone know what impact this has on the system and also if there is anyway to update these accounts without reinstalling SQL Server?
My old database server runs SQL 2000 and has the CRM 3.0 app and database, our corporate web site (SharePoint Services 3.0) database, and Project Server 2007 database. The corporate site and project apps and web sites reside on our file server.
I want to move, upgrade or migrate the databases, corporate site and Project site to this new SQL 2005 server. I am a little unsure the best way to do this.
Should I move all the database first, then move the apps?
Should I do a restore of everything on the new server, and after I know it works just turn off the other server?
I am moving my SQL 2000 Server from a Small Business Server to a full version of Windows 2000 Server and SQL 2000 Server. I have had no experience doing this but have backed up and restored my production databases for practice in case a of disaster situation. Is there anything special I need to do to move everything, including the system databases to a new server and not loose any of the user logons, etc.?
I have a bunch of SSIS packages that were created on a 32-bit machine (OS as well as SQL Server) where they run without error. I have moved them to a machine with a 64-bit OS as well as 64-bit Enterprise SQL Server, SP2. Initially I encountered errors with the packages that contained Script Transformation tasks where I had to set PreCompile=True. This allowed me to execute the packages individually. When I try and execute them as a batch, I encounter errors on various packages. They don't seem to be consistent - sometimes the error occurs on one package, the next time it will be on a different package. Sometimes they occur pre-execute, sometimes post-execute. Here are a couple of example errors:
[OLE DB Command [1007]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ". [Insert Destination [1177]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "TCP Provider: An existing connection was forcibly closed by the remote host. ".
The source database is on a different server, but the destination database is on the same server as the SSIS packages for testing purposes. Any information would be appreciated...
Dear All,We have a procedure that takes12 minutes to run on the first server butthat same procedure now takes 3 hours to run on the second server using thesame data. Does anyone have any suggestions why this is happening and howto make the procedure faster on the second serverThanks in advance.Jeff Magouirk
Hi everybody. I have such problem: After I move my integration services packege to another machine it failed. I tried to recreate connection manager, but result is the same. If I create a simple SQL task in that package and try to execute it - it fails with info:
SSIS package "Main_Package.dtsx" starting.
Error: 0xC00291EC at Execute SQL Task, Execute SQL Task: Failed to acquire connection "SRV-DSA3.TIA_EXTRACTS_OriginalData.sa". Connection may not be configured correctly or you may not have the right permissions on this connection.
Books On Line makes breaking out the report server databases on to a separate machine from the report server itself sound very easy. I have tried it and it is but I can't get the report server to connect to the databases once they are on the other machine.
Everything was done by the book(s). We use SSRS only for intranet use so all inside firewall. The SQL Server 2005 services on both machines (including the RS Windows service) all run as the same domain administrator account, this account was used to log in to RS Config Tool and it was told to use this account under Windows Authentication to connect to the database server. The two machines are in the same domain, even on the same switch. The only difference is the one with report server on is Windows 2000 Server SP4 and the one to which the rs databases are moving is Windows Server 2003 SP1. The account mentioned above has sysadmin rights on both SQL Servers, as well as having all the RSExecRole rights as specified in BOL. And it has rights to logon as a service in group policy on both machines. Its password hasn't been changed.
The RS Config Tool completed fine and reported no errors.
But when you try to connect to the report server you get the error:
"The report server cannot open a connection to the report server database. The logon failed. (rsReportServerDatabaseLogonFailed)" The log shows that a privilege required by the client is missing but doesn't specify what! I thought this was all taken care of when the RS Config Tool told it which account to connect with.
This is driving me daft. It should be so easy!! Does anyone have any idea what might be wrong? Nothing says I need to do anything with the encryption key when I am keeping the report server itself exactly as it was and just moving the catalog - or have I missed something here?
Hi everybody, I moved my packages to the new machine, and have problem with parent variables. When child package tries to get parent variable value I get an error:
Information: 0x40016042 at LoopPackage: The package is attempting to configure from the parent variable "MAIN_SesId".
Warning: 0x80012028 at LoopPackage: Process configuration failed to set the destination at the package path of "Package.Variables[User::MAIN_SesId].Properties[Value]". This occurs when attempting to set the destination property or variable fails. Check the destination property or variable.
When deploying a project from within a SSIS project in Visual Studio 2012 to SQL Server 2012 Integration services server I get the follwoing error message:
Failed to deploy project. For more information, query the operation_messages view for the operation identifier '10'. (Microsoft SQL Server, Error: 27203)
For the given operation id there is no entry in view catalog.operation_messages.
For some reason in a Team Foundation Team Project that has multiple project types (SSRS, SSIS, WebSite, C# Business DLL...), the SSIS project makes itself the startup project to the team project. If I explicitly set another project as the startup project to the team project and then select an SSIS package in the SSIS project in the team project, the SSIS project becomes the startup project automatically.
I have been working on some SSIS packages for a while now and today while i was working i was trying to create a new connection and in the process there was an error and it said the BIDS has to be closed and i closed it but later when i open BIDS and try to open my project(.sln) from the file menu to work on the half done package it pops up an error which shows the path to my project location on the first line and next statement on the pop up error box says:
"Make Sure the application for the project type (.dtproj) is installed."
I tried to check some forums in which some suggested to try installing SP1 which i tried but ..i dont know why but the SP1 fails to install (i dont know if its causing problem becoz i already installed SP2 as i had some other problem before for which the cure was to install SP2).
Did anyone here face such a problem before ?
I'd really appreciate if the experts here can tell a cure for this problem.
I have a Visual Studio 2005 solution which contains a Sql Server Integration Services (SSIS) project.
In this solution I have explicitly set a Web application project as startup project, but whenever I edit a DTS package within the SSIS project, VS automatically sets the SSIS project as startup project and the package I edit as startup object.
Needless to say, this may cause some really unwanted incidents when running the solution - thinking that you're about to run the Web application project (that was explicitly set as startup project), but instead, you run the edited package in the SSIS project.
Is there any way to avoid having the SSIS project automatically setting itself as startup project, any workaround here at all? :)
in order to maintain a deployed project into an Integration Services Catalog I'd like to know if it is possible to import it into a new project inside SSDT.
I want to update value of a custom field for a perticular project in Project Server 2007 using PSI.
I have created 5 enterprise custom fields(A,B,C,D,E) through PWA/Server Settings.
I want to search all Projects on Server. If any project is having value for custom field A then I want to update rest of the custom fields(B,C,D,E) for that perticular project.
I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.
I took a SQL Server 2000 dts package and using the SQL Server 3005 legacy tools migrated it so I could still use the package withing SQL 2005 until I can build one using BI/SSIS.
Anyway,I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:
Dim oApp As New Application Dim oPkg As New Package oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing) Dim oResults As DTSExecResult oResults = oPkg.Execute
Ok. That works fine. Executes without a hitch. So now I try and create a setup project for this and I use the setup wizard.
During the creation of the setup project I get a message that states: The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project. C:windowssystem32msxml6.dll
OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.
How do I find this out?
Has anyone else created a project like this and experenced the same?
I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.
I've got an SSIS solution file with project deployment model in VS 2013 and would like to deploy that to SSISDB on different environments.All these days I followed the regular way to create a project in SSISDB and deploy it to that. Now want to find out if i can automate this process and so got some questions
1. Can we automate the process of creating a project on SSISDB based on our SSIS project name? This will be like when we do a deployment it should check if the project exists or not on SSISDB based on our SSIS project name, if the project exists we just deploy the packages in the project and if the project does not exists in SSISDB it will create that project and deploy the packages.
2. Can we also automate the process of creating environments? In traditional way we manually create the environment variables under environment tab of SSISDB, but can we make that also as part of deployment? Like when we are releasing to Dev server we look if that particular Dev variable exists on that server, if it exists we just update the existing stuff and if it does not exists we just create it.
I have visual studio 2005 and sql server 2005 with integration service installed on my machine. Couple of days ago, I installed visual studio 2008 professional. When I go to create SSIS project I dont see it in visual studio 2008. What do I have to do to make it appear in visual studio 2008 so that I can create SSIS projects.
I fail to use project professional 2003 to access to the project server 2003 using MSDE 2000 in local area network, following message was shown,
Connection failed:
SQLState: '01000' SQL Server Error 1326 [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()) Connection failed: SQLState '08001' SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
I have seen these pages with similiar cases but can't help.
Help! I am using Script Transformation to output a new column as image[DT_IMAGE] field to store serialized object. In the VB script, the sample code as
The package always runs fine on my developing machine and will halt on other machine at AddBlobData after certain number row records were processed. I am stuck here. Anyone has any suggestion?
What I need is reading data from mutiple tables in one database and writing into a single table in another datable. In order preserve all the columns data, I use input column fields to construct a new object and then serialize it, and store the serialize data into detination db table. (The object and serialization function is coming from c# dll.)
Dim b As BusinessLicense = New BusinessLicense() b.ApprovalDate = Row.approvaldate b.BusinessId = Row.busid b.BusinessName = Row.busname b.NaicsCode = Row.naicscode b.NaicsDescription = Row.naicsdescr b.OwnerName = Row.ownername b.Phone = Row.phone b.Pkey = Row.pkey b.RenewalDate = Row.renewaldate b.StartDate = Row.startdate b.Suite = Row.suite
Row.serializedobject.AddBlobData(Serializer.Serialize(b)) '''----This is blocking line Row.infoType = BusinessLicense.TYPE
Both machine is xp with sp2. and standard SQL Server 2005 - 9.00.1399.06
Hi to everyone, I'm facing a problem that drives me crazy. I've a web application that has the following problem. When I test the application on my developement machine all runs fine, but when I put into production server there is a problem in connection pooling. Look at the following image, the blue line is the number of connection in the pool and the violet line is the number of connection reclaimed. From the image it is clear that connection are returned on the pool only in block, maybe when the garbage collection pass and reclaim the object. The strange thing is that on my developement machine all is good, and also I'm using Enterprise Library and the connection are managed internally.- Thanks to everyone for any help.
Hullo all I have two machines, One is a standalone machine and the other is on a domain network. How can I run a stored procedure/job on the standalone machine from the domain machine ? running the procedure as a Domain user results in a failed job/stored proc. also creating an sql login and attempting to run it as that user also fails. How can I solve this problem ? please e-mail me at wayde@sunnygrp.com if you have any thoughts...
Hi All;We are going to change our application server. We will copy all of ourDatabase from Mic 2000 Server OS to Mic 2003 Server OS. I found anarticle that how to move all the folders from same OS. My question isthat Would the 2003 OS be a problem when we copy all of the MC SQL 2000folders to New OS ? Has anybody done this before? Could you gimme yoursuggestions please?ThanksASA
