Script tasks not pre-compiling all of a sudden

I've been building and running script tasks for years without issue. Then all of sudden last week Visual Studio starts showing the "Task is configured to pre-compile the script, but binary code is not found" error anytime I open a script -- even I make no changes. If I copy the dtsx package to another machine, the script compiles fine and I can see the binary data in the raw .dtx file -- so I know the code is correct.

I can also reproduce the error simply by adding a new script task, going into "Design Script", make no changes to the default code (which is basically one line: Dts.TaskResult = Dts.Results.Success) and simply press "OK" on the Script Task Editor.

I've been trying to find some VS setting somewhere that might stop the script IDE from producing the binary code, but I can't. It doesn't seem to be project setting, because all my SSIS projects are now suffering this problem on my main dev box.

Anyone experience this?

Did you just recently apply a bunch of Microsoft patches?

Did you see this thread? http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1855810&SiteID=1

Script task

Hi,

I am new in SSIS development. In the script task of the Control Flow, how to use my custom classes (that use SMO and DTS for building a package and are written in C##?). If not the Script Task then which tool I have to use?

Natali Rozin wrote:

Hi,

I am new in SSIS development. In the script task of the Control Flow, how to use my custom classes (that use SMO and DTS for building a package and are written in C##?). If not the Script Task then which tool I have to use?

If you have compiled them into assemblies then you can reference them.

You should read this though:

VSA requires DLLs to be in the Microsoft.Net folder (but not all the time)
(http://blogs.conchango.com/jamiethomson/archive/2005/11/02/2341.aspx)

-Jamie

|||

thank you very much Jamie.

Did you put your DDLs into the root of the Microsoft.Net folder? Through "Add Reference", I cannot find my DDLs I just put into C:\WINDOWS\Microsoft.NET\Framework

|||

Natali Rozin wrote:

thank you very much Jamie.

Did you put your DDLs into the root of the Microsoft.Net folder? Through "Add Reference", I cannot find my DDLs I just put into C:\WINDOWS\Microsoft.NET\Framework

Natali,

You should put it into the appropriate .Net Framework version folder (I always just pick the highest). e.g.:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

My apologies, the post I linked to above does not explain this does it?

-Jamie

|||

Thank you - all are working!

The problem was I put mine into C:\WINDOWS\Microsoft.NET\Framework\v3.0 and do not have VS SDK yet.

In C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 works well!

thanks again

Screen output vs. print output, SSRS 2000

Hi,
I'm building a report for a client (in SSRS 2000), where I am
experiencing the fact that the output on the screen (ie, what is
rendered by Report Manager) is very different from the print output (or
export output, for that matter).
I am using a list, with a couple of tables (with fixed size) embedded
in it. While shown on screen, the page breaks are (as far as I can
tell) randomly inserted, no matter what I set as properties for Page
Break, Keep Together, etc. The output while exporting to (for example)
PDF is great, and exactly as I want it.
Has anyone experienced a similar problem? If so, have you solved it,
and how?
Thanks,
Jeroen Buisman
InfoReports Business Intelligence B.V.I have read in training material that the output to the screen (HTML) does
not have fixed page bounderies but goes until it hits the end of a group set
for a page break at the end of the group. HTML is not a "page oriented"
output format, while PDF is. This has been my experience.
<jeroen.buisman@.gmail.com> wrote in message
news:1141808034.990107.276690@.i39g2000cwa.googlegroups.com...
> Hi,
> I'm building a report for a client (in SSRS 2000), where I am
> experiencing the fact that the output on the screen (ie, what is
> rendered by Report Manager) is very different from the print output (or
> export output, for that matter).
> I am using a list, with a couple of tables (with fixed size) embedded
> in it. While shown on screen, the page breaks are (as far as I can
> tell) randomly inserted, no matter what I set as properties for Page
> Break, Keep Together, etc. The output while exporting to (for example)
> PDF is great, and exactly as I want it.
> Has anyone experienced a similar problem? If so, have you solved it,
> and how?
> Thanks,
> Jeroen Buisman
> InfoReports Business Intelligence B.V.
>|||Hi,
if you dont mention the margin propert for the report layout then this
problem will come up for the HTML print and not for PDF. so you have to
mention the margin hight,width,top,left in the rdl for the html activex
control to get that property otherwise it will get the default property which
makes the report ugly. You can fix temp by changing the margin property to
low in HTML print active control while viewing.
Bava
"jeroen.buisman@.gmail.com" wrote:
> Hi,
> I'm building a report for a client (in SSRS 2000), where I am
> experiencing the fact that the output on the screen (ie, what is
> rendered by Report Manager) is very different from the print output (or
> export output, for that matter).
> I am using a list, with a couple of tables (with fixed size) embedded
> in it. While shown on screen, the page breaks are (as far as I can
> tell) randomly inserted, no matter what I set as properties for Page
> Break, Keep Together, etc. The output while exporting to (for example)
> PDF is great, and exactly as I want it.
> Has anyone experienced a similar problem? If so, have you solved it,
> and how?
> Thanks,
> Jeroen Buisman
> InfoReports Business Intelligence B.V.
>|||Bava
can you explain this more in detail
Thx|||True, but the page breaks are occurring erraticaly. If it were so that
the HTML page break would only occur after the first group which has
the "Page Break at End" (or something like that) set, the break would
occur on exactly the same spot, right? So my guess is that that's not
the case. Will check it though, when I visit my client again tomorrow.
Thx,
Jeroen|||Hi Bava,
You mean that for the Report object, I should set explicit margins? If
so, that's something I always do with my reports. If that's not wat you
mean: could you please clarify what you mean with "changing the margin
property to low in HTML print active control"?
Thx,
Jeroen|||Hi,
The report rdl has the element like
<Report>
<RightMargin>0.2in</RightMargin>
<LeftMargin>0.2in</LeftMargin>
<TopMargin>0.2in</TopMargin>
</Report>
you have to set explicit for the report otherwise it will take the default
of .5in i think.
The default of 0.5in will not be good for some reports in HTML print control
that is avilable in report manager near the Export link.
You can see the value of the report margin set during the print control
preview mode. You can adjust the margin in this print control preview mode
but it will not be saved to the report or in the setting.
Bava
"Jeroen Buisman" wrote:
> Hi Bava,
> You mean that for the Report object, I should set explicit margins? If
> so, that's something I always do with my reports. If that's not wat you
> mean: could you please clarify what you mean with "changing the margin
> property to low in HTML print active control"?
> Thx,
> Jeroen
>|||Ow ok... however, the problem I'm having is not with printing, in fact,
printing is what goes well. The rendering on screen doesn't work as it
should.