SSI problem

Hello!
Alright here's the situation:
1.) I can see my includes in Dreamweaver CS3 in Display mode
2.) I can see the includes also during "preview in browser"
3.) I've uploaded all files to my host
Yet.... the includes doesn't display online in my site.
Here's the site:
http://www.elemental-sayings-quotes.com/index.html
As you can see in the code there are 6 includes:






None of them loads...
I suspect there's some problem with my .htaccess file or the host preference, but it's really weird because yesterday it worked well.
What I did was to re-upload all files after having created a new folder structure, and deleted all other files, probably including the .htaccess file.
Don't know how to fix it.
What's the .htaccess file supposed to look like? Any other possible root cause to why it doesn't work now?
Thanks a lot!

ESQ CB wrote:
Oh gosh,
I asked my host for support and they went in and updated my .htaccess file so now it looks like this:
AddType text/x-server-parsed-html .html
According to this document, that is correct: Look right at the bottom of the page: Why .shtml? Can't I use .html?
http://www.wdvl.com/Authoring/SSI/Intro/
As your pages are saved with the html extension, that is needed so the server can parse the includes on html pages, otherwise you would need to change the file extension to .shtml
As to why the site is trying to download the page instead of letting us view it, I have no idea - I'm only writing this to try and keep you calm :-) while you wait for the host to get back to you. I'm not experienced enough at this type of programming to give you a definitive answer, and I'd hate to guess and it all goes wrong.
As long as the tech guys know that you have html pages that need to server includes with a .shtml extension, then they should be able to set it up. There could possibly be a problem with the include extension name, maybe the server needs it to be html or ssi or even inc. Make sure you tell them what extension you are using and ask that is the correct way to name them... and hopefully they'll sort you out.

Similar Messages

SSIS problem - Script Component - The value is too large to fit in the column data area of the buffer

I am trying to run a task in a package, however there is a problem come out, see any one meet this before ?

/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
using System.IO;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
    public override void PreExecute()
        base.PreExecute();
          Add your code here for preprocessing or remove if not needed
    public override void PostExecute()
        base.PostExecute();
          Add your code here for postprocessing or remove if not needed
          You can set read/write variables here, for example:
          Variables.MyIntVar = 100
    public override void Input0_ProcessInputRow(Input0Buffer Row)
        string temp = GetString(Row.FlatFileSourceErrorOutputColumn.GetBlobData(0, (int)(Row.FlatFileSourceErrorOutputColumn.Length - 2)));
        string[] cols = temp.ToString().Split(';');
        var r = Row;
        //try {
            r.Column1 = cols[0].ToString();
            r.Column2 = cols[1].ToString();
            r.Column3 = cols[2].ToString();
            r.Column4 = cols[3].ToString();
            r.Column5 = cols[4].ToString();
            r.Column6 = cols[5].ToString();
            r.Column7 = cols[6].ToString();
            r.Column8 = cols[7].ToString();
            r.Column9 = cols[8].ToString();
            r.Column10 = cols[9].ToString();
            r.Column11 = cols[10].ToString().Substring(0, 2);
            r.Column12 = cols[11].ToString();
            r.Column13 = cols[12].ToString();
            r.Column14 = cols[13].ToString();
            r.Column15 = cols[14].ToString();
            r.Column16 = cols[15].ToString();
            r.Column17 = cols[16].ToString();
            r.Column18 = cols[17].ToString();
            r.Column19 = cols[18].ToString();
            r.Column20 = cols[19].ToString();
            r.Column21 = cols[20].ToString();
            r.Column22 = cols[21].ToString();
            r.Column23 = decimal.Parse(String.IsNullOrEmpty(cols[22].ToString()) ? "0.00" : cols[22].ToString());
            r.Column24 = decimal.Parse(String.IsNullOrEmpty(cols[23].ToString()) ? "0.00" : cols[23].ToString());
            r.Column25 = cols[24].ToString();
            r.Column26 = cols[25].ToString();
            r.Column27 = cols[26].ToString();
            r.Column28 = decimal.Parse(String.IsNullOrEmpty(cols[27].ToString()) ? "0.00" : cols[27].ToString());
            r.Column29 = cols[28].ToString();
            r.Column30 = cols[29].ToString();
            r.Column31 = cols[30].ToString();
            r.Column32 = cols[31].ToString();
            r.Column33 = cols[32].ToString();
            r.Column34 = cols[33].ToString();
            r.Column35 = decimal.Parse(String.IsNullOrEmpty(cols[34].ToString()) ? "0.00" : cols[34].ToString());
            r.Column36 = cols[35].ToString();
            r.Column37 = cols[36].ToString();
            r.Column38 = cols[37].ToString();
            r.Column39 = decimal.Parse(String.IsNullOrEmpty(cols[38].ToString()) ? "0.00" : cols[38].ToString());
            r.Column40 = decimal.Parse(String.IsNullOrEmpty(cols[39].ToString()) ? "0.00" : cols[39].ToString());
            r.Column41 = decimal.Parse(String.IsNullOrEmpty(cols[40].ToString()) ? "0.00" : cols[40].ToString());
            r.Column43 = decimal.Parse(String.IsNullOrEmpty(cols[42].ToString()) ? "0.00" : cols[42].ToString());
            r.Column44 = cols[43].ToString();
            r.Column45 = decimal.Parse(String.IsNullOrEmpty(cols[44].ToString()) ? "0.00" : cols[44].ToString());
            r.Column46 = decimal.Parse(String.IsNullOrEmpty(cols[45].ToString()) ? "0.00" : cols[45].ToString());
            r.Column47 = decimal.Parse(String.IsNullOrEmpty(cols[46].ToString()) ? "0.00" : cols[46].ToString());
            r.Column56 = decimal.Parse(String.IsNullOrEmpty(cols[55].ToString()) ? "0.00" : cols[55].ToString());
            r.Column57 = cols[56].ToString();
            r.Column58 = cols[57].ToString();
            r.Column59 = cols[58].ToString();
            r.DirectRowToOutput0();
        //}catch(Exception ex)
        //    //using (StreamWriter sw = new StreamWriter("C:\\Users\\i290\\Documents\\temp_err.txt", (File.Exists("C:\\Users\\i290\\Documents\\temp_err.txt") ? true : false)))
        //        sw.Write(temp.ToString() + ex.Message.ToString() + "\r\n");
        //IDTSComponentMetaData100 mdt;
    static string GetString(byte[] bytes)
        System.Text.Encoding enc = System.Text.Encoding.ASCII;
        return enc.GetString(bytes);

SSI problem with Tomcat 4.0.6

Hello,
I have recently configured SSI on my Tomcat 4.0.6, as described in the Tomcat 4.1 documentation. I was unable to find it in the 4.0 documentation and I got a bit suspicious. How is the support for SSI in 4.0?
Anyhow, this is what i can and can't do:
This works fins (example from Apache SSI Tutorial)

This doesn't work (example from Java Servlet Programming, O'Reilly)
<SERVLET CODE=SSITester>
<PARAM NAME=startAt VALUE=10>
</SERVLET>
I would guess that I the SSIServlet uses the subclasses to org.apache.catalina.util.ssi.SsiMediator, but which should i use and how?
/padbaq

I don't think the servlet tag is supported anymore.

Sql Server High availability failover trigger

Hello,
We are implementing sql server 2012 availability groups (AG). Our secondary databases are not accessible in order to save licenses.
We have a lot of issues concerning monitoring, backup and SSIS. They all come down to the fact that they want basic information from the secondary, that is not accessible. We are implementing SSIS, which is supported on AG, but the SSISDB is encrypted.
Backup problem
The secondary instance does not know anything about the backups made in the primary instance. After a failover differential backups fail.
SSIS problem:
There is a blog (http://blogs.msdn.com/b/mattm/archive/2012/09/19/ssis-with-alwayson.aspx) that suggest to make a job that checks whether the status has changed from secondary to primary. If so, you can decrypt and encrypt again.
This job has to be executed every minute. Which is way too much effort for an event that happens once in a while. There are a few other problems with this solution. The phrase "use ssisdb" has to be included in the a job step. And the
jobstep fails. The secondary is not accessible.
Monitoring problems:
We use Microsoft tooling for monitoring: SCOM. Scom does not recognize a non readable secondary and tries to login continuously.
There are a few solutions that I can think of:
- sql server build in failover trigger
- Special status of secondary database.
Failover trigger:
We would like a build-in failover trigger, in stead of a time based job, that starts a few standard maintenance actions if only at the time (or directly after) a failover has occurred. Because now our HA cluster is not really high available until :
- SSISDB works and is accessible after failover
- Backup information is synchronised
- SCOM monitoring skips the secondary database (scom produces loads of login failures)
Does anyone have any suggestion how to fix this?

No built in trigger can achieve your requirement.

Problem Running SSIS Package with a SQL Server Agent

SQL Server: SQL Server 2012
VS: Visual Studio 2012
Hello,
      I have been having a problem running SSIS packages by using a SQL Server Agent job. I first created these SSIS packages in a separate IS project in Visual Studio. I imported the packages to the Integration Services (Package
Store) instance on my SQL Server and tried to create a job that would run them from there.
      At first I read around about needing a proxy account to allow the agent/packages to access the file system since these packages are importing data from a flat file in the SQL database. So I created a temporary admin user to
use as the user for the agent. I did this by going to Services.msc on the server and linked the account the agent's "logon as". Then arose another issue where I am getting an error about using the incorrect type for my connection managers.
The connection manager "TestFile" is an incorrect type. The type required is "OLEDB". The type available to the component is "FLATFILE". Source: Data Flow Task Flat File Destination [2]     Description:
Cannot open the datafile "O:\*****\Success.txt"
I am not sure what this even means as I am getting this error even with a test package that doesn't do anything with the database. I have just two flat file connection managers in this test project one for grabbing the source file and one for
creating the new test file.
I am not sure what to do.
Thanks in advance,
Matt

I accidently created two posts. The newest one has the details.
I did not mean to.
SQL Server: SQL Server 2012
VS: Visual Studio 2012
Hello,
      I have been having a problem running SSIS packages by using a SQL Server Agent job. I first created these SSIS packages in a separate IS project in Visual Studio. I imported the packages to the Integration Services (Package
Store) instance on my SQL Server and tried to create a job that would run them from there.
      At first I read around about needing a proxy account to allow the agent/packages to access the file system since these packages are importing data from a flat file in the SQL database. So I created a temporary admin user to
use as the user for the agent. I did this by going to Services.msc on the server and linked the account the agent's "logon as". Then arose another issue where I am getting an error about using the incorrect type for my connection managers.
The connection manager "TestFile" is an incorrect type. The type required is "OLEDB". The type available to the component is "FLATFILE". Source: Data Flow Task Flat File Destination [2]     Description:
Cannot open the datafile "O:\*****\Success.txt"
I am not sure what this even means as I am getting this error even with a test package that doesn't do anything with the database. I have just two flat file connection managers in this test project one for grabbing the source file and one for
creating the new test file.
I am not sure what to do.
Thanks in advance,
Matt

SSIS 2014 - Parametrize connection gives a problem of Null password

Hi guys,
I was using the option of Parameterize on the connections I have under
Connection Manager. I had no problem with the SQL Server Native client connections, however on Oracle Provider for OLE DB, as soon as I parameterize the connection string, all OLEDB sources that use this connection turn on the red X error mark.
It seems the password is not saved anymore because it gives an authentication failure saying it has a null password.
I'm using EncryptSensitiveWithPassword in package.
Any ideas on this? Thank you

Hi Pedro,
If I understand correctly, you get the error message that”The expression will not be evaluated because it contains sensitive parameter variable” when you are using package parameter or project parameter which with Sensitive = True in expression.
Based on my research, this issue is caused by design. For more information, please refer to the following feedbacks:
https://connect.microsoft.com/SQLServer/feedback/details/750997/changing-a-parameter-to-sensitive-should-trigger-alert-in-ssis
https://connect.microsoft.com/SQLServer/feedback/details/816052/ssis-evaluating-expressions-using-project-parameters-set-as-sensitive
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Template-based ssi causing problems

I'm working on a small site that has a sidebar listing news features, which the client needs to edit. The sidebar list appears throughout the site so I set it up as an SSI in the base template. The editable items in the sidebar are repeating elements with some internal structure, so I based the SSI on a template to make the items easy for the client to edit in Contribute.
There's no problem editing the template-based SSI itself in Contribute, and there's no problem editing the pages in Contribute when the SSI is not included. The problem arises when I try to edit any of the pages in Contribute once the SSI is included; they no longer function properly. Several pages have editable regions that are also comprised of editable, repeating list items, but the buttons in Contribute for adding, deleting, and moving these repeating regions on those pages no longer do anything once the SSI is incorporated into the page.
If I change the SSI so it is not template based -- make it just raw html -- the problem goes away. (Unless I can find a solution, I'll have to go this route although it makes it harder for the client to edit the contents of the SSI.) So the problem isn't the SSI; it's when the SSI is based on a template.
There are no <body> or <head> tags in the template-based SSI; just the sidebar <ul> snippet with editable, repeating regions. I've tried changing the SSI extension to .shtml, .inc, .htm, etc. to no avail.
I can think of many scenarios where an SSI needs to be editable and, at the same time, has enough structure that I would want to base it on a template to facilitate editing in Contribute. But a template-based SSI seems to make Contribute choke.
I'd appreciate any help on this.

Have you renamed the file with an *.shtm(l) extension?
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com
- Template Triage!
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
http://www.macromedia.com/support/search/
- Macromedia (MM) Technotes
==================
"tnuaga" <[email protected]> wrote in
message
news:e9oks7$2kd$[email protected]..
>I have a template based on the halo_left_nav css file,
into which - in the
> editable region - I have embedded an ssi file. Although
the include file
> shows
> up in Dreamweaver, it does not show up in the browser.
Any sagacious
> advice?
> I'm using DW MX (yeah - old and no longer supported) on
a Mac. (I just
> received approval to upgrade to v8.0, but I have a
deadline of 8-1-06 to
> complete a rather daunting project and am a little
insecure about
> switching at
> the moment.)
>
> I have another issue with the same template which I will
post separately
> in
> order to keep my oranges out of my apple box.
>

Oracle Provider for OLE DB on Vista SSIS Unicode Problem

I wrote a few SSIS packages on my XP computer using the 10.2.0.2 OLE DB Provider which work fine.
Now I'm trying to migrate to a Vista computer... I loaded the Vista certified 10.2.0.3 client and can connect to Oracle databases no problem.
The problem is when openning the packages that work fine. For some reason its now seeing the non-unicode columns from the Oracle database as unicode and can't validate the OLE DB Data Sources.
Any ideas?

I thought I'd let everyone know that I had resolved the problem. It came down to the order of the installations, and possibly what I had been installing.
Initially I had only run the 10.2.0.3 Client Install for Vista. Everything worked fine except for the unicode issue. This last time, after removing everything Oracle, I installed the ODT with ODAC 10.2.0.2.21 into its own new home "ODACHome1". Then I ran the 10.2.0.3 Client Install for Vista and chose the same home as the ODAC install (the installer complained but I continued). I then performed a "Custom" install and only choose to upgrade the Oracle Net to 10.2.0.3 from the 10.2.0.1 that wouldn't work under vista. Thats it, thats all I chose.
The installer completed successfully and now everything is working fine. SSIS is recognizing them as it did on XP. Also, I was able to repeat this and get it to break again...

SSIS connection problem -- inexplicable red box

I've developed a lengthy SSIS package to migrate data from an old database to a new SQL Server 2008
database. My workstation is on the same domain as our dev SQL server. The SSIS package has several connection managers. When I'm connecting to the databases in the dev environment, everything works fine.
As a final stage in testing the package, I'm trying to change the connection managers of the source databases to our production environment. Production is in a different, untrusted domain. I'm using SQL Server authentication. When I change a connection manager
from the dev server to the production server, I click the Test Connection button and see "Test connection succeeded." I go to an OLE DB source object that uses this connection manager. I click the "Preview..." button and it successfully
displays sample data. But when I try to execute the step that contains this OLE DB source object, I get these error messages and the box turns red:
Error: There were errors during task validation.
[SSIS.Pipeline] Error: One or more component failed validation.
[SSIS.Pipeline] Error: component [OLE DB source object name] (329) failed validation and returned error code 0xC020801C.
[PRIMS Commands [329]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager [Connection Manager name] failed with error code 0xC0202009. There may be error messages
posted before this with more information on why the AcquireConnection method call failed.
For the provider on the connection manager, I've tried SQL Server Native Client 10.0, SQL Server Native Client 11.0, and Microsoft OLE DB Provider for SQL Server. All of them give me the same failure.
I'd really appreciate any suggestions. Thanks.
Addendum. In my troubleshooting, I've turned off Run64BitRuntime, and the connections work. Why would 64-bit runtime work when connecting to the dev server but not the production server?
This isn't really a good workaround for my problem because the package uses a fuzzy lookup transformation, which only runs in 64 bit mode. I might be able to separate that out into another package, but that would be inconvenient at best.

Hi AlanYoung001,
The issue is rather odd. Could you try the ADO NET Source and use the .Net Providers\SqlClient Data Provider and check the issue again? In addition, if it is possible, run this package on your Dev server to see if the package works. Besides, the error message
should not be complete, could you post the complete error message to see if we can find more clues?
Regards,
Mike Yin
If you have any feedback on our support, please click here
Mike Yin
TechNet Community Support

SSI PARAM problem

I am getting null value when I call req.getParameter(arg). I saw couple of
          postings on this problem. Can someone post the solution?
          Thanks
          -Bala
          email: [email protected]


http://www.weblogic.com/docs51/classdocs/API_servlet.html#ssi
          Cheers
          mbg
          In article <8h3e0a$kop$[email protected]>, [email protected]
          says...
          > I am getting null value when I call req.getParameter(arg). I saw couple of
          > postings on this problem. Can someone post the solution?
          >
          > Thanks
          > -Bala
          > email: [email protected]
          >
          >
          >
          ==================================================
          NewsGroup Rant
          ==================================================
          Rant 1.
          The less info you provide about your problem means
          the less we can help you. Try to look at the
          problem from an external perspective and provide
          all the data necessary to put your problem in
          perspective.

Data Flow Task problems after installing SQL Server 2014 SSIS

I can't create any Data Flow Task. Once I create (tested and working) Connection (it doesn't
matter if it is Excel, Flat File or other) and try to use it with a Source Assistant, I get the following messages:
===================================
The component could not be added to the Data Flow task.
Could not initialize the component. There is a potential problem in the ProvideComponentProperties method. (Microsoft Visual Studio)
===================================
Error at Data Flow Task [SSIS.Pipeline]: Component ", clsid {C4D48377-EFD6-4C95-9A0B-049219453431}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.
Error at Data Flow Task [ [1]]: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
===================================
Exception from HRESULT: 0xC0048021 (Microsoft.SqlServer.DTSPipelineWrap)
Program Location:
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()
at Microsoft.DataTransformationServices.Design.PipelineTaskDesigner.AddNewComponent(String clsid, Boolean throwOnError, Boolean select)
===================================
The component could not be added to the Data Flow task.
Could not initialize the component. There is a potential problem in the ProvideComponentProperties method. (Microsoft Visual Studio)
The component could not be added to the Data Flow task.
Could not initialize the component. There is a potential problem in the ProvideComponentProperties method. (Microsoft Visual Studio)
===================================
Error at Data Flow Task [SSIS.Pipeline]: Component ", clsid {C4D48377-EFD6-4C95-9A0B-049219453431}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.
Error at Data Flow Task [ [1]]: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
Error at Data Flow Task [SSIS.Pipeline]: Component ", clsid {C4D48377-EFD6-4C95-9A0B-049219453431}" could not be created and returned error code 0x80070005 "Access is denied.". Make sure that the component is registered correctly.
Error at Data Flow Task [ [1]]: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "".
===================================
Exception from HRESULT: 0xC0048021 (Microsoft.SqlServer.DTSPipelineWrap)
Program Location:
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()
at Microsoft.DataTransformationServices.Design.PipelineTaskDesigner.AddNewComponent(String clsid, Boolean throwOnError, Boolean select)
Exception from HRESULT: 0xC0048021 (Microsoft.SqlServer.DTSPipelineWrap)
at Microsoft.SqlServer.Dts.Pipeline.Wrapper.CManagedComponentWrapperClass.ProvideComponentProperties()
at Microsoft.DataTransformationServices.Design.PipelineTaskDesigner.AddNewComponent(String clsid, Boolean throwOnError, Boolean select)

See examples here:
http://www.sqlusa.com/bestpractices/ssis-wizard/
What is your data source?
What is your data destination?
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

Having problems opening an SSIS solution file

I have to make some changes to an SSIS package that was last modified in 2009 by a person who has left the company.
I am having problems finding a version of Visual Studio that will open the SLN file. I do not know how the package was originally maintained.
Yesterday, I was able to right-click on the SLN file and select 'version selector', that opened the solution in VS 2005 without me having to select a program. I made some changes and saved, rebuilt and ran the package.
Today when I try to open the SLN the same way, it displays the screen with the various VS version icons on it, but no VS 2005 listed!
The bottom line, is I now cannot open the solution with any version of Visual Studio. If I can find another SLN file that will open, can I copy the modified dtsx file to that solution so all my work is not wasted? It took me 3 days work to modify this package.
Can someone please help, my deadline for this task is TODAY.
Here is the message I get if opening with VS 2005:
Here is the message I get if opening with VS 2010:
Here is the SLN file (It looks like it got modified because I'm pretty sure yesterday it said VS 2005 at the top):
Microsoft Visual Studio Solution File, Format Version 11.00
# Visual Studio 2010
Project("{D183A3D8-5FD8-494B-B014-37F57B35E655}") = "HPAddress_ExportData", "HPAddress_ExportData.dtproj", "{7EB5909F-6836-4B23-A121-9F623FB1C932}"
EndProject
Global
GlobalSection(SolutionConfigurationPlatforms) = preSolution
  Development|Default = Development|Default
EndGlobalSection
GlobalSection(ProjectConfigurationPlatforms) = postSolution
  {7EB5909F-6836-4B23-A121-9F623FB1C932}.Development|Default.ActiveCfg = Development
  {7EB5909F-6836-4B23-A121-9F623FB1C932}.Development|Default.Build.0 = Development
EndGlobalSection
GlobalSection(SolutionProperties) = preSolution
  HideSolutionNode = FALSE
EndGlobalSection
EndGlobal

Hi AllTheGoodNamesWereTaken,
Based on my test, if we open a solution file with lower version in a higher version Visual Studio (VS), it will use Visual Studio Conversion Wizard to update the solution to current version of VS. Then the solution file will also change to current version
of VS. If we open a solution file with higher version in a lower version Visual Studio (VS), it causes an error that “The version number in the package is not valid. The version number cannot be greater than current version number”. And the solution file still
use the original version of VS.
So it seems that the original version of solution file is lower than or equal to VS 2010. Since the VS is backwards compatible, we should use a higher version of VS (VS2010 and later) to open the solution file. Notice that we need open the solution file,
not the project file.
Besides, we can also create a new SSIS project in a higher version of VS, then add the packages with “Add existing package” option from File System. Reference:
https://www.blackbaud.com/files/support/guides/infinitydevguide/Subsystems/bbdw-developer-help/content/tkaddpackagefromexisting.htm
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Conn problem SQl Server 64 Bit to Oracle 32 bit using SSIS packages

Hi,
I am facing the problem with connection SQL(64 bit) to Oracle(32 bit).
Please give me the solution/guide in right direction.
Environment is
S1-----> DBServer : 64 bit Windows Server 2003 Enterprise Edition, 64 Bit SQl Server EE, 64 Bit Oracle 10g Client
S2----->.AppServer :32 bit Windows Server 2003 Enterprise Edition, IIS, 32 Bit Oracle 10g Client & Server DB
I have doubt like....
1.Can i install 32 bit oracle also at (S1) 64 bit SQL Server(SSIS)
or only 64 bit oracle?
2.Running command line for SSIS packages at S1
i am unable to connect S1---->S2 using SSIS packages?
How can i solve this problem? pl give steps for going right direction.
Thanks
JOHN
[email protected]

Fabio D'Alfonso wrote:
Hi,
I was setting up VMware vCenter 4.1 (probably the only well known and largely used product with this lethal mix) and needed to setup an ODBC access to Oracle on the 32 bit side of Windows to setup the Update Manager server component, which is still a 32 bit application)
The problem with Oracle configuration is that in no way I found a 32 bit ODBC registered driver after the setup (of the 32 bit client and the 64 database server). I tried some third party driver for oracle (e.g. easysoft).They registered in the 32 bit ODBC manager but they never got a successful connection.
Also if this vCenter requirement is questionable (more questionable considering that the setup of this 32 component is not allowed on a 32 separate OS, not because it is separate but because is a 32 bit OS) I would get it working.
Could suggest a way to get this working?
Thanks
Fabio D'AlfonsoWhen you install the Oracle client software on Windows (which is necessary to support ODBC, as the Oracle ODBC driver sits on top of the native client software) the ODBC driver is NOT installed by default. You have to go back and do a "custom" install and select the "Windows components".

SSIS - "Insufficient Connection information was supplied" problem

Hello,
I have connection problem with my SSIS package. Setup is as follows:
Package includes 150+ dataflows that pump data from Informix tables to MS SQL Server tables
Setup of each dataflow consists of ADO.NET source (newest driver version 4.10 for Windows x64) and OLEDB destination pointing to SQL Server 2012
Data components are linked to connection managers, which are parametrised. Connection string is set from one parameter and password from another (sensitive) parameter
All dataflows are in one big container to achieve maximal parallelism (parameter MaxConcurrentExecutables = -1) and highest performance.
Most of the time, it works correctly. But ca. 1 out of 10 runs, I get following error:
Error: ADO NET Source has
failed to acquire the connection {3DC4A80D-EC92-4551-
B607-B0D2E2652F43} with the following error message:
"ERROR [HY000] [Informix .NET provider][-11302]
Insufficient Connection information was supplied".
When I then re-run the package with identical configuration, it runs fine. Informix support told me, that from their point
of view everything seems OK. They tried to simulate this error and ran test with ca. 50 dataflows (but with password supplied in connection string) and it ran correctly.
So they assume, that problem lies within SSIS, which sometimes simply fails to supply password to ADO.NET source
and it fails. Do you have any suggestion where might be problem?
Thanks for cooperation

Hi duffmansk,
According to your description, it supposed to be the performance issue. I suggest you can run the packages in more network traffic time, increase the hardware and virtual memory of your computer to test again. For adding virtual memory, please go to System
Properties -> Advance -> Performance Options -> Advance -> Virtual Memory, increase the size for Virtual Memory.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

VariableScope problem with sequence containers (SSIS 2012)

Hi,
a co-worker of mine experienced a problem with variable scopes in SSIS 2012 when copying a sequence container.
This is what he tried to do:
Create a sequence container with a data flow task and a script component
Add variable "a" with scope set to the sequence container
Add "a" to ReadOnlyVariables in the script component and assign it to a variable within PreExecute() in the script
Copy the sequence container (with DFT and SC)
Rename (or remove and add new - doesn't matter) variable "b" with scope set to the new sequence container
Change variable in ReadOnlyVariables of copied SC to "b", change it in the script as well
Now when executing the package, one of the sequence containers will always fail. Interestingly enough, it is not always the same but switches seemingly randomly. It doesn't matter if the script is written in C# or VB.
The following error is thrown:
Exception from HRESULT: 0xC0010009
   at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSVariables100.get_Item(Object Index)
   at SC_f8fa68ce667a42d2b4b154c26831db5f.Variables.get_VarForCopySeqC()
   at SC_f8fa68ce667a42d2b4b154c26831db5f.ScriptMain.PreExecute()
   at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.PreExecute()
In this case, VarForCopySeqC is the variable used in the copied sequence container, but the failing one is the original sequence container.
Does anyone have an idea how to resolve this? Thanks in advance for anyone helping us out here!
Regards,
Thorsten H.

If the variable is scoped to the Sequence Container then you could leave it as is in the new Sequence Container too. Why rename it to "b" ?
Granular scoping makes the package debugging and maintenance a lot more difficult because you have to bring the component in focus to see its scoped variables. It is easier to have package-scoped variables IMHO.
- Aalamjeet Rangi | (Blog)

SSI problem

Similar Messages

Maybe you are looking for