In my SSIS package, I have a script task in addition to other tasks. When I put a debug point within the script task and run the package( on the whole), ideally, it is supposed to hit the breakpoint. but it now only opens a new VS window, shuts it after few seconds and a green tick is displayed over the task.
I tried setting the the Run64BitRuntime flag to false and also editted and saved the script task again. The issue persists. Any pointers on this ?
I have VS 2010 BI and the machine is 64 bit Windows Server R2
Yes, break points do work in script task. But if that was a script component, then it wouldn't have worked. Any way, if you have a script task, the reason it might not be working is that it may be using the 64 bit runtime. Try running it in the 32 bit runtime.
Also, make sure that the place at which you have hit the breakpoint is actually reachable. If there are some case statements or if conditions, possibilities are that the line of code is actually missed.
Surely debug is allowed for script task. Couple of point to remember
1. Run the package in 32 bit
2.wherever u set up debug pointer... code should be rechable
3.debug only allowed for 1 script task. Ssis engine can only show you debugging only for 1 script task. If you have 2 script task then ssis will open debugging only for first script task.. suggesting you put de bugging only to one script task
I ran into this as well and found the script task had been set to optimize code even for debug mode.
See more detail here
Related
I have a bad situation I'm trying to work through and would appreciate your help. We have a legacy .NET application that initiates a stored procedure call that is exceeding the default command timeout threshold. I know how to change the command timeout threshold in code (that's easy) - the problem is that we don't have the source code for this legacy application (trust me, no one's more upset about this than I).
We're working on optimizing the Stored Procedure, but we're facing some blockers. Namely, the database which the Stored Procedure runs against is a vendor database and they've said they can't add some indexes that would help. We're also facing an issue where the vendor's database has grown dramatically over the last few years and the size appears to be contributing to the problem.
Previous to our optimization efforts, the stored procedure was taking minutes to complete. We've now got it down to about 36 seconds, but we're not sure if we can get it below the default command timeout of 30 seconds.
I've read that there's no way to change the command timeout in the connection string, but I was wondering if any of you fabulous people had any ideas on how to change the command timeout outside of code.
Thanks!
You can use ildasm to alter what will get executed directly in the .net dll. e.g. see top answer in:
dotnet dll decompile and change the code
There's a bit of a learning curve, but it is possible.
Or could try something like DnSpy https://github.com/dnSpy/dnSpy , which looks promising.
Some discussion of DnSpy at:
Modify Compiled .Net Exe
I have some trouble keeping alive a background process when launched by TFS.
Usually I use a batch that launch a java server (new window), as long as I keep this window open it works properly.
C:\Users\TFSService\mbs-iot-sdk\osgi\bin\vms\jdk\server.bat
In order to make my process automatic, I include this in TFS. In the step I call a batch that contains the following:
cd C:\Users\TFSService\mbs-iot-sdk\osgi\bin\vms\jdk // necessary to find the batch
start C:\Users\TFSService\mbs-iot-sdk\osgi\bin\vms\jdk\server.bat
In my task manager, I can see in background tasks that java is launched (no new window is opened), exactly as it behaves when launching directly the batch. But after a few seconds, when TFS switches to the next step, it stops.
Then the next step carries on but fails as it requires the server to be launched.
Is there a particular way of doing it in TFS ?
thank you
Alexandre
It's suggest to launch the .bat file from a relative path not directly use cd to hard code the path.
Also recommend you to use Run Batch File task not Run Command Line task to launch the .bat file.
According to your description, seems you are using a run command line task in your build pipeline. Then run the command under the working directory c:\Build_work\5\s, the command cd to C:\Users\TFSService\mbs-iot-sdk\osgi\bin\vms\jdk\ on the build agent, find the server.bat, run the server.bat.
First check if the .bat file is located at the path you are specifying on the build agent. Not sure if the bat file have to run under C:\Users\TFSService\mbs-iot-sdk\osgi\bin\vms\jdk\, guess you are also hard code the path in your server.bat file. Suggest you change all the path to relative path, you could use some built-in variable in TFS.
As for your workaround in comment, seems you want to chain builds in TFS. The official docs literally say "not yet" and have a uservoice in planed. However you could use some workaround, such as create or use other's customize extension (use rest api) to call another build. Detail ways please refer huserben's answer in this question: How to chain builds in TFS 2015?
Note sure you have to go deep into this area for your original issue. Just add some related info in case you are interested or need.
Well,
Just in case someone else goes through the same kind of issue, I found a workaround:
I wish to mix different command line steps, some of them launching Python scripts:
I have one step for launching the server that is required for my testing tool, one step for my testing tool and one Python step for differential testing
I realized that I could embed everything in a Python script.
It can handle server launching process in a separate window (with subprocess), launch my Python part and launch another process for my validation tool.
I have to test the whole chain but, at least, I solved my problem of launching a background process and detach it from TFS
I am trying to pull data from a Salesforce API account using Pentaho/Kettle Spoon. I am able to establish a connection on Pentaho with this account. I am also able to get fields from specific modules. However, when I try and "Preview rows" (even with a small number of rows), the "Operation in Progress" window comes up and never completes the task. When I try and cancel the job, Pentaho hangs and I have to force quit it.
I am running Fedora 21. Any input is greatly appreciated.
Thanks!
This works for me:
Since upgrading to Fedora 22 Spoon (the client tool of PDI) was not working properly anymore. Although I could start Spoon properly and create transformations etc, once I wanted to execute a transformation or sometimes even when trying to open settings, nothing was working and the terminal window showed several (SWT:20352): GLib-CRITICAL error messages. In a nutshell, Spoon was rendered useless.
Here is how to solve this:
Go to the Eclipse Download Page and download the latest 64bit verion of Eclipse IDE for Java EE Developers. Note: There is a separate download area for SWT; however, for Linux there is no 64 bit version available. The only way to get one is to build it yourself. So I just went the easier way and downloaded Eclipse instead.
Unzip the file and search for swt. A search result will show a few files, but the ones interesting for us are (your version number might be different): org.eclipse.swt_3.103.2.v20150203-1313.jar and org.eclipse.swt.gtk.linux.x86_64_3.103.2.v20150203-1351.jar.
Copy the first one of these files into <PDI_HOME>/libswt/linux/x86 and the second into <PDI_HOME>/libswt/linux/x86_64.
oth folders still have the original jar files in them. Rename them to swt-jar-old (Note: no extension, so that they are not picked up).
Start Spoon. There will be a few error messages shown, but so far Spoon is working way better for me than before.
FONT: http://diethardsteiner.github.io/pdi/2015/06/07/Fixing-PDI-GLib-CRITICAL.html
i'm running Ubuntu 14.04, i5,6gb RAM, got same trouble..
when i check, the load in proccessor is 100%, evertime i try showing the content or other thing in pentaho, the Operation in progress is show up, and never end..
How to solve, check your access to file/connection in your database,unrecognize file,field,etc. after this resolve, my proccessor run normal, and i could run / execute the transformation.
I have created an SSIS package in SQL Server. In Data Flow I have added a Script Task in which there is a break point. When I started debugging the package, it hit the break point and everything went fine.
Then I made some changes in code in Script Task and now break point won't hit. I have tried everything but no luck. I have even did the following as per Microsoft but same issue.
http://blogs.msdn.com/b/farukcelik/archive/2010/03/17/why-the-breakpoints-that-i-set-in-my-script-task-not-script-component-in-the-data-flow-never-hits.aspx
In the package it self it shows that Red circle on Script Task which means there is a break point but it never hits. When I debug the package and it reaches the Script Task, then looks like it is trying to open the editor and hit the break point but then it automatically closes and continues with the code. What am I doing wrong?
I have a situation where there are two different users using the same machine, debugging the same package. (SQL Server 2012)
When a breakpoint is set in a script task, for the one, when the breakpoint is hit, execution pauses appropriately, and VSS is opened, at the right point in the code, paused, ready to step through.
With the other user, visual studio opens, but the code is not in view. Although the code can be opened, and the breakpoint is visible, the debugger does not appear to be attached and he can't step through.
To be clear, this is the same machine, same project, just two different users, and we're unable to identify any major differences between the two users (both are local admin).
The project settings are for interactive mode = true, 64 bit = false.
Anyone have any idea what could cause this?
I would resolve this issue by not sharing the same source files amongst developers. Each developer would have their own copy of the project, synchronized via source control e.g. TFS, VSS. TFS in particular brings a host of other features and can be used online for free.