Connection Managers don't work once I change the Protection Level - encryption

Using SSIS 2008 currently, my package ProtectionLevel is set to: EncryptSensitiveWithUserKey.
I recently tried changing it to DontSaveSensitive
but my package fails after making that change with the following error:
SSIS package "ImportModerators.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC020801C at Data Flow Task, Add new Moderators [422]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "StagingDatabase" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "Add new Moderators" (422) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Data Flow Task: There were errors during task validation.
SSIS package "ImportModerators.dtsx" finished: Success.
If I've changed the protection level (and I'm the one who created the package), shouldn't this package be able to run?

If the connection is not windows authentication, you will need to setup package configurations for each connection so SSIS has somewhere to pull credentials from.

Related

Why does this Visual Studio warning / problem occur?

I get this error whenever I want to access the database that I have created and it shows this message
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed
Does anyone know how to solve this?

Failed due to a lacking or broken API call inherited from UI Automation in UFT

I get following error message (after a long wait) in UFT when try to set value of an input field in a Java based desktop application. I checked in Object Repository and it shows correct field in UI of application.
Failed due to a lacking or broken API call inherited

pool::dbPool returning Pool object not able to notify connection observer

I'm trying to use the pool package for the first time. I've created a Pool object with the code below.
pool <- dbPool(drv=odbc::odbc(),
dbname="dbname",
driver="SQL Server",
server="server",
uid="user.name",
pwd="password",
port=1433)
This results in the following warning message.
# warning messages from top-level task callback '1'
# Warning message:
# Could not notify connection observer. trying to get slot "info" from an object (class "Pool") that is not an S4 object
> class(pool)
# [1] "Pool" "R6"
Since this is my first time using pool I'm unsure if it is safe to proceed despite the warning. Can someone with more experience with pool share some insight into the possible repercussions and/or causes of this warning message?
I'm able to successfully get data using the Pool object as my connection.
table <- DBI::SQL("TableName")
query <- glue::glue_sql("select * from {table}", .con=pool)
dbGetQuery(pool, query) ## returns expected data
I'm using the development version of pool but I've also tried using the latest version on CRAN, both have resulted in the aforementioned warning message.
I also had this error message. A thread on the RStudio forums suggests to update the DBI, odbc and pool packages to the latest versions, which worked for me
https://community.rstudio.com/t/how-to-use-dbpool-with-rodbc/5609/3

Golden gate replication table's trigger failed to call package

Receiving "ORA-06508: PL/SQL: could not find program unit being called" when a trigger on a replication table tries to call a package.
The same code was working fine at first and it is failing later.
And the package is valid and we have all grants in place. Also we tried dropping and recreating both the trigger and the package including the grants. Still facing same error.
​
Try to trace the behavior in Oracle Database. You can use the 10046 trace to list all SQL commands that GoldenGate is issuing. Extract the commands from the trace and run them manually on the target database. You should be able to see the same error and be able to track the source of it.

Using Standard WF activities to access a web service - how to set 'expected namespace'?

I am attempting to connect to a .Net 1.0 web service using standard activities in WF 4.0.
I am using the SendandReceiveReplyFactory - the send portion seems to be working - however the ReceiveReplyForSend is for some reason expecting a tempuri.org namespace response rather than the www.thermo.com/informatics/xmlns/limswebservice namespace.
Could anyone instruct me on how I can cause the activity to expect the correct NS.
Thanks in advance for your help.
All the best,
DJ
Error Message:
Workflow Console: Starting Workflow... Send Done Workflow
3fdc4d67-dcac-4092-b34b-9c347acdfe22 Terminated. Exception:
System.ServiceModel.CommunicationException Error in deserializing body
of reply message for operation 'Process'. OperationFormatter
encountered an invalid Message body. Expected to find node type
'Element' with name 'ProcessResponse' and namespace
'http://tempuri.org/'. Found node type 'Element' with name
'ProcessResponse' and namespace
'http://www.thermo.com/informatics/xmlns/limswebservice' Workflow
Console: Workflow Completed
The answer is to specify the namespace in the ServiceContractName Property of the 'Send' Activity using the following syntax '{http://someserver.org/test/}FileService ' in my case '{http://www.thermo.com/informatics/xmlns/limswebservice}LIMSSoap' . The syntax was sensitive to the trailing slash so a little trial and error was needed.
Many thanks to the contributors to WF4 - How to consume external web service? for the answer.

Resources