Issue with SSIS SystemAvailabletask

Hi BPC & SSIS Experts,
We are working on SAP BPC 5.1 MS version. We have the below requirment.
" We have to take the BPC Appset (Application Set) offline for maintenance activities and at the same time a notification has to be sent to all the users". The said functionality should be achieved using SSIS package.
The steps we followed.
1) We logged into SSIS and crated a new project
2) from the tool box we dragged the systemavailabletask to the control flow.
3) we tried editing the properties of this task
4) when we edit and provide the information as, Description, Appset, Server details as(hostname/userid) and check thesystem setting option as Unavaialable to the user and click ok then we get the below error despite of the fact that all the entries provided are correct.
"Invalid UserID or the server is not respondin properly LateGetObject Variable or With Block variable not set."
Request you to please share your experties and provide a relevent resolution.
Any help in this regard will be much appreciated.
Regards,
Mohd Mujahd Zaffar
9966235863

Hi,
The user id should be mentioned as hostname\userid and not hostname/userid. This id should have the admin access to the appset. Try this and let me know if you see issues.
Hope this helps.
Badrish

Similar Messages

  • Issues with SSIS in named instance SQL 2014

    I have a SSIS job that runs without any issues with native mode. But for named instance, I get these errors:
    Any suggestions?
    Failed to decrypt protected XML node
    "DTS:Password" with error 0x8009000B "Key not valid for use in specified state.
    You may not be authorized to access this
    information. This error occurs when there is a cryptographic error. Verify that the correct key is available.  End Error  Error: 2015-04-22 15:20:01.67     Code: 0xC0016016    
    Source: xxx Description: Failed to decrypt protected XML node "OraPassword" with error 0x8009000B
    "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a
    cryptographic error. Verify that the correct key is available.  End Error  Error: 2015-04-22 15:20:02.22     Code:
    0x000002BD     Source: xxx  Connection manager "yyy"     Description:Oracle Home not found.  End Error  Error: 2015-04-22
    15:20:02.22     Code: 0x0000020F    Source: mmm[96]    
    Description: The AcquireConnection method call to the connection manager yyy failed with error code 0x80004005.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.  End Error 
    Thanks

    Hi LaxUdas,
    If I understand correctly, the package is developed with Protection Level set as "EncryptSensitiveWithUserKey". When you execute the package via a SQL Agent Job in a Named Instance, the account that job step using is not the user that create the
    package. So it cannot be able to connect to the Oracle DB with invalid connection string.
    This behavior is by design. In an Integration Services package, the following information is defined as sensitive:
    The password part of a connection string.
    The task-generated XML nodes that are tagged as sensitive.
    Any variable that is marked as sensitive.
    EncryptSensitiveWithUserKey uses a key that is based on the current user profile to encrypt only the values of sensitive properties in the package. Only the same user who uses the same profile can load the package. If a different user opens the package,
    the sensitive information is replaced with blanks and the current user must provide new values for the sensitive data.
    To work around this issue, please refer to the following suggestions:
    Change the SSIS Package ProtectionLevel property to EncryptSensitiveWithPassword. This setting uses a password for encryption. To open the package in SSIS Designer (SSDT), the user must provide the package password.
    Change the Named Instance SQL Agent Service account to the user that create the package, like your Default Instance.
    Use SSIS Package configuration files to store sensitive information, and then store these configuration files in a secured folder. You can then change the ProtectionLevel property to DontSaveSensitive so that the package is not encrypted and does not try
    to save secrets to the package. When you run the SSIS package, the required information is loaded from the configuration file. Make sure that the configuration files are adequately protected if they contain sensitive information.
    The following two documents are for your references:
    https://msdn.microsoft.com/en-us/library/ms141747.aspx
    https://support.microsoft.com/en-us/kb/918760
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Issue with SSIS Custom Components - 64 bit SQL 2012

    Hello All,
    Our SSIS packages built on SQL 2008 R2 make use of some custom components. These custom components are installed as part of an MSI. The dll's are copied over to the Windows/assemble [GAC Folder] and also to the Program Files(x86)/SQL Server/110/DTS/* folder.
    The installation does not copy the dll's to the 64 bit program files folder.
    X:\Program Files\Microsoft SQL Server\110\DTS
    These packages are executed via SQL Agent jobs on a 64 bit SQL server and there does not seem be any issue.
    Now we are upgrading our servers to SQL 2012 and we have a new installer for the custom components as well. The new custom components use .NET Framework 4.0 and when installed the dll files get copied over to the Ms.NET 32 bit runtime GAC folder and also
    to the SQL Server DTS Folder in x86. The upgraded packages work only when we set the runtime mode to 32 bit. The packages successfully executes within the 32 bit dtexec utility, but when we try to run the same package using a 64 bit dtexec utility the
    process errors out with a component failed to load message. The package moves data between two SQL Server instances.
    The custom components have always been built for 32 bit runtime. I can run a older package through the dtexec utility (from the 64 bit folder in program files) and it does work without any issues. After the upgrade the package will only execute on
    a 32 bit utility. can someone help me understand this issue?
    Regards, Dinesh

    Thank you Arthur.
    i think we got the answer as well, as the .NET framework 3.0 installer copied the files over to the C:\windows assembly the dtexec utility [32 bit/64 bit] was able to load the components.
    Now with the new installer the files are copied to specific runtime gac folders as Arthur has mentioned. The 64  bit  utility does not find the dlls in the GAC whereas the 32 bit version will find them.
    Regards, Dinesh

  • Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

    Hello everyone.
    We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
    packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
    Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
    MCP

    Hi. Yes...
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="SQLISServer" /> 
      <EventID Qualifiers="0">1</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" /> 
      <EventRecordID>469950</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>abtru1a11.oneabbott.com</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
    exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
    runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
    at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
    Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
    Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
    behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
    at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data> 
      </EventData>
      </Event>
    MCP

  • Log In Issues with SSIS

    I installed SSIS two moths after installing SQL Server 2014. I granted permissions  to users per MSDN in Dcomcnfg.exe and rebooted SSMS and SSIS.
    I am able to log on via my client without any issues; however, the other user cannot even see the instance via her client. The only way she can log on is to remote into server, right click administrator and it works.
    She has permissions for everything other than sysadmin, which I don't want to grant to her.
    Any ideas why she wouldn't even see the instance from her client when given permissions?
    Thank you!

    To grant access to the Integration Services service
    1. Run Dcomcnfg.exe. Dcomcnfg.exe provides a user interface for modifying certain settings in the registry.
    2. In the Component Services dialog, expand the Component Services > Computers > My Computer > DCOM Config node.
    3. Right-click Microsoft SQL Server Integration Services 11.0, and then click Properties.
    4. On the Security tab, click Edit in the Launch and Activation Permissions area.
    5. Add users and assign appropriate permissions, and then click Ok.
    6. Repeat steps 4 - 5 for Access Permissions.
    7. Restart SQL Server Management Studio.
    8. Restart the Integration Services Service.
    Thanks

  • Strange issue with rights of account, used by SSIS (Foreach Loop Container does not return file names without Admin rights on server)

    Hello everyone.
    Faced very strange issue with account, which is used to run SSIS package.
    The specific package uses Foreach Loop Container to retrieve file names within the specified folder, and put them into Import file task.
    The package is set up to run under specific service account. This service account is given all permissions (Full control) to the folder where source files reside.
    So the issue is: SSIS package fails to execute this task (Foreach Loop Container and then Import), and shows that no files are found in the directory (although files ARE there).
    Once we're adding the service account into local Administrators group on the SQL Server, it works! Removing - does not work again. We cannot leave the service account as SQL server's admin as it's prohibited by our IT policies, and is just a bad practice.
    Any ideas, please? 
    MCP

    Here's the real log output:
    Date 16.04.2014 12:47:09
    Log Job History (RU-BW: Update)
    Step ID 1
    Server Server
    Job Name RU-BW: Update
    Step Name bw_import_cust_master_data
    Duration 00:00:02
    Sql Severity 0
    Sql Message ID 0
    Operator Emailed
    Operator Net sent
    Operator Paged
    Retries Attempted 0
    Message
    Executed as user: service_account Microsoft (R) SQL Server Execute Package Utility  Version 10.50.4286.0 for 64-bit  Copyright (C) Microsoft Corporation 2010. All rights reserved.    Started:  12:47:09  Error: 2014-04-16 12:47:11.45
        Code: 0xC0202070     Source: bw_import_cust_master_data Connection manager "Input"     Description: The file name property is not valid. The file name is a device or contains invalid characters.  End Error  Error:
    2014-04-16 12:47:11.47     Code: 0xC0202070     Source: bw_import_cust_master_data Connection manager "Input"     Description: The file name property is not valid. The file name is a device or contains invalid characters.  End
    Error  Error: 2014-04-16 12:47:11.48     Code: 0xC0202070     Source: bw_import_cust_master_data Connection manager "Input"     Description: The file name property is not valid. The file name is a device or contains invalid
    characters.  End Error  Error: 2014-04-16 12:47:11.48     Code: 0xC020207E     Source: Import file Flat File Source [1]     Description: The file name is not valid. The file name is a device or contains invalid characters.
     End Error  Error: 2014-04-16 12:47:11.48     Code: 0xC004701A     Source: Import file SSIS.Pipeline     Description: component "Flat File Source" (1) failed the pre-execute phase and returned error code 0xC020207E.
     End Error  DTExec: The package execution returned DTSER_FAILURE (1).  Started:  12:47:09  Finished: 12:47:11  Elapsed:  2.324 seconds.  The package execution failed.  The step failed.
    MCP

  • Issue with Temp tables in SSIS 2012 with RetainSameConnection=true

    Hello,
    We have few packages written in 2008 and are being upgraded to 2012. Our package mostly uses temp tables during the process.  During initial migration, we faced issue with handling temp table in the OLE Db destination provider and found a solution for
    the same under 
    usage of Temp tables in SSIS 2012
    Most of our packages execute fine now. 
    we came across a different issue recently. For one of our package, which merges 3 feeds into a temp table and then executes a stored procedure for processing, the package fails intermittently.
    Below are properties of SSIS and its components, which you might be interested
    * Retainsameconnection for the OLE Db connection manager set to True
    * properties of OLEDB Destination 
    AccessMode : SQL Command
    CommandTimeOut : 0
    SQLCommand : Select * from #tmp
    * using SSIS 2012 and SQL OLEDB Native Provider 11 (Provider=SQLNCLI11.1)
    * one of the feed is 10MB
    During investigation using profiler, found that though I use RetainSameConnection, I often  could see that more than one SPId is used during the scope of SSIS execution and when ever this happens, package fails with below error message 
    An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "Statement(s) could not be prepared.".
    An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80040E14 Description: "Invalid object name '#tmp'."
    Now, Why SSIS uses a different SPId during its execution when RetainSameconnection is set to True (note : I have only one OLEDB connection in that package)? 
    To simulate the issue, Instead of 10MB file, I used a 500KB file and execute the package twice and all went fine.
    Is it because of 10 MB file taking long time to process causing the time out of that OLEDB destionation forcing the SSIS to go for another connection? but remember, CommandTimeout is set to infinite(0) for that OLEDB destination. 
    Much appreciated your response. 

    Hey,
    I understand you used Retainsameconnection property true for all the OLEDB connections you used in the package if not make sure its for all the connection including file connection as well.
    Additionally, you can try to set Delayvalidation property to true for all the dataflows and control flows in the connection and try running the package for 10MB file.
    I hope this will fix the intermittent failure issue you are facing with SSIS.
    (Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker)
    Thanks,
    Atul Gaikwad.

  • Issue with Dataflow Task in SSIS Package

    Hello Everyone,
    I have recently created an SSIS package to Load data from Flat file to SQL Server Table, it was working fine. Now I have bought a new laptop and copied the projects into this new system and changed all the connection managers(Flat files) accordingly. 
    Problem is, when I previously ran the package(With File1) in old laptop and check the distinct count on a table it was perfect, but when I ran the same package with same File on New Laptop, the Distinct count gives me an issue with particular record.
    Eg: Distinct Count with old laptop Run , 10,20,100
          Distinct Count with old New Run , 10,20,100  , 100
    There is a Space being generated for a particular record, when I run the package on new laptop with same File as old one.
    Any suggestions on this, I could not exactly figured out the Issue.
    Please Help.
    Thanks
    Thanks, Please Help People When they need..!!! Mark as answered if your problem is solved.

    You need to tell the responders here how exactly to reproduce your issue and provide the file.
    I do not know how the "distinct count" works.
    Seems to me it appears to be a database issue not SSIS.
    Arthur
    MyBlog
    Twitter
    When I perform the above query on old laptop, this gives me a result set of
    10
    20
    100
    When I perform the Same query on New laptop, this gives me a result set of
    10
    20
    100
    '100  ' (No Quotes please see the spaces generated)
    Thanks, Please Help People When they need..!!! Mark as answered if your problem is solved.
    Can you give us an idea of tasks you're having after the file source?
    Particulary see steps where you are doing some data manipulations.
    Please Mark This As Answer if it solved your issue
    Please Mark This As Helpful if it helps to solve your issue
    Visakh
    My MSDN Page
    My Personal Blog
    My Facebook Page
    I am using simple Flatfile source and oledb destination in here. this is causing issue, all the other tasks after this are loading perfectly except this.
    Thanks, Please Help People When they need..!!! Mark as answered if your problem is solved.

  • Issue with Multiple Tables in Report

    Post Author: dwessell
    CA Forum: General
    Hi,
    I'm using Crystal Reports 2k8.
    I'm doing a report with three tables, CQ_HEADER, SO_HEADER and SALESPERSON. Both the CQ_HEADER and the SO_HEADER tables link to the SALESPERSON table via a SPN_AUTO_KEY field.
    However, I always receive duplicates in my result set, due to the joins made, and I don't receive results that are valid in one table, and empty in another (Such that it only counts a CQ, if there is a SO associated with it. Here's the query that's produced by CR.
      SELECT "CQ_HEADER"."CQ_NUMBER", "CQ_HEADER"."ENTRY_DATE", "CQ_HEADER"."TOTAL_PRICE", "SALESPERSON"."SALESPERSON_NAME", "SO_HEADER"."ENTRY_DATE", "SO_HEADER"."TOTAL_PRICE"
    FROM   "CQ_HEADER" "CQ_HEADER" INNER JOIN ("SO_HEADER" "SO_HEADER" INNER JOIN "SALESPERSON" "SALESPERSON" ON "SO_HEADER"."SPN_AUTO_KEY"="SALESPERSON"."SPN_AUTO_KEY") ON "CQ_HEADER"."SPN_AUTO_KEY"="SALESPERSON"."SPN_AUTO_KEY"
    WHERE  ("CQ_HEADER"."ENTRY_DATE">={ts '2007-12-01 00:00:00'} AND "CQ_HEADER"."ENTRY_DATE"<{ts '2007-12-18 00:00:00'}) AND ("SO_HEADER"."ENTRY_DATE">={ts '2007-12-01 00:00:00'} AND "SO_HEADER"."ENTRY_DATE"<{ts '2007-12-18 00:00:00'})
    ORDER BY "SALESPERSON"."SALESPERSON_NAME"
    There is no link between the SO_HEADER and the CQ_HEADER.  Can anyone make a suggestion as to how I could go about structuring this such that it doesn't return duplicate values?
    Thanks
    David     

    Hey,
    I understand you used Retainsameconnection property true for all the OLEDB connections you used in the package if not make sure its for all the connection including file connection as well.
    Additionally, you can try to set Delayvalidation property to true for all the dataflows and control flows in the connection and try running the package for 10MB file.
    I hope this will fix the intermittent failure issue you are facing with SSIS.
    (Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker)
    Thanks,
    Atul Gaikwad.

  • Issue with 32 bit mapping while doing the job configuration.

    Hello,
                   From my end, facing a strange issue while execution of job in 32-bit mode.
    As part of the solution implementation, do have one excel file which has to be imported to my database. For this activity, have created a package in SQL 2012 and changed the project properties to 32-bit (by setting False from the Run64bitRuntime). With this
    implementation, It has worked fine without having an issue.
    As we are going with the project deployment model, have deployed this package to Integration Services Catalogs. From my end, have executed the package by choosing the option to execute in 32-bit Runtime and It is also worked fine.
    From my end, have configured the same package through job by mapping the package from SSIS Integration Catalog. Now, the job is getting failed as the package is not running in 64-bit mode.  Have tried to configure the package in 32-bit mode. But, I
    could not be able to configure the same. I am getting the option of 32-bit run time when I am going with File System,SSIS package store not with the SSIS Catalog.
    From your end,could you please help me in resolving this issue?
    SSIS Package Store--> Execution Options
    SSIS Catalog--> ????
    Regards,
    Pradeep.

    But it is a job property, not the catalog:
    Arthur My Blog

  • CDC Issue in SSIS Package

    Hi All,
    We have created SSIS package using CDC(2012). But performance is very slow. How can we improve performance in the below senario's
    Scenario A:
    Source DB & CDC in SSIS in the same server:
    When we run  the CDC package in this scenario. We are able to extract 500K records in 50seconds. 
    Scenario B:
    Source DB is in physical server 1 and CDC with SSIS in physical server 2:
    When we run the CDC package in the scenario, 10,000 record extraction takes 15min. We have Primary Key in the table from where we extracting the records.
    Please reply us how to solve the delay in data extraction using CDC in the Scenario B. We are using 2012.
    Kindly provide us multiple options.
    Thanks in Advance...

    Hi All,
    We have created SSIS package using CDC(2012). But performance is very slow. How can we improve performance in the below senario's. The issue in reading transaction log
    When we run the CDC package in this scenario, 10,000 record extraction takes 15min. We have Primary Key in the table from where we extracting the records.
    Issue : CDC source component is taking time to read data from transaction log file . Is there any way to track this ? 
    Our requirement is reading changed data e.g. 100,000 records in some seconds .
    Kindly provide us multiple options.
    Thanks in Advance...

  • Pipeline Delimeter issue in SSIS flatfile.

    I have flat file with pipeline delimeter with 9 columns, each columns having diffrent data lenth. i am having issue with one on of the column Address.
    User enter the value with PIPELINE symbol in his address, so that my developed SSIS packages got messed up bcoz my package is consider user enterted additional pipeline is one column. so my package is got failed. please help me, how to sort this issue or
    i need to consider this record as bad data.

    I would say you would have to consider this as bad data, and then process rest of the records as pipe is the only way one can identify the change in the columns, the way to identify bad data is, 
    a) Use a script task before your DFT, check each row for number of pipes expected ex: if you expect 10 columns then pipe should be 9 .
    b) Compare this condition and write a new file with only valid records and process this file.
    Abhinav http://bishtabhinav.wordpress.com/

  • Really, Really Weird issue in SSIS and DQS...

    My SSIS package is spitting out all 35 of my rows into the "invalid" bucket. In fact, only 4 of the rows should be invalid. When I used dataviewer to the output of the Data Cleansing task, I find that input columns are being wrongly selected
    as error by using a totally irrelevant domain. I have checked my task and ensured that the columns use the appropriate domains. Any thoughts? TIA
    Jagannathan Santhanam

    Hi Jagannathan,
    A number of things come to mind and I may be shooting in the dark here.
    1) Was the DQS install a clean install? Further have you had any issues with your SSIS project. I have know packages to become corrupted.
    2) By an irrelevant 'domain', I would presume that your incoming data into the 'data cleansing task' is coming from Master Data Services. I would suggest that you have a look to ensure that the subscription view that you are using (to pull the data) is
    valid and if NOT, recreate the view AND MOST IMPORTANTLY SEE THAT THE CURRENT FLAG is set. Should you need any help with this, PLEASE let me know.  I have an excellent example which I recently presented at the PASS Amsterdam Rally in November 2013.
    3) Next, within the Data Cleansing task ensure that the mappings are correct.
    4) I would also presume that your output from the data cleansing task is going into a conditional split. This one was a 'Gotha' to me. As I am sure that you are ware, you must think this one out carefully as the order in which you handle the output
    is CRITICAL to the logic. As I mentioned, this one caught me, giving faulty 'invalids' as well.
    In summary:
    This said, AND if I understand correctly what you have said above, please check that your subscription view is correct and what you think that it should be. A corrupt subscription view can cause this to happen.
    Sincerest regards
    Steve Simon SQL Server MVP

  • Connection Manager Issue in SSIS 2008 version

    Hello Team,
    I'm facing weird issue in SSIS 2008 version. In one SSIS package, whenever I open the connection manager and point the DEV server abd test the connection it is working. When I open again, it is throwing the below error eventhough I have access to the database.
    "Test connection failed because of an error in initializing provider. Login failed for user"
    It's with Windows Authentication.
    Additional Details:
    Package configuration is disabled.
    Connection manager has expression which is gettiing the details from variables that has DEV server details.

    Are the variables having static values? or is the values getting passed through a parameter?
    Please Mark This As Answer if it solved your issue
    Please Vote This As Helpful if it helps to solve your issue
    Visakh
    My Wiki User Page
    My MSDN Page
    My Personal Blog
    My Facebook Page

  • Edit a BPC Standard Package with SSIS

    Hi,
    I need to edit a BPC standard package ("Convert Task" for example) with SSIS.
    I have an Error message of Microsoft Visual Studio :
    The task with the name "Admin Task" and the creation name "Osoft.Services.Application.DataMgr.Task.SSISAdmin, OsoftTaskAdmin, Version=4.2.0.400, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648" is not registered for use on this computer. Contact Information:Admin Task
    I copied files .dll from "u2026\websrvr\bin" to "u2026\90\DTS\Tasks"
    Thank you for your help
    Regards,
    Morgann

    Hi James,
    I always have the same issue.
    For my customer, BPC is installed E:\ in Citrix environment
    In first, I followed the guide "How to...Build SSIS Package for SAP 5.0".
    I copied my "osofttask.dll" files in E:\BPC\websvr\Web\Installation\OsoftSSIS_client\Bin to E:\MSSQL\MSSQL2005-0\90\DTS\Tasks
    Then, I copied these files in GAC (C:\Windows\Assembly) like your procedure.
    But I always had the same error message in SSIS...
    Have you another idea ?
    Files are copied betwween E and C, is it an impact ?
    Thanks,
    Morgann

Maybe you are looking for