Unable To Identify Child Package Events Post SP2 Install
Jun 8, 2007
Pre-SP2, log events that bubbled up from child packages used to be prepended with "User:" (as documented in KB906563). It appears that this behaviour has changed in SP2, and only the Diagnostic event gets prepended with "User:". When I debug a custom log provider, the event names are now clearly not prepended on any other event type.
Is this a bug, or a breaking feature? Can anyone suggest a way to identify events that bubble up from child packages under SP2, now that this has changed?
Hi can someone help me please? I browsed through the SP2 install feedback below, but it doesn't quite seem to fit what happened to my install. My .MDF and .LDF files for the system databases are in C:Program FilesMicrosoft SQL ServerMSQL.1MSQLData (I presume this is the correct location.)
I am the local administrator on this box.
I uploaded the .CAB file with all the logs onto www.sendspace.com if it gives you something to go on.
The only other thing of note is that it said there were two machines on the network and that I needed to change my machine name in the control panel when I installed. This doesn't seem right, as far as I understand the computer name is unique.
The SQL Server runs under the local system account, if that is of any use.
I attempted uninstalling and reinstalling the SQL native client MSI package in the hope it would be a simple fix similar to that chap further down the page, but that didn't help at all either.
.CAB file of installation logfiles is here: http://www.sendspace.com/file/7ihoet
kind regards Jason
ERRORLOG starting SQL Server post failed SP2 install
2007-06-12 19:55:21.94 Server Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86) Feb 9 2007 22:47:07 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
2007-06-12 19:55:21.96 Server (c) 2005 Microsoft Corporation. 2007-06-12 19:55:21.96 Server All rights reserved. 2007-06-12 19:55:21.97 Server Server process ID is 5468. 2007-06-12 19:55:21.97 Server Authentication mode is MIXED. 2007-06-12 19:55:21.97 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. 2007-06-12 19:55:21.97 Server This instance of SQL Server last reported using a process ID of 5756 at 12/06/2007 19:36:35 (local) 12/06/2007 18:36:35 (UTC). This is an informational message only; no user action is required. 2007-06-12 19:55:21.97 Server Registry startup parameters: 2007-06-12 19:55:21.99 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf 2007-06-12 19:55:21.99 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG 2007-06-12 19:55:21.99 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf 2007-06-12 19:55:22.00 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2007-06-12 19:55:22.00 Server Detected 4 CPUs. This is an informational message; no user action is required. 2007-06-12 19:55:22.17 Server Address Windowing Extensions is enabled. This is an informational message only; no user action is required. 2007-06-12 19:55:22.33 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required. 2007-06-12 19:55:22.57 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-06-12 19:55:23.60 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required. 2007-06-12 19:55:23.63 Server Database mirroring has been enabled on this instance of SQL Server. 2007-06-12 19:55:23.72 spid5s Starting up database 'master'. 2007-06-12 19:55:24.07 spid5s SQL Trace ID 1 was started by login "sa". 2007-06-12 19:55:24.11 spid5s Starting up database 'mssqlsystemresource'. 2007-06-12 19:55:24.13 spid5s The resource database build version is 9.00.3042. This is an informational message only. No user action is required. 2007-06-12 19:55:24.29 spid5s Server name is 'GBLOND088SQ8MSQL_CREDS_DEV1'. This is an informational message only. No user action is required. 2007-06-12 19:55:24.29 spid9s Starting up database 'model'. 2007-06-12 19:55:24.30 Server Error: 17182, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server TDSSNIClient initialization failed with error 0x34, status code 0x1e. 2007-06-12 19:55:24.30 Server Error: 17182, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server TDSSNIClient initialization failed with error 0x34, status code 0x1. 2007-06-12 19:55:24.30 Server Error: 17826, Severity: 18, State: 3. 2007-06-12 19:55:24.30 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 2007-06-12 19:55:24.30 Server Error: 17120, Severity: 16, State: 1. 2007-06-12 19:55:24.30 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Yesterday, SQL Server 2005 SP2 was installed on our DEV Server (Windows 2003 SP1 x86) and now I cannot right-click a package in the Solutions Explorer window in BIDS and Execute Package. When I do, I get the following error
===================================
Object reference not set to an instance of an object. (Microsoft Visual Studio)
------------------------------ Program Location:
at Microsoft.DataTransformationServices.Project.DtsPackagesFolderProjectFeature.ExecuteTaskOrPackage(ProjectItem prjItem, String taskPath)
I know I could do this yesterday morning pre SP2. I've attempted this with a couple of different packages and solutions, so it is probably not a corrupt package (unless now they are all corrupt). I can execute in debug mode if I open the package first and then hit Start Debugging. However this is not always an optimal solution because I sometimes have many connected packages and sometimes what gets executed is not what is expected.
Does anyone know if it is possible to do Post-Build Events in Reporting Services? I am using Visual Studio 2005 Team Edition and creating Reports under the Business Intelligence Projects.
When creating C# projects, when you right click on the solution and go to properties there is a tab for Build Events at which point you can create Pre-build and Post-build events; however I am not finding this option available within a Reports project. Does anyone know if this is possible to do in Reporting Services?
Basically what I am trying to accomplish is, I am having to create multiple template files and there are multiple developers going to be working on this project and I would like to create a batch file of some sort that copies the template files that are created into the IDEPrivateAssembliesProjectItemsReportProject directory each time the project is built.
I have installed a single instance of SQLserver2005Express on a stand alone PC running WinXP Pro.
Do you always have to be logged in as a Windows [XP] administrator to work with SQL Server databases? Because when I'm not it SQLserver Management Studio won't allow me to open any database.
Also, do all databases have to be in the default data folder location [in my case this is: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData]? Because if I try and navigate to other databases I have in other locations using Management Studio they are not visible.
Today I attempted to install SQL Reporting Services on a box that only has the OLE DB driver for Analysis Services and the MSXML components; both of which are SP2.
When running the SQL Server 2005 install to install SSRS, I get an error:
"SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme."
This box has barely anything on it aside from ProClarity Analytics Server and the components I mentioned above. My only guess is that the SQL 2005 installer sees some newer components that are SP2 and it thinks they are beta? I know for sure I do not have any beta software on this machine.
Anyone starting to see "Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)" after installing SQL Server 2005 SP2 on x86 machines? Second, how can it be fixed?
After installing SP2, the script component editor will not edit script components created in pre SP2 releases. (I also have Visual Studio 2005 SP1 installed). The script TASK editor will start, but when attempting to open a script COMPONENT in the VSA editor, a script component created for pre-SP2 packages, the following error dialog occurs.
Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)
This same error dialog has occurred on multiple computers, none of them are running Vista (rather Windows XP SP2). All of the pre-existent pre-SP2 script components have Precompile set to true as well, since they are intended for 64 bit machines.
Now, certain posts say, register DLLs in the following directories via: for %i in (*.dll) do RegSvr32 -s %i.
One problem with these instruction is that the second directory doesn't even exist, however, a directory called "C:Program FilesCommon FilesMicrosoft SharedVSA8.0VsaEnv" does exist, which is perhaps what was meant. Even after registering the DLLs there, the script component editor will not open (erroring out after clicking the "Design Script..." button).
I need to provide a media kit to other DBAs in my organization so that when they run the setup.exe it will automatically apply some "hardening" scripts that my team has written. We want it to be a seemless part of the installation process so that the scripts can be applied consistently across the organization.
I created a package which passes some infornmations( through parameters) to its child package.
I need to do some processing in parent package based on execution status of child package.i.e.
if child fails then some operation and if child succeeds then other operation.
To determine the status of execution of child package I am using two differnt constraint ..one constraint is having value "Success" and other having value "Failure".
My problem is that when child packge is executed successfully the constraint with value = "Success" works properly but when child fails the constraint with value "Failure" does not work.
I have created a SSIS package with a Foreach Loop including a Data Flow Task, which in turn include a Row Count component which pass the row count value to variable with package scope. The variable is used in an Execute SQL Task following the Data Flow Task.
The package executes successfully when executed on its own, but when executed as a child from a parent package (which only include an Execute Package Task) the variable from the Foreach Loop becomes NULL.
There are a lot of other variables in the package receiving values dynamically without any problem, the row count variable however is the only variable in the package that receives a value as part of a Data Flow (and used in following tasks within the Foreach Loop).
Why does the variable become Null? For your information, I am using a variable with package scope and no variables from the parent package are used or passed from the child package to the parent package.
(For your information, we are running the 64 bit version)
The master package has a configuration file, specifying the connect strings The master package passes these connect-strings to the child packages in a variable Both master package and child packages have connection managers, setup to use localhost. This is done deliberately to be able to test the packages on individual development pc€™s. We do not want to change anything inside the packages when deploying to test, and from test to production. All differences will be in the config files (which are pretty fixed, they very seldom change). That way we can be sure that we can deploy to production without any changes at all.
The package is run from the file system, through a job-schedule.
We experience the following when running on a not default sql-server instance (called dkms5253uedw)
Case 1: The master package starts by executing three sql-scripts (drop foreign key€™s, truncate tables, create foreign key€™s). This works fine.
The master package then executes the first child package. We then in the sysdtslog get:
Error - €œcannot connect to database xxx€? Info - €œpackage is preparing to get connection string from parent €¦€?
The child package then executes OK, does all it€™s work, and finish. Because there has been an error, the master package then stops with an error.
Case 2: When we run exactly the same, but with the connection strings in the config file pointing to the default instance (dkms5253), the everything works fine.
Case 3: When we run exactly the same, again against the dkms5253uedw instance, but now with the exact same databases defined in the default instance, it also works perfect.
Case 4: When we then stop the sql-server on the default instance, the package faults again, this time with
Error - €œtimeout when connect to database xxx€? Info - €œpackage is preparing to get connection string from parent €¦€?
And the continues as in the first case
From all this we conclude, that the child package tries to connect to the database before it knows the connection string it gets passed in the variable from the master package. It therefore tries to connect to the default instance, and this only works if the default instance is running and has the same databases defined. As far as we can see, the child package does no work against the default instance (no logging etc.).
We have tried delayed validation in the packages and in the connection managers, but with the same results (error).
So we are desperately hoping that someone can help us solve this problem.
We have one main package from which 7 other child packages are called. We are using ParentPackage variables to assign values for variables and database connections.
While the values from ParentPackage variable get assigned to some of the packages properly, to others it doesn€™t assign the value.
For example: Except for one of the packages the database connection string gets assigned properly to all other packages.
Similarly, in another package one of the variables doesn€™t get assigned. In other packages it is assigned properly.
We have checked all the other property values and they are exactly the same.
We cannot make any head or tail of this erratic behavior.
I am interested in Passing value from a child Package variable to the Parent package that calls it in ssis.
I am able to call the Child package using the execute package task and use Configurations to pass values from the parent variable to the child, but I am not able to pass the value from the child to the parent.
I have a variable called datasetId in both the parent and child. it gets computed in the child and needs to be passed to the parent...
Here's the deal. I have a child package, (say, pack01.dtsx), which uses a dtsconfig file for its connection string, which can be called from other packages, but which also can be called by itself.
However I also have another package (say, pack02.dtsx) which uses the same dtsconfig file for its connection string. It calls on pack01.dtsx.
When I use DTEXECUI and run pack01.dtsx, specifying the proper .dtsconfig file, it goes well. But when I try and run pack02.dtsx, an error occurs saying pack01.dtsx connection cannot be established.
How do I pass the connectionstring being used by pack02 to pack01, without having to remove the configuration file setting of pack01? Can a Parent Package configuration and a configuration file try and map to the same property?
I have a SSIS Package with a "Execute Package Task" to call a child package. I am trying to have the master/parent package complete its execution regardless the outcome (failure or success) of the child package. The overall structure of the master package is:
1. Perform Pre-load tasks (stored procedure).
2. Execute Package Task (call child package)
3. Perform Post-load Tasks (stored procedure)
I have try everything and cannot get the results that I want... I have tried the combination of "failparentonfailure", "forceexecutionvalue", etc. The master package stops at childs failure. I would like to resume to completion
I have two SSIS packages in a project, one calling the other. The parent package works fine in my local mechine. After they are deployed to the production, I schedeul jobs to run the packages in the SqlServer. The child package works fine if I run it alone, but the parent package could not find its child package if I run the parent package . As I checked, all xml config files and the connection string pointing to the child package were set correctly. It seems the parent package did not use the xml config file. Can someone help me? Thanks in advance.
Hi, In my application, i have two package, parent package and child package. the parent package is executing child package using a Execute Package Task. "Execute Out Of Process" property of Execute Package Task is set to TRUE. means the child package will be run in separate process not in the process of Parent package. this was working fine, but at a particular client location. its failing the error is "not able to load child package". for me it seems some setting on server restricting to create separate process for child package execution. when "Execute Out Of Process" property of Execute Package Task is set to FALSE. its working fine.
can anyone help what could cause its failure with property set to TRUE.
I am trying to figure out how to run an SSIS package that is encrypted but also has a child package which is encrypted. I am trying to run from the cmd line using dtexec and specifying DECRYPT <pwd> for the parent package but how do you specify for the child package.
Please help if you have seen such an issue before or you have a work around.
I have a parent package which calls a number of child packages. Occasionally, I have one child package which starts up and appears to finish but the parent package never gets notification that the child has finished. If I view this in Management Studio's in Integration Services, I can view the packages that are running and only the parent package is running. Because it never gets control back, the next child package will never get started and the parent package will continue to run and never finish.
I need to pass variables from the parent package to the child package. I got this to work in a small test case. But in the actual project, I get an error when I try to do that. The parent package's log has this error :
Error: Error 0xC0012050 whike loading package file "c:.......". Package failed validation from the ExecutePackage task. The package cannot run..
I run into some issues and really need some expert help here.
Here is the problem. I have two packages (parent.dtsx and child.dtsx). Both package have its own configuration file (parent.dtsConfig and child.dtsConfig). The file Child.dtsConfig contains a variable (i.e. "X") that is to be used by Child.dtsx.
Inside parent.dtsx. there is a package-task that calls into Child.dtsx. It worked perfectly well if I run parent.dtsx using Dtexec or from inside SSIS's IDE.
Now I want to programmably call "parent.dtsx" from my C# code. I loaded package using "app.LoadPackage"... Inside C# code, I want to reconfigure Child-package's variable ("X"). I then loaded in "Child.dtsx". However when I run "parent.dtsx" and child.dtsx still loads the original value for "X". The reconfigured value for "X" is not updated.
We've had this issue for awhile, but I have not been able to find a resolution for this. We have 2 identical servers (hardware & software) set-up: IBM x3850-(88633RU) running Windows Server 2003 Enterprise x64 (5.2.3790 SP1 Build 3790 R2). Server A was running SP1 (Build 9.0.2047) on a 3-node active-passive-passive failover cluster. Server B was running SP2 + Hotfix KB933097 (Build 9.0.3152) on a 2-node active-passive failover cluster. Both these servers are heavily utilized, and when originally installed with these versions of SQL Server Enterprise 2005 experienced no issues during or post-install. The original install of SQL 2005 Enterprise on both these servers had the Cluster Group Selection "Data files" setting changed to "M:MICROSOFT SQL SERVER" so that all system dbs and binaries would be installed to that location. On Server B where SP2 had already been applied, the update was downloaded on May 1, 2007, well after the GDR issues which had been plaguing SP2 releases was supposed to have been resolved.
Our problems began the night when we tried to apply hotfix KB933097 on Server A, and cumulative update packages 1,2,3 on Servers A & B, as well as catch-up the same SP2 and hotfix packages on other non-clustered servers where default system db locations remained the same. On all servers other than Servers A and B, the installs proceeded smoothly and without issue.
On Server B, which was already running SP2 + Hotfix KB933097, we tried installing Cumulative Update Package 1 (Build 9.0.3161) on the primary node. The install proceeded until the following errors were encountered:
"[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission."
"[Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_memory_grants', because it does not exist or you do not have permission."
After this, the setup finished with the message "Product: Microsoft SQL Server 2005 (64-bit) - Update 'Hotfix 3161 for SQL Server Database Services 2005 (64-bit) ENU (KB935356)' could not be installed. Error code 1603. Additional information is available in the log file C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB935356_sqlrun_sql.msp.log."
We rebooted the server and tried several times to reinstall the hotfix as sa and as the database service account with full windows and sa credentials, each time with no success, and rebooting between retries. All other components were installed successfully. We were hesitant to try uninstalling the hotfix, since it was unable to be removed successfully in previous attempts. However, when I connected to Database Engine using Management Studio, I found that the version of SQL being reported was in fact Build 9.0.3161! Everything also appeared to be running properly.
I tried to to Google the answer, but could only find information as applied to SP1 when system dbs master and mssqlsystemresource were located on different locations (http://support.microsoft.com/default.aspx?scid=kb;EN-US;918695 ). I had already verified that all system dbs, including the ones mentioned, were originally and currently located together on M:Microsoft SQL ServerMSSQL.1MSSQLData.
Finally I contacted a fellow DBA who advised me to continue installing all the other hotfixes, and then compare all SQL files against other servers where the install succeeded to ensure all system files were updated correctly (matching file sizes and datetime stamps). Since we were depending on a fix in Cumulative Update Package 3 to fix a critical log-shipping security issue, I went ahead with the rest of the installs, getting the same error with each package, rebooting between each install.
We found after the final install that the mssqlsystemresource files in the M:Microsoft SQL ServerMSSQL.1MSSQLData
directory were in fact updated after each install with a new timestamp, and that all files in C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn matched on both file size and timestamp. The log-shipping security issue we were looking to fix also appeared to be resolved by the last update.
On Server A, which was running SP1 (Build 9.0.2047), we installed the same SP2 package as we had on Server B with no issue. We rebooted and then tried to apply the same Hotfix KB933097 (Build 9.0.3152) that had been applied successfully on Server B and found to our surprise that the same errors were being generated here as well. We continued to apply the rest of the hotfixes so that both servers matched software updates. Comparing the above directories showed that files seemed to have been updated, even though database services appeared to be not installed.
It looks like we now need Cumulative Update 5 hotfix package in order to deal with WMI alerting issues, but I'm afraid to apply it until we have a known resolution for the past errors.
Since this issue was supposed to be resolved by SP2, I'm not sure why these post-SP2 hotfixes should fail. It seems to me to be an issue of the directory location of the system files which is in question.
I can post the hotfix log files as well, if anyone is interested in seeing them.
Any help would be greatly appreciated. As well, does anyone have any idea when SP3 is scheduled to come out? I really don't like applying hotfixes which are usually untested for general purposes, and it seems Microsoft is delaying this in favour of releasing SQL 2008.
I created a SSIS package to extract data from a flat file source and load them into a table in a data base. After I created the package i checked it in to source control(perforce).
But the problem is once a month new flat source file comes and data should be updated. Once the new flat file comes, is there anyway that SSIS package can identify the path of the flat file and execute the package automatically? In Flat file source only the data will be changed. Not location or data type or anything. Can i use parameters to do that?
i searched and all i found is questions, not answers.
maybe it's a silly question, but i really can't find any documention / posts about this.
i have a scheduled job in sqlagent that executes a SSIS package that runs every minute. As a result, my application log in eventviewer gets filled very quickly.
i tried using "/REPORTING E" option with no luck.
i tried enabling logging on the package, and then select only the OnErro Event, no luck.
AFAIK I don't think so. Let me know if possible and how.
I'm talking about a SSIS package which owns a Execute DTS 2000 Package Task and from there it calls a DTS 2000. Programatically, from our VB .Net front-end app we're seeing only SSIS events (when validate and execute methods are called) and any kind of information is provided from RCW proxy (I suppose that internally it gonna be created in order to send messages between managed and unmanaged code).
When a task inside our DTS 2000 fails we're awaring by means a "generic message" such this:
Error: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user. at DTS.PackageClass.Execute() at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread()
From material I have read I should be able to reference columns in a datarelation by
Parent.ColumnName Child.ColumnName
The code below is Ok until I use the Child reference
Dim tbl0102reltn As New DataRelation("tbl012tbl02", tbl01Cols, tbl02Cols)
dataset01.Relations.Add(tbl012tbl02reltn)
'=== Add the new Forecast Column to table01 (The display table) Dim FcstTotVol As DataColumn = New DataColumn("FcstTotVol") 'declaring a column named Name FcstTotVol.DataType = System.Type.GetType("System.Int16") FcstTotVol.Expression = "Child(tbl012tbl02reltn).TotVol"
The last line throws an error
"cannot interpret token Child() at position 1"
If I replace the last Line as
FcstTotVol.Expression = "tbl0102reltn.Childtable.Columns(10)" i receive the error
"The expression contains undefined function call tbl0102reltn.Childtable.Columns()."
I am unable to find away to feed the expression required for the new column.
Hello experts. I have been searching for anything about this but found very little. What are the events logged in SQL Server Error Logs aside from Successful/Failed Login, Backup/Restore/Recover database and, start/init sql server? Can we configure this to log other events, like CREATE or DBCC events for example? If so, how? Thanks a lot.
