The Configuration File Name Is Not Valid
Jan 28, 2008
The configuration file name "C:......XMLSSIS2005_ConStr.dtsConfig" is not valid. Check the configuration file name.
The path is correct but we got this error. Please help us.
ADVERTISEMENT
The Configuration Of The AdminConnectionTCP Protocol In The SQL Instance XX Is Not Valid.
Aug 28, 2007I have a 2 node SQL Server 2005 cluster with 2 named instances. Both appear
to be working properly with no issues but I have the following warning
message in the event viewer and I would like to know if it is something I
should be worried about.
Source: SQL Browser
Type: Warning
Category: None
User: N/A
Description: The configuration of the AdminConnectionTCP protocol in the
SQL instance XX is not valid.
The servers in the cluster are running with Windows Server 2003 X64 Enterprise
Edition, SQL 2005 Enterprise Edition SP2 X64.
I have failed the cluster over and I continue to get the message when I
start the instances in the cluster admin, but I don't appear to have any
other symptons. Client machines can connect without any problem and
transactional replication works no matter what node I bring the instance up
on.
I changed default TCP/IP port and disable/enable Named pipes, but no luck so far.
I see lots of postings about this message but it seems to be related to
SQLExpress and I am not using that here.
Any info would be appreciated.
The Configuration Of The AdminConnectionTCP Protocol In The SQL Instance SQLEXPRESS Is Not Valid
Mar 4, 2006Hello,
I am getting the following warning in the Application Event Log:
The configuration of the AdminConnectionTCP protocol in the SQL instance SQLEXPRESS is not valid.
The warning is logged by the SQLBrowser service.
This is happening on Windows 2003 server with SQL Server Express 2005. On the same machine SQL Server 2000 is installed.
I am currently unable to connect from remote clients to the instance of SQL Express and I believe it has to do with this warning (I've tried all the usual remote connection troubleshooting without success - enabled protocols, SQL Browser Service running, there is no firewall on the server, I disabled firewall on the client when trying to connect).
Does anyone know how to resolve this issue?
If you need additional information please let me know.
SQL 2005 Mobile : The File Is Not A Valid Database File
Jun 8, 2006I used SQl Server replication to create a new database (as I did using Visual Studio 2003) but when I go the Pocket PC and click on the file I get a native error 25011 with a description
The file is not a valid database file
An Internal error has occurred[,,,Databasename,,]
Interface defining error: IID_IDBInitialize
When I check on my Pocket PC what programs are available I've got Query Analyser 3.0 and SQLCE Query. It appears that the .sdf file is associated with SQLCE Query because when I use that to try and connect to the same database I get the same error.
If I use Query Analyser 3.0 (after having copied the .sdf file) to the temp directory I'm able to open the database.
There is a similar post to this one but it doesn't help me.
Is it that SQLCE Query is wrongly associated with the .sdf file?
If so how do I change that?
Or is there some other problem preventing me clicking on the .sdf db to open it?
I have recreated my project in Visual Studio 2005 and rebuilt all my components in 2005. There are some external ones that I use that I can't do this for.
The following is the build output that I get when I deploy to a clean PDA with a hard reset performed
------ Build started: Project: Printing, Configuration: Release Any CPU ------
No way to resolve conflict between "System.Data.SqlServerCe, Version=3.0.3600.0, Culture=neutral,
PublicKeyToken=3be235df1c8d2ad3, Retargetable=Yes" and "System.Data.SqlServerCe, Version=1.0.5000.0, Culture=neutral,
PublicKeyToken=969db8053d3322ac, Retargetable=Yes". Choosing "System.Data.SqlServerCe, Version=3.0.3600.0, Culture=neutral,
PublicKeyToken=3be235df1c8d2ad3, Retargetable=Yes" arbitrarily.
Printing -> C:DevmillarMobileSellercode2005MobileSellerMobileSellerPrintinginReleasePrinting.dll
------ Build started: Project: MobileSeller, Configuration: Release Any CPU ------
Consider app.config remapping of assembly "System.Data, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes"
from Version "1.0.5000.0" [] to Version "2.0.0.0" [C:Program FilesMicrosoft Visual Studio
8SmartDevicesSDKCompactFramework2.0v2.0WindowsCESystem.Data.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System.Windows.Forms, Culture=neutral, PublicKeyToken=969db8053d3322ac,
Retargetable=Yes" from Version "1.0.5000.0" [] to Version "2.0.0.0" [C:Program FilesMicrosoft Visual Studio
8SmartDevicesSDKCompactFramework2.0v2.0WindowsCESystem.Windows.Forms.dll] to solve conflict and get rid of warning.
Consider app.config remapping of assembly "System, Culture=neutral, PublicKeyToken=969db8053d3322ac, Retargetable=Yes" from
Version "1.0.5000.0" [] to Version "2.0.0.0" [C:Program FilesMicrosoft Visual Studio
8SmartDevicesSDKCompactFramework2.0v2.0WindowsCESystem.dll] to solve conflict and get rid of warning.
C:WINDOWSMicrosoft.NETFrameworkv2.0.50727Microsoft.Common.targets : warning MSB3247: Found conflicts between different
versions of the same dependent assembly.
MobileSeller -> C:DevmillarMobileSellercode2005MobileSellerMobileSellerMobileSellerinReleaseMobileSeller.exe
C:DevmillarMobileSellercode2005MobileSellerMobileSellerMobileSellerfrmInvoice.vb(546,9): warning VSD101: Members not
supported by the device platform should not be called: System.Windows.Forms.Panel.set_Text is not a supported method in this
platform.
C:DevmillarMobileSellercode2005MobileSellerMobileSellerMobileSellerfrmInvoice.vb(634,9): warning VSD101: Members not
supported by the device platform should not be called: System.Windows.Forms.Panel.set_Text is not a supported method in this
platform.
C:DevmillarMobileSellercode2005MobileSellerMobileSellerMobileSellerfrmInvoice.vb(706,9): warning VSD101: Members not
supported by the device platform should not be called: System.Windows.Forms.Panel.set_Text is not a supported method in this
platform.
C:DevmillarMobileSellercode2005MobileSellerMobileSellerMobileSellerfrmInvoice.vb(846,9): warning VSD101: Members not
supported by the device platform should not be called: System.Windows.Forms.Panel.set_Text is not a supported method in this
platform.
Done building project "MobileSeller.vbproj".
------ Skipped Deploy: Project: BO, Configuration: Release Any CPU ------
Project not selected to build for this solution configuration
------ Skipped Deploy: Project: Printing, Configuration: Release Any CPU ------
Project not selected to build for this solution configuration
------ Deploy started: Project: MobileSeller, Configuration: Release Any CPU ------
Deploying 'C:DevmillarMobileSellercode2005MobileSellerMobileSellerBOinReleaseInTheHand.Data.Adoce.dll'
Deploying 'C:DevmillarMobileSellercode2005MobileSellerMobileSellerBOinReleaseInTheHand.Interop.dll'
Deploying 'C:DevmillarMobileSellercode2005MobileSellerMobileSellerPrintinginReleasePocketHTMLprint_NetCF.dll'
Deploying 'C:DevMILLAR CODE CABINETVS2003CFReferencesUSICF.dll'
Deploying 'C:DevVS2005CFReferences
eleaseSignature.dll'
Deploying 'C:DevVS2005CFReferences
eleaseRealUpDown.dll'
Deploying 'C:DevmillarMobileSellercode2005MobileSellerMobileSellerPrintinginReleasePrinting.dll'
Deploying 'C:DevVS2005CFReferences
eleasePhoneAPI.dll'
Deploying 'C:DevVS2005CFReferences
eleaseMVnetApplication.dll'
Deploying 'C:DevVS2005CFReferences
eleaseMobileHList.dll'
Deploying 'C:DevVS2005CFReferences
eleaseMobileGrid.dll'
Deploying 'C:DevVS2005CFReferences
eleaseImageButtons.dll'
Deploying 'C:DevVS2005CFReferences
eleaseCreditCardValidator.dll'
Deploying 'C:DevmillarMobileSellercode2005MobileSellerMobileSellerBOinReleaseBO.dll'
Deploying 'C:DevmillarMobileSellercode2005MobileSellerMobileSellerMobileSellerinReleaseMobileSeller.exe'
========== Build: 3 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 2 skipped ==========
After Restoring MASTER Database, Can't Start SQLServer Service: Configuration Block Version 0 Is Not A Valid Version Number
Jul 16, 2007Now, I checked and verified that my backup version of SQL Server is the same as the version installed on the computer I'm restoring too.
I have SQL Server on a production machine that I backed up and want to test a full restore on a dev machine to make sure it will work when I need it to.
Now that I've run the restore command on my tape backup and go to restart the SQL server service I receive:
Configuration block version 0 is not a valid version number. SQL Server is exiting. Restore the master database or reinstall.
I'm afraid I don't understand why this is happening. If the builds are the same, then shouldn't restoring the MASTER database have worked normally and I'd be able to restart the service now?
Any thoughts or suggestions?
File Format Is Not Valid
Jun 12, 2015when installing sql server error showing file format is not vaild
View 3 Replies View RelatedBackup Master Key, Cannot Write Into File 'c: Empmaster'. Verify That You Have Write Permissions, That The File Path Is Valid.
Jul 12, 2006Hi,
I tried to backup the master key by the following syntax :
OPEN MASTER KEY DECRYPTION BY PASSWORD = 'mypassword'
BACKUP MASTER KEY TO FILE = 'c: empmaster' ENCRYPTION BY PASSWORD = 'mypassword'
but it failed and i got the following message:
Cannot write into file 'c: empmaster'. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
NB: I am using the "sa" user to execute this command.
I know that we have a security permission issue , but where and how ?
Regards,
Tarek Ghazali
SQL Server MVP
%1 Is Not A Valid Win32 Application - Trying To Execute A Batch File
Feb 12, 2008Today I ran into the error (see title of this post) while trying to execute a batch file using SSIS. If anyone else runs into this problem I want to point them to my post on the issue, as I did not easily find a solution when doing the search myself: http://blog.lyalin.com/2008/02/1-is-not-valid-win32-application-ssis.html
Summary (So you dont need to visit my blog):
I was trying to execute a totally empty placeholder batchfile and this produces the "%1 is not a valid win32 application" error when using Execute Process Task. Simply add something to your placeholder file (like DIR command) and you can continue running your package without error
I hope this saves someone time in the future.
Comments? If anything in my post is inaccurate I hope you guys post some corrections.
Regards,
Dmitry
http://blog.lyalin.com
Package Failure - Multiple Synchronous Data Flows - File Name Not Valid – /3GB /PAE
Apr 23, 2008I have a package with 10 synchronous dataflows, which, combined, load about 300MB of flat file data to a database. This package would run successfully on 2 of our database servers, but would regularly fail on a third. The server on which it was failing is a 4 processor box with 16GB Ram with Windows Server 2003, SQL 2005, SSIS and SSRS installed - much more robust than one of the others that the package worked on. The SSIS error messages returned alternated between the following (with no apparent reason why one would show up rather than another, though the first was the most common):
"The file name "\Server1Folder1File1.txt" specified in the connection was not valid."
"The file name property is not valid. The file name is a device or contains invalid characters."
"An error occurred while initializing the flat file parser."
For the first error message, the error would report different connection managers and their associated file as invalid from run to run. All of the files across the 10 dataflows resided in the same network folder, and the package would read in and process a few of them before failing, so the problem was definitely not the connection string.
Searching the forums, etc. for these errors provided no useful information - given the real cause of the problem, these error messages are worse than unhelpful, they send you looking in the wrong direction. It was only when trying to track down another problem on the same server that I discovered the issue. When trying to copy database backups greater than 12GB over the network to this server, the operation would fail with an "Insufficient System Resources" message.
Some research led to the discovery that problem was caused by the /3GB switch in the boot.ini file of the server (don't let your Server team use that switch if you have 16GB of memory or more). Removing the switch and setting SQL to utilize AWE, fixed both the file copy problem AND the SSIS package failure problem. The SSIS package failed, not due to a bad connection string, but rather to insufficient server resources (read memory) to handle the simultaneous connections.
I hope this may help any others trying to track down this kind of SSIS package failure.
I will also provide here what I have gleaned about setting up Memory usage for SQL Server 2005 running on 32 bit Windows Server 2003 (with the caveat that I am no expert €“ corrections and additional information are welcome).
The following links got me started in my research (thanks to the folks who provided such useful information):
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=55191
http://articles.techrepublic.com.com/5100-10878_11-6091280.html
http://www.simple-talk.com/community/blogs/brian_donahue/archive/2007/09/30/37747.aspx
http://blogs.technet.com/askperf/archive/2007/03/23/memory-management-demystifying-3gb.aspx
http://www.modhul.com/2007/11/10/optimising-system-memory-for-sql-server-part-i/
Also, search BOL for:
Server Memory Options
Enabling Memory Support for Over 4 GB of Physical Memory
Enabling AWE Memory for SQL Server
Windows Server 2003 provides access to 4GB of virtual address space. By default, 2GB is assigned to the OS and 2GB to applications. This default can be change to 1GB for the OS and 3GB for applications by the use of the /3GB switch in the boot.ini file.
Physical memory over 4GB can be addressed by enabling Physical Addressing Extensions (PAE), which is done by setting the /PAE switch in the boot.ini file. This does not increase the systems virtual address space, rather it increases the size of the page table (which is maintained within the virtual address space), adding entries to reference the physical memory above 4GB.
It is important to note that these two switches are not interdependent (they do different things and you can turn each on or off regardless of the others status), though the combination of them has an impact on server performance and the maximum amount of physical memory which can be addressed.
The /3GB switch only impacts the allocation of the first 4GB of memory (virtual address space) between the OS and applications (default 50/50 % split, with switch on - 25% OS and 75% applications). The /PAE switch enables the system to reference/manage physical memory above 4GB, but does not alter the allocation percentages of the first 4GB of memory between the OS and applications. However, when PAE is enabled, the OS requires more memory within the first 4GB to manage the physical memory above 4GB (due to increased page table entries). With the /3GB switch, the OS has only 1GB of virtual address space, and only enough space to manage a total of 16GB of physical memory. If 32GB of physical memory is installed, 16GB of it will go to waste.
Address Windowing Extensions (AWE) is an API that allows an application to address more than the 2-3GB of memory that is available to applications within the virtual address space (first 4GB of memory). SQL Server can utilize AWE to take advantage of memory above the first 4GB that is made available via PAE, and can even reserve portions for its own use. I believe (though I can€™t remember where I got this bit) that SQL utilizes AWE memory only for the page cache (buffer pool €“ which seems to be a misnomer), and not for other operations.
To enable AWE, see the BOL references above.
The big question: what are the recommended settings for all of these? That all depends on what you have running on the server. You need to leave space for the OS, SQL Server and any other applications you have.
The hard and fast rules:
If you have more than 4GB of RAM, you must use the /PAE switch in order to take advantage of it.
If you have more than 16GB of RAM, you must NOT use the /3GB switch in order to take advantage of it.
Based on anecdotal evidence, I€™ve noticed the following generally recommended guidelines €“ assuming the server is dedicated to SQL.
Use of the /3GB switch seems to be a generally accepted practice if you have 8GB of RAM or less. For between 8 and 16GB, some say never use the /3GB switch, others say you can use it up to 12GB and still others up to 16GB. I interpret this to mean that it all depends on what types of loads are being placed on the server and that testing on individual servers will be required to determine whether or not to use the switch. Certainly that was my experience - the /3GB switch worked fine with 16GB RAM, until the server encountered a certain workload. For me, no more /3GB switch.
For setting SQL to use AWE, most seem to agree that it should be enabled if you have more than 4GB RAM. The setting of max server memory is more complicated. BOL seems to suggest (the €˜Server Memory Options€™ entry) a formula of Total Physical Memory minus 1-2GB for the operating system. Based on a desire to be a bit more conservative, I am now using the following formula:
max server memory = total physical memory
minus
4GB for the OS and application processes (since the AWE memory is utilized for page cache, not SQL processes)
minus
AWE memory required by other applications, including other instance of SQL Server
If anyone has additional insight, or a more refined equation, I could certainly benefit from it.
SQL 2012 :: Transaction Log Shipping Secondary Error - Tuf Is Not A Valid Undo File For Database
Jun 18, 2015I received an alert from one of my two secondary servers (all servers are running 2012 SP1):
File 'E:SQLMS SQL ServerMSSQL11.MSSQLSERVERMSSQLDATAMyDatabaseName_DateTime.tuf' is not a valid undo file for database 'MyDatabaseName (database ID 8). Verify the file path, and specify the correct file.
The detail in the job step shows this additional information:
*** Error: Could not apply log backup file 'MyDatabaseName_DateTime.trn' to secondary database 'MyDatabaseName'.(Microsoft.SqlServer.Management.LogShipping) ***
*** Error: Table error: Page (0:0). Test (m_headerVersion == HEADER_7_0) failed. Values are 0 and 1.
Table error: Page (0:0). Test ((m_type >= DATA_PAGE && m_type <= UNDOFILE_HEADER_PAGE) || (m_type == UNKNOWN_PAGE && level == BASIC_HEADER)) failed. Values are 0 and 0.
Table error: Page (0:0). Test (m_freeData >= PageHeaderOverhead () && m_freeData <= (UINT)PAGESIZE - m_slotCnt * sizeof (Slot)) failed. Values are 0 and 8192.
Starting a few minutes later, the Agent Job named LSRestore_MyServerName_MyDatabaseName fails every time it runs. The generated log backup, copy, and restore jobs run every 15 minutes.
I fixed the immediate problem by running a copy-only full backup on the primary, deleting the database on the secondary and restoring the new backup on the secondary with NORECOVERY. The restore job now succeeds and all seems fine. The secondaries only exists for DR purposes - no one runs reports against them or uses them at all. I had a similar problem last weekend on a different database that is also replicated between the same servers. I've been here for over a year, and these are the first instances of this problem that I've seen. However, I've now seen it twice in a week on the same server.
Log File Path In Configuration File Does Not Work.
Jan 25, 2007Hi,
I cannot get the log file path read from the configuration.
If the path in the Connection Manager is invalid, package throws an error "SSIS logging provider has failed to open the log" instead of reading it from the config.file. What am I doing wrong?
Here is the portion of the config file. Everthing else is read from the config file correctly.
- <Configuration ConfiguredType="Property" Path="Package.Connections[SalesforceConnectLog].Properties[ConnectionString]" ValueType="String"> ConfiguredValue>D:APPSBACIARSalesforceConnectSalesforceConnect.log</ConfiguredValue>
</Configuration>
Appreciate a help.
Gulden
Sqlexpr.exe Is Not A Valid Win32 Application, I Downloaded The Sql Express 2005 Edition When I Click On Exe File. I Receive A
May 26, 2006I am using a windows xp sp 2. I have visual web developer 2005 express edition. .net Framework 2. but when i downloaded the sql 2005 express edition. when i click on the sqlexpr.exe. I receive a message " sqlexpr.exe is not a valid win32 application".
just to try I downloaded the framework 2. for win32 , when i click on the exe file I receied the same message.
Well someone help me please with the sql server. i have almost given it up and using this tool for my last resort.
Thanks
trying hard
Configuration File
Jan 4, 2006Is there a configuration file in SQL Server where I can find basicconfiguration of the server such as instance name, home folder, datafolder, etc.
View 1 Replies View RelatedConfiguration File Not Always Used
Oct 1, 2006I have a simple SSIS package (stored in the file system) that gets a file path from a configuration file. The configuration type is an indirect XML configuration file that uses an environment variable to store the location of the configuration file.
When I run the package using dtexecui, or just dtexec from a command line, the package successfully picks up the file path from the configuration file (for verification I am writing out the variable containing the path to the log file). However when I run the package from a SQL Agent job it appears that the configuration file is not being used (the path is set to the same dummy path that I used during development). I have tried running the job as both a CmdExec and an Integration Services job and both fail on the same thing (invalid file path).
Both the SQL Server Agent service and the Integration Services service use a domain account as their start up account. This domain account has been included in the local administrators group on the server (in case it was having trouble accessing the environment variables).
What is the problem here €“ surely changing the way in which the package runs should not affect the configuration file settings! Any help would be appreciated€¦
[help] SSIS File Configuration (XML)
Apr 3, 2007We are deploying our SSIS packages into different folders. For example:
Test1
est2
production
Test1 points to the Test1 database, etc.
So, I configured my SSIS package to use a database connection called dbMAIN.
I then setup the SSIS File Configuration (XML) so that "dbMain" points to Test1. This xml file, called Global.dtsConfig, sits in C: est1, the same place as my ssis.dtsx file.
I want to copy my dtsx file and my dtsconfig file into est2 and production. The problem is that the the location of dtsconfig is HARDCODED in the ssis package!
How do I dynamically change it?
I tried to hardcode the location to ".Global.dtsconfig", but that did not work! Please advise!
Configuration File Issue
Mar 29, 2008Hi,
I'm sitting down again to see if I can get configuration files to work. To test, I've set up a simple package that reads a flat file and writes to a table.
I've enabled configurations by clicking the checkbox in the configurations window. I am using an xml file on the local server, and there is an absolute path defined to the file. I also added a password to the xml file so the connection will work. To this point, everything works.
However, when I go into the configuration file and edit it to point to another server, it doesn't pick it up!
That is, when I run my package, it still writes the data to the old server. It's like it's completely ignoring the configuration file and just using the OLE DB connection manager instead.
However, if I delete the OLE DB conn mgr, the package doesn't work.
Please help... this is where I got stuck before.
Thank you
Is It Possible To Read Configuration From An INI File ?
May 19, 2008Hi guys,
That's the question. I'm sure I will be encourage to use xml or other configuration types rather than INI files. But INI file has the advantage of not embedding any object property path and can be used for both packages and other applications.
Imagine a large implementation with hundreds of packages and dozens of class libraries and applications which are configured from the same INI file.
Imagine also that the production environment must support both DTS 2000 and SSIS 2005 packages as it's impossible to migrate all at once.
I've read that SSIS would support INI configuration files:
In Package Configurations Kirk says:
"...The two types of package configurations that haven't been documented yet in books online is INI and SQL configurations. INI package configurations have basically been provided for backward compatibility..."
And in BOL, in the DTSConfigurationType Enumeration description we can find that the INIFile configuration Type is also mentioned.
Anyway, a possible workaround is building a custom task with an UI that allows to assign INI keys to object properties, but I wanted to know if it's possible to avoid this.
Thanks in advance
Leandro
Dtutil And Xml Configuration File
May 14, 2007Hi,
Im loading the packages with a dutil-batch from the file-system into the sqlserver.
All the packages have xml-configuration-file.
for %%f in (*.dtsx) do dtutil /FILE %%f /COPY SQL;%%~nf /DestServer server /QUIET
When I try to run the packages in the sqlserver environment there is no configuration file found.
Is there a possibility to transfer also the link to the xml-configuration-file xml-configuration-file with dtutil?
Thanks Gerd
Configuration File Issues
Jan 18, 2008
I created an SSIS package that is connecting to 2 SQL Databases, one connection is using windows auth and the other database connection is using SQL Auth to connect to the database. I setup a config file to use for my ID, servername, database, and password but when I run my SSIS package it fails stating'
"[Execute SQL Task] Error: Failed to acquire connection "dbConnection". Connection may not be configured correctly or you may not have the right permissions on this connection."
If I open up my connecting dbConnection in Connection Manager the username is filled it but the password is blank, if I enter in the password and click 'test connection' it passes. I have the ProtecionLevel = EncryptSensitiveWithUserKey but the password is still 'blanked out' So my question is
1) how can I use the config file to store my id and pwd for my db connection?
2) how can I get my package to read the config file to get the ID and password for my database.
3) is there another way to do this? Would a varaiable work for this, if so how do they work?
Dtexec Vs Configuration File
Oct 9, 2007Hello,
I have a package where I store connection managers in a configuration file (XML file). I updated manually the XML file to add the passwords.
When I launch the command line generated by dtexecui, everything is good:
"dtexecui /FILE "E:mssql90DTSPackagesBVOMDWRefreshStage Refresh EUR 1.dtsx" /CONFIGFILE "E:mssql90DTSPackagesBVOMDWRefreshEnv_Prod.dtsconfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW "
When I launch the command line with dtexec:
"dtexec /FILE "E:mssql90DTSPackagesBVOMDWRefreshStage Refresh EUR 1.dtsx" /CONFIGFILE "E:mssql90DTSPackagesBVOMDWRefreshEnv_Prod.dtsconfig" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EW ",
I have the familiar error: "Failed to decrypt protected XML node "DTSassword""
I have the package level set to "EncryptSensitiveWithUserKey", but I think I don't need to update it to "EncryptSensitiveWithPassword" because it works with dtexecui.
I don't understand... What I should do?
Thanks,
Guillaume
Configuration File Question
Mar 26, 2008I have sucessfully merged and recreated my 1st DTS package to SSIS. now I am working on the configuration file and deploying it. I have a question about config files. I have set one up to use with my package pointing to proudction data sources. If I wanted to to set one up for a development source do I just create another config file for development. How do I tell it then which config file to use when I am testing?
IE we only have one server but will have a production and a test db. Right now just have prodcution. We have just merged over from 2000 to 2005. Just wanted to make sure I understand how to point it to development when I want to to this. '
Stacy
SSIS Configuration File
May 28, 2007Hello All,
In my project, developers enable configuration on the packages they develop. This means that if a project has 100 packages, each one has its own configuration file.
If our primary database server changes, I have to go an update 100 configuration files.
This defeats the purpose of having a configuration file in the first place.
I want to have a configuration file which contains common settings for all the packages in the project.
At the same time, I should have the flexibility of having individual configuration files for the project.
Is this possible and how can I do this?
Configuration File Woes!!
Jul 6, 2007I have a package for which I have set ProtectionLevel to DontSaveSenstive.
I connect to a SQL Database which supports mixed authentication.
To connect to this server in a flexible way, I have enabled SSIS package configuration.
I have edited my dtsconfig file with notepad and put the right password there (I am able to use management studio to connect to that database using same password).
Now when I come back to BIDS and double click on my connection manager, it doesn't read the configuration from the config file. (it just has a blank password). So it seems that BIDS doesn't read the config file.
What can I do to make BIDS read the config file.
Also, is there a way to encrypt the password (without keys) in the configuration file?
regards,
Abhishek.
Package Configuration With XML File
Aug 30, 2006Hi,
I have about 40 packages in my job. One of the problems that I have encoutered is that I don't know how I could use same XML dtsconfig file for all of my files. Each SSIS calls different file.
The XML dtsconfig file is a replacment for my *.ini file in sql 2000. The dtsconfig file will hold paths to all different files. Each SSIS will take different file name at a runtime.
How can I have all the files paths in one dtsconfig file - and is it even possible to do that in SSIS?
Any help greatly appreciated....Thank you,
Maria
Web Services Task Editor: The Input Web Services Description Language (WSDL) File Is Not Valid
Mar 14, 2006I am trying to prove I can use SSIS to connect to a web service. The WS I am trying to connect to was developed by a vendor and covered by a NDA, but I was able to reproduce the issue with a public WS.
Here are the steps to reproduce the issue:
In the Web Services Connection Manager, I entered http://office.microsoft.com/Research/Providers/MoneyCentral.asmx?wsdl in the URL window. I am able to successfully "test" the connection
I pasted the above link into IE and saved the resulting XML as a .wsdl file on my local machine. In the Web Services Task Editor, General Tab, I specify the path to the .wsdl file and click on "Download WSDL" button. No Issues
When I click on "Input" and select "MoneyCentralRemote" from the drop-down for Service, I receive an error message saying "This version of the Web Services Description Language (WSDL) is not supported"
So the questions are:
Did I perform the above steps correctly?
What WSDL versions are supported in SSIS?
How can I tell what WSDL version was used to create the .wsdl I am trying to access?
If the WSDL is an unsupported version, is there a work-around to fix the issue?
SQL 2005 Enterprise Edition The Image File Setup.exe Is Valid, But Is For A Machine Type Other Than The Current Machine
Nov 28, 2006Hi All,
I have enterprise version software CD1 and CD2 of SQL server 2005
when i try to run setup.exe..the following error pops -up
The image file Setup.exe is valid, but is for a machine type other than the current machine
MY OS version is windows 2003 32bit Operating system...
I am suspecting the binarie may be of 64bit.. How do we check the binaries are 32 bit and 64 bit software
Thanks for your Help
Mohan
Which Configuration File Can Disable Traces
Nov 29, 2011When I restart the server that hosts the database engine SQL Server 2005 Standard Edition SP4, the trace gets up mytrace-5.trc with a size of 100 MB and id is 2, leaving the hard disk space, then the SQL Server stops execution of the trace due to lack of space. I do not know how to erase the trace, because I do not know where is it.
The archive log looks like : SQL Trace ID 2 was started by login "sa"
Trace ID '2' was stopped because of an error. Cause: 0x80070070(There is not enough space on the disk.). Restart the trace after correcting the problem.
I only know how delete a trace, knowing id.
EXEC sp_trace_setstatus 2, 0
EXEC sp_trace_setstatus 2, 2
Which configuration file I can disable all SQL Server traces. If I run select * from sys.traces, I just get the default trace:
id = 1
status = 1
path= D:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGlog_32736.trc
max_size = 20
stop_time = NULL
max_files = 5
is_rowset = 0
is_rollover = 1
is_shutdown = 0
[code]....
Package Not Finding Xml Configuration File
Nov 26, 2007Hi,
I'm having difficulty configuring a package to look for an xml configuration file that contains values for source/destination connection strings.
The goal is to be able to have a package and its configuration file on one file system and to be able to copy/move the file dtsx and dtsx.config between build/staging/production servers while only having to set the xml value for the source/destination configurations.
In the package, I've created an xml configuration file called zzz.config. I took the absolute path out of the location of the xml file so that I have
xml location = zzz.config
instead of
xml location = e:ssiszzz.config
I'm assuming that when it gets to the point of validating the location of that file, it starts by looking in the current directory where the package is found.
All is well as long as I execute the package through the execute package utility by double clicking on the package file.
The problem lies when configuring a job in the sql server agent, it doesn't seem to pick up the xml configuration values because its pointing to the old server and not the current server stored in the xml file. I'm assuming its because the current directory is not the package directory at this point.
How can I get around this? Do I have to move the xml config file (zzz.config) to another directory where the agent will look for?
I know I could configure this as an environment variable but this contradicts the point of having movable packages without any extra tweaks.
Any help would be appreciated.
Thanks,
Robin
Configuration File Reused By Different Packages
Jun 1, 2006I have two packages share same configuration file. There are 4 connections in the first package and 2 connections in the second. Configuration file contains properties for 4 connections. First package opens in VS designer with no error. The problem with second package.
I get error that connection exist in the configuration but not in the package
and
"Could not copy file " Master_Configuration.dtsConfig" to the deployment utility output directory. Master_Configuration.dtsConfig' already exists."
Any help?
Passwords In The SSIS Configuration File
Oct 17, 2006Thanks to some earlier help from this forum, I have my package running using configuration files and Windows Authentication. However, when I try to execute the package using Sql authentication, login fails for the user i am specifying. When I check out the configuration file, the connection string does not contain the password. I added the password to the connection string, but it does not cone back. I followed the instructions found on the following site:
http://www.nigelrivett.net/DTS/SSISConfigurationFile.html
After trying what was suggested there, I was still unsuccessful with my login attempt.
Anyone know how to set up a package to run using Sql authentication?
Thanks!
Craig
Configuring - Configuration File Path
Mar 6, 2008Is there any way I can configure the Configuration file Path.
I have an understanding that wherever I store my package but my Configuration file(XML) must be store in the place specified in the package. In my dev environment I have C Drive as such the package is in DevServerNameC:SSIS.
However, there is no C drive allocated in Prod envirnment as such package is going to rest in ProdServerName/SSIS
Now if I place my package and execute here and it will look for configuration files(XML) which are on C file path. Then I guess my package fails.
I am just wondering how can I make my package configure file path dynamic?
Universal Indirect Configuration File, Can It Be Done?
Nov 11, 2005Hi,
View 9 Replies View RelatedSSIS DTS Configuration File Issue
Nov 14, 2007I have an SSIS package (which is already delivered to the customer, so I can't change it), but I want to switch off (disable) one of the elements. I use a dtsConfig file (XML), so I want to just send an update to that config file to switch off the element.
So, I used the Package Configurations Organizer to generate a new config file with the element switched off, and it generated the following:-
<Configuration ConfiguredType="Property" Path="PackageRun Data LoadForeach Data FileLoad Invalid Format Recs into rej_dat_format_errors.Properties[Disable]" ValueType="Boolean">
<ConfiguredValue>0</ConfiguredValue>
</Configuration>
So I copied these lines into my "production" config file and ran the package, but got the following warning message:-
Warning: 0x80012017 at ImportData: The package path referenced an object that cannot be found: "PackageRun Data LoadForeach Data FileLoad Invalid Format Recs into rej_dat_format_errors.Properties[Disable]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
Can anyone explain why? Is there some issue with having spaces in the Path name perhaps? Is there some syntax to get around it? Why did it generate a Path that is wrong?
Thanks
- AA