Create datastore Type R/3

Hi
I'm trying to create a datastore with the type R/3.
But I get the error/warning
WARNING: Cannot establish database connection ' The transport mechanism being used to transfer data is <Shared Directory>. This required a pth to be specified for both the server side and the client side directories' (BODI-1111348)
Do you want to conitnue anyway
If I continue it does not work. Any ideas and help will be appreciated.
Thanks in advance
Edited by: Louis De Gouveia on Mar 4, 2010 1:01 PM

Did u check all the confiugurations.
Looks like the error is looking for an
application shared directory information
https://wiki.sdn.sap.com/wiki/display/BOBJ/shared_directorytransportmethod
Take a look at this wiki

Similar Messages

Create datastore for complex comma seperated file

I am trying to integrate a comma seperated file to an Oracle database. The files contain multiple record types each of which have different number of fields and a different order of datatypes within those fields. The order that the records types are listed in the file determines the relationship between them, e.g.
The file could contained the following record types in the order shown:
Segment
Fixture
Position
Position
Segment
Segment
Fixture
Position
Position
Position
So there is a parent-child relationship between the Segement record and the Fixture record that immediately follows it and similarly the position records are child records to the Fixture record.
How can I create datastores that represents this relationship when there is no parent field in the child record types?

I dont think ODI would be able to help you much with Out of the box functionality. You will need to modify the LKM (SQLLDR) to achieve this.
The following entry illustrates the logic:
[http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:7526680049479]
Hope that helps

Problem in Tax Exexpiton for Newly created Wage type

Dear Gurus,
I Have tried to create a New Wage type for Allowance with Exemption IT582 created Amount. In pay roll results the IT582 Exemption amount is coming. In Wage type /132 Monthly Exemptions it says the Entire Amount which it created for the Particular wage type.
Example:
Newly created wage type 1010 : 10,000
Exemption Created : 6000
Payroll Results:
/132 : showing 10,000+800 Conveyance
MCAX : 6000 - Custom Allowance
MCMX :6000 - Custom Allowance.
By the above result the Gross value reduced to -10,000.
Please suggest me to complete this process.
Thanks in Advanc.
Anbu.

Hi Anbu,
I am lil bit confused abt the explanation u had given. anyway i will explain the configuration n step u need to perform-
configure a wage type in V_T7INA9 and V_T7INT9 view first.
maintain the amount, which employee has submitted as claim.
then pass the value in infotype 8 or 14 or 15 through the same wage type u have configure.
now minimum of 3(entry in V-T7INT9, infotype 8 or 15 or 14 and entry maintained in infotype 582) will b the exemption amount.
Regards,
Praveen
Edited by: Praveen-Sapping in SAP World on Mar 26, 2009 10:11 PM

Want to create a type at runtime

Hi all ,
I am trying to create a type at run time within my scheme by making use of a table loop.
[code]
Report test_data.
data :
    llv_imp type table of RSIMP,
    gt_imp_par type string occurs 0.
Field-Symbols :
    <fs_imp_par> like RSIMP,
    <fs_struct> type string.
Form inst_par_types
Changing
lv_imp like llv_imp
lt_imp_par like gt_imp_par.
Data :
    lv_str(72) type c ,
    lv_line     type I ,
    lv_delim    type C value ',' .
Describe table lv_imp lines lv_line.
Loop at lv_imp assigning <fs_imp_par>.
    if sy-tabix = lv_line.
       lv_delim = '.'.
    endif.
      if <fs_imp_par>-default is not initial.
        concatenate <fs_imp_par>-parameter 'TYPE' <fs_imp_par>-typ
        'VALUE' <fs_imp_par>-default lv_delim into
        lv_str SEPARATED BY space.
      else.
        concatenate <fs_imp_par>-parameter 'TYPE' <fs_imp_par>-typ
        lv_delim into lv_str SEPARATED BY space.
      endif.
append lv_str to lt_imp_par.
clear lv_str.
endloop.
Types :
        Begin of l_tabname ,
           <b><i>{T$lt_imp_par$$$&lt_imp_par&$$}</i></b>
        End of l_tabname.
EndForm.
[/code]
But when i instantiate this scheme it dumps as the highlighted line creates 2 different definitions of same variable lt_imp_par (1 as var & another one as table).
What shall I do to get the solution?

Please do not post multiple treads for the same question.
Please refer to other thread.
want to create an internal table at runtime
Regards,
Rich Heilman

Getting error while creating condition type in SPRO

Hi ,
can somebdy tell me why i am getting the following error while creating condition type in SPRO
No valid change license available for message /sapcnd/
and also while rule determination using condition type we are getting the following error.
system error:system cannot read the structure for table
reg
venkat

Hi Venkat,
Do you have the error number code!?
Regards,
Michel Bohn

Hello Guru's Error MSG while creating Material Type HERS

Hello Guru's,
While creating material type HERS the system is showing the following error *"The field orign acceptance is defined as a required field; it does't contain an entry'"* will any one give solution.
even i have filled orign field in info record also still it is giving same error message, will anyone give solution.
full points for the answer.

hers is for the mpn
note the techincal name of that field and then go to oms9 and there make that filed for the filed selection key of hers as optional
u can get the field selcton key of hers from the tcode oms2

Error when trying to create a types jar from a web service WSDL

Hi,
I generated a WSDL from a web service. When I try to generate a types jar from that WSDL in another project, I get an error:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
com.bea.workshop.webservices.servicecontrol.ui.except.TypeGenerationFailedException: Buildfile: C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml
Trying to override old definition of task wsgen
build:
build-types:
clean-types:
[echo] Deleting types directory c:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474
[echo] Deleting types jar C:\eclipsews\AAATest\WebContent\WEB-INF\lib\CaregiverEBillingMasterServiceServiceTypes_xmlbeans_apache.jar
[mkdir] Created dir: C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474
generate-src-code:
[echo] Generating types of family xmlbeans_apache from WSDL at file:/C:/eclipsews/AAATest/src/test/CaregiverEBillingMasterServiceService.wsdl, all services. Outputting to c:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474
[typesGen] Generating complex Java types for schema types in WSDL file:/C:/eclipsews/AAATest/src/test/CaregiverEBillingMasterServiceService.wsdl. Outputting to C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474 ...
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfTreatmentDetailItem@http://org/abc/claims/caregiver/ebilling/services
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfDocumentTypeAutoPayWrapper_literal@java:org.abc.claims.caregiver.ebilling.services.util
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfJavaLangint_literal@java:org.abc.claims.caregiver.ebilling.services
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfDocumentSubmissionHierarchy@http://org/abc/claims/caregiver/ebilling/services
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfMessageCode@http://org/abc/claims/caregiver/ebilling/services
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfFeeCodeType@http://org/abc/claims/caregiver/ebilling/services
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfBatchMessage@http://org/abc/claims/caregiver/ebilling/services
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfArrayOfJavaLangstring_literal@java:org.abc.claims.caregiver.ebilling.services.util
[typesGen] [WARNING] Generating array which is non-compliant with JaxRPC 1.1 for XML name: t=ArrayOfJavaLangstring_literal@java:org.abc.claims.caregiver.ebilling.services.util
compile-src-code:
[echo] Compiling source files from c:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474 to c:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474
[javac] Compiling 298 source files to C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474
[javac] ----------
[javac] 1. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\com\abc\claims\caregiver\ebilling\FeeCodeDocument.java (at line 51)
[javac]      public static com.abc.claims.caregiver.ebilling.FeeCodeDocument parse(java.lang.String xmlAsString) throws org.apache.xmlbeans.XmlException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 2. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\com\abc\claims\caregiver\ebilling\FeeCodeDocument.java (at line 54)
[javac]      public static com.abc.claims.caregiver.ebilling.FeeCodeDocument parse(java.lang.String xmlAsString, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 3. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\com\abc\claims\caregiver\ebilling\FeeCodeDocument.java (at line 58)
[javac]      public static com.abc.claims.caregiver.ebilling.FeeCodeDocument parse(java.io.File file) throws org.apache.xmlbeans.XmlException, java.io.IOException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 4. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\com\abc\claims\caregiver\ebilling\FeeCodeDocument.java (at line 61)
[javac]      public static com.abc.claims.caregiver.ebilling.FeeCodeDocument parse(java.io.File file, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 5. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\com\abc\claims\caregiver\ebilling\FeeCodeDocument.java (at line 64)
[javac]      public static com.abc.claims.caregiver.ebilling.FeeCodeDocument parse(java.net.URL u) throws org.apache.xmlbeans.XmlException, java.io.IOException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 6. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\com\abc\claims\caregiver\ebilling\FeeCodeDocument.java (at line 67)
[javac]      public static com.abc.claims.caregiver.ebilling.FeeCodeDocument parse(java.net.URL u, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, java.io.IOException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
=== snipped here due to huge file size ===
[javac] 2680. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\org\xfa\schema\xfaData\x10\SignatureDocument.java (at line 99)
[javac]      public static org.xfa.schema.xfaData.x10.SignatureDocument parse(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 2681. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\org\xfa\schema\xfaData\x10\SignatureDocument.java (at line 103)
[javac]      public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 2682. ERROR in C:\development\wlwBuild\XCaregiverEBillingMasterServiceService1297810259474\org\xfa\schema\xfaData\x10\SignatureDocument.java (at line 107)
[javac]      public static org.apache.xmlbeans.xml.stream.XMLInputStream newValidatingXMLInputStream(org.apache.xmlbeans.xml.stream.XMLInputStream xis, org.apache.xmlbeans.XmlOptions options) throws org.apache.xmlbeans.XmlException, org.apache.xmlbeans.xml.stream.XMLStreamException {
[javac]      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[javac] No exception of type XmlException can be thrown; an exception type must be a subclass of Throwable
[javac] ----------
[javac] 2682 problems (2682 errors)
BUILD FAILED
C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml:73: The following error occurred while executing this line:
C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml:107: The following error occurred while executing this line:
C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml:181: Compile failed; see the compiler error output for details.
Total time: 17 seconds
     at com.bea.workshop.webservices.servicecontrol.ui.util.TypesGenerationScript.run(TypesGenerationScript.java:197)
     at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Caused by: org.eclipse.core.runtime.CoreException: C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml:73: The following error occurred while executing this line:
C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml:107: The following error occurred while executing this line:
C:\eclipsews\.metadata\com.bea.workshop.webservices.servicecontrol.ui\build-dir\build.xml:181: Compile failed; see the compiler error output for details.
     at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:451)
     at org.eclipse.ant.core.AntRunner.run(AntRunner.java:383)
     at com.bea.workshop.webservices.servicecontrol.ui.util.TypesGenerationScript.run(TypesGenerationScript.java:185)
     ... 1 more
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I was previously able to generate a types jar just fine from the web service's WSDL. Recently, I made some changes to the web service. Apparently, these changes to the web service now cause the WSDL to be unparseable when trying to generate types jars.
Any ideas?

The WSDL is generated from my web service. I made heavy revisions to my web service which, in turn, affected the resultant WSDL. The changes I made to my web service were almost exclusively related to object substitution. For example, prior to the change I was referencing object A from my web service; after the change, I was referencing object B. The objects that I'm referring to are XMLBeans, if that matters. I can't really describe it more than that without actually showing you the WSDL.
I would post the WSDL file here to allow you to try to create a types jar out of it, but the WSDL exceeds the 30000 character limit for this field. There is no way for me to attach the WSDL to this post.

Error while creating data type

Hi
I am creating data type for the scenario from File to IDOC
Namespace urn:xiworkshop:groupxx:legacy is not defined in the software component version NEWPRODUCT , 100 of sap Object Message Type Vendor | urn:xiworkshop:groupxx:legacy references the inactive object Data Type Vendor | urn:xiworkshop:groupxx:legacy
Please help me

Hi;
First activate your namespace and then create the data type.
Namespace + default datatypes should be activated together.
Then your data type
Mudit

Create "Object" Type based on columns of a table

Hi Experts
is it possible to create an Object Type based on columns of a table?
for example the syntax for creation of type is
CREATE OR REPLACE TYPE temp_t
AS OBJECT (ID number, code number)
can we create a type that is based on columns of an existing table? so that we donot have to write down all the column names in each type as i have to create types based on 100 and above tables :-s
Please help me out here!
Best Regards

You cannot do that Zia, check below code:
SQL> create or replace type temp_t as object(object_name all_objects.object_name%TYPE);
2 /
Warning: Type created with compilation errors.
SQL> sho err
Errors for TYPE TEMP_T:
LINE/COL ERROR
0/0 PL/SQL: Compilation unit analysis terminated
1/35 PLS-00201: identifier 'ALL_OBJECTS.OBJECT_NAME' must be declared

Bapi for creating message type in a sales order

Hi, I am involved in a IS-MAM project for an italian company.
I need to create or add a message output type in a sales order in a complex batch program. I thought to use a bapi technicality; in particular BAPI_ADMGMTSO_CHANGE in order to change the document.
How can I create message type in the order? Can I use the same bapi or I need of an other one?
thanks in advance for your help
Lucia

Can you please provide more information...

Import XSD to create Data type in Design

hi,
I know that we can import XSD in Design and create data type,my question is:
1. Can i import an XSD thats been created in message mapping and use that to create my data type in design.
(or)
2.Should i have to write an XSD on my own and then import it to create my data type, and is there any standard format to write it.

Hello Prashanth,
For your first question: i don't know exactly what you mean that the the xsd you create in the data mapping steps. So can you explain it in details?
For your 2nd question: Sure you can write your own XSD to create a data type. And i will give you an example xsd file format. Then you can import it in the XSD tab view.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/hansteel" targetNamespace="http://sap.com/xi/XI/hansteel">
     <xsd:complexType name="CustomerInfo">
          <xsd:annotation>
               <xsd:appinfo source="http://sap.com/xi/TextID">
               a6c26c80000f11dac45e00096b1669b3
               </xsd:appinfo>
          </xsd:annotation>
          <xsd:sequence>
               <xsd:element name="ID">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         dfe699c0e7bc11d9c736d51c0a0013e1
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="NAME">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         dfe82060e7bc11d9b2efd51c0a0013e1
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="35" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="CUSTTYPE">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         dfe82061e7bc11d9c193d51c0a0013e1
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="4" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="POSTCODE">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         e93039a0e7bc11d9c7c6d51c0a0013e1
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="10" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
               <xsd:element name="CITY">
                    <xsd:annotation>
                         <xsd:appinfo source="http://sap.com/xi/TextID">
                         f0122850e7bc11d99189d51c0a0013e1
                         </xsd:appinfo>
                    </xsd:annotation>
                    <xsd:simpleType>
                         <xsd:restriction base="xsd:string">
                              <xsd:length value="35" />
                         </xsd:restriction>
                    </xsd:simpleType>
               </xsd:element>
          </xsd:sequence>
     </xsd:complexType>
</xsd:schema>
Hope this will be helpful.
Eric Ma

Why should we create data type

Hi all,
I have a basic question!
why do we create data type and then wrap it as message type?
why dont we directly create a message type and use that ?
please give the answers. Thanks in Advance.

Hi Seshu,
Please go through below links, you get answer
message type and datatype
Difference between Data type and Message type - Process Integration - SCN Wiki
Regards,
Krupa

Problem in creating data type

hi..
i've problem in creating data type in xi after importing idoc from the R/3 sender
plz tell me the basic steps for creating data type in the receiver i.e xi.....
thanks in advance

Hi,
You don't need to create a data type after importing the IDOC.
Idoc itself acts as message type and message interface.
check this for creating a data type..
http://help.sap.com/saphelp_nw70/helpdata/en/2d/c0633c3a892251e10000000a114084/frameset.htm
Thanks,
Vijaya.

Unable to create the type with the name 'MSORA'. (Microsoft.SqlServer.ManagedDTS)

I am attempting to use the Integration Services Import Project Wizard within Microsoft Visual Studio and am getting this error
Unable to create the type with the name 'MSORA'. (Microsoft.SqlServer.ManagedDTS)
upon Import.
Can anyone shed some light for me on this cryptique error message?
Thanks for your review and am hopeful for a reply.

If you have the SSIS and SSDT (BIDS) installed then
I believe the DTS assemblies got derigistered, a typical outcome of corrupted software, so a full re-install would be the best option. VS +SQL Server + more
Otherwise, as a quick fix try to
reference the SSIS assemblies, like Microsoft.SQLServer.ManagedDTS.dll + more.
They are by default in C:\Program Files\Microsoft SQL Server\<number>\SDK\Assemblies.
Arthur
MyBlog
Twitter

Unable to create the type with the name 'ODATA'

On a test server with VS 2012 and SQL 2012 installed, I have created an SSIS project in project deployment mode. In the packages of the project I use the Odata source for SSIS. The packages run fine in VS 2012. But when I deploy the package to the Integration
Services catalog on the same server as where I am running VS 2012 I get a deployment error:
‘Failed to deploy project. For more information, query the operation_messages view for the operation identifier '25084'. (Microsoft SQL Server, Error: 27203)'
When I read this message from the SSISDB database, I see the problem with ODATA.
use SSISDB
go
select * from catalog.operation_messages where operation_id = 25084
--Failed to deploy the project. Fix the problems and try again later.:Unable to create the type with the name 'ODATA'.
As I said: the packages with the Odata run without error when tested from within VS2012 on the SAME server. When I deploy the project from Visual Studio I get the error.
For completeness: I have also tried deployment from VS2012 to another server where the SSIS Odata source has bene deployed. Also to no avail.
Jan D'Hondt - SQL server BI development

The next possiblity for me was to convert the project to Package deployment and see what the result I get. I have converted my project with package connections from project deployment to Package deployment. Then I deployed the package on the server in MSDB
catalog from SSIS. I.e. I connect with SSMS to Integration Services as an administrator and under the MSDB folder I added a new folder for my package. I then imported the dtsx into the mdsb package store. The Import worked. Still from within SSMS and connected
to the Integration Services, i right-clicked on the package in the MSDB store and selected 'Run package'. In the Execute Package dialog window, I clicked on 'Execute' and the package actually ran. The Odata connector was opened, it read the data and imported
into my database.
This experience made me realize what the real culprit was: The OData connector is a 32-bit connector in SQL Server 2012.
To prove this: with SSMS I connected to the SQL database server and in the Integration services catalog, i right-clicked on the package that was deployed in Project deployment mode, then selected 'Execute...'. In the execute dialog windo in the 'Advanced'
tab I checked 32-bit runtime. And the package ran.
To wrap it all up:
The Project deployment will work, but not with the Odata source as project connection. The Odata connection must be defined in each package as a package connection.
Run the deployed packages in 32-bit mode on the server
Jan D'Hondt - SQL server BI development

Create datastore Type R/3

Similar Messages

Maybe you are looking for