BPC SSIS component permissions (7.0.116)

Environment:
- bpc v 7.0.116 (microsoft platform)
- 1 app server (ssis components installed here)
- 1 database server (sql server and analysis services)
We have a set of SSIS packages on the app server using the OSoft SSIS components and would like to run the packages from our centralized control-m (http://www.bmc.com/products/offering/control-m.html) scheduler.
Both the app server and database services (sql server and analysis services) are running under the same account (domain\osoft). When I log on the app server with the osoft account and run the packages, they execute successfully.
When I try to run these same packages from our control-m agent (account = domain\controlm), I get the following:
- admin tasks (create dimension): successful
- data manager - dump & load settings (import into cube): fails
The domain\controlm account has admin rights on the analysis services database and db_owner rights on the sql server database. In the data manager ssis control this is set for the server\userid: domain\osoft (same account is used for the admin task components as well which do work)
Unfortunately the OSoft SSIS components do not output any error information which is a known issue (sap note 1346004).
I have looked at the documentation for the components and did not see anything related to permissions but seems like a permission problem somewhere since the packages run under domain\osoft but not under domain\controlm.
Can someone point me in the right direction?
Thanks!
Henry

osoft
- app server
- member of server administrator group
- login account for sql server reporting services
- bpc: member of AdminTeam (AdminMbrAccPrf profile enabled)
- sql server
- login account for sql server service
- login account for sql server agent service
- login account for sql server analysis services service
- login account for sql server browser
- login account for sql server integration services
- member of the sql server sysadmin role
- analysis services database permissions
    - full control (administrator)
    - process database
    - read definition
controlm
- app server
- member of server users group
- bpc: member of AdminTeam (AdminMbrAccPrf profile enabled)
- sql server
- appset database the ssis components are run against
    - read (db_datareader)
    - write (db_datawriter)
- analysis services database permissions (same role as osoft account)
    - full control (administrator)
     - process database
     - read definition
The obvious glaring differences are app server administrator (osoft) vs app server user (controlm) and sql server sysadmin role (osoft) vs database read/write access (controlm). I would prefer not to give a job execution account (controlm) more privileges than it needs.
I will try to grant the controlm account sysadmin first, then server system administrator, and then both to see if the packages at least run but if anyone knows the least number of privileges to give the controlm account, I would be most appreciative.
Thanks!
Henry

Similar Messages

Sql Server 2008 - problems after incorrect installation of SSIS component

During the addition of SSIS component to an existing installation of Sql Server 2008 the setup has been made using Sql Server 2008 R2 media.
Now SSMS shows the following error during the connection to the instance :
Method not found: 'Int32.Microsoft.SqlServer.Management.Sdk.Sfc.ISfcDomain.GetLogicalVersion()'
I've tried to remove R2 components and to repair the existing 2008 installation.
At the moment 2008 R2 Native client and Setup are still present in the list of Programs and Features.
From previous comments I understand this method is in a Sql Server 2008 R2 assembly, so it seems that SSMS is running as R2 but is using 2008 libraries.
How can I correct this ?
Thanks.

Hello,
Be careful uninstalling now SQL Server 2008 R2 components. If you uninstall shared components that are SQL Server 2008
R2 components the whole SQL Server 2008 instance will be unusable. For more information about having SQL Server 2008 and SQL Server 2008 R2 installed on the same computer, please read the following article:
http://msdn.microsoft.com/en-us/library/ee210714(v=sql.105).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Error in creating custom SSIS component in sql server 2014

===================================
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 {33D831DE-5DCF-48F0-B431-4D327B9E785D} failed to initialize due to error 0x80131600 "".
Error at Data Flow Task [ [5]]: 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)
What was the possible causes.Please help me.This is irritating stuff

Yes DLL's were placed in pipelinecomponents folder and GAC also.is there any chance for having issue in development environment?
Hi Mahesh,
Have you install a version of SQL Server Integration Services (SSIS) that is earlier than SSIS 2014 installed on your computer? What's the detail version of your SQL Server Data Tool?
In addition, please help to collect clsid {33D831DE-5DCF-48F0-B431-4D327B9E785D} information in registry.
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

Pass BPC SSIS variable to stored procedure

Dear All
We have a ssis package in which there is data flow task. There
is a OLEDB source which uses “Data access mode” as sql command. We used OLEDB data source instead of execute sql task as the outuput is table format generated in Stored proc which is used in following task
This task calls a stored procedure with a input parameter which will be appset name.   [EXEC ProcName '@BPCAPPSET']
The stored procedure is executing fine without any issues.But when I pass variable containing appset name to that stored procedure its not taking properly and package ending successful.
The variable is “BPCAPPSET” it contains appset name which
will be taken front end.
   However to test if this value is taken by stored procedure
or not, I tried to hardcode and pass appset name to stored procedure. i.e exec
ProcName Appset1.
Appset1 is existing appset. It worked fine. But we want to
put this package in all land scapes, such that whenever it is triggered it will
take the appset as parameter and does the calculation in stored procedure.
   Please advice how to pass this variable to stored
procedure.
regards
Prasad

Hi Roberto
Thanks for your mail.
I have tried, but I am getting error that @BPCAPPSET scalar
variable must be defined.
I believe that @BPCAPPSET is system defined variable which
will be passed from Data manager package. May be this is the reason it is not
recognizing this variable?
If so, should I define a variable in SSIS. How can we
assign value of @BPCAPPSET to the newly defined variable?
Please advise. Attached screenshot.

BPC Mass User Management Tool in BPC 10.0 NW-Version Component Error

Hi,
We have a problem when importing request K900024.RBP and R900024.RBP.
We changed the UJ_STRING in "DATA: lv_value TYPE uj_value" in the source code as recommended at BPC Mass User Management Tool in BPC 10.0 NW
Unfortunately, when we try to import CSV files we receive a error message "BPC Version Component must be 800". Our is 801.
Where can I find this files or its upgrades? Is there a SAP link?
Can anybody help us?
Best Regards,
Ana Teresa

Hi Ana,
See note https://css.wdf.sap.corp/sap/support/notes/1861347. You should solve this issue.
Best Regards,
Charlie

BPC 7.5 Unable to add user

Hi All,
After installation of SAP BPC 7.5 for Netweaver I am facing an issue while adding a new user. I am getting the following error whenever I click on 'Add new user' in BPC:
"Could not find function module UJE_API_GET_ALL_TEAMS_DATA"
I have checked in SE37 and UJE_API_GET_ALL_TEAMS_DATA does not exist. What should I do to resolve this error?
Thanks in advance
Regards
Abhik Ray

Hi Abhik,
Have you verified that your Netweaver BPC (ABAP) component, .NET component, and client component are all on the same support package level? It sounds like your .NET/Web server might be on a different level than the ABAP component.
Ethan

Questions on Installing SAP BPC NW 7 SP2

Hi Friends,
My company is Installing SAP BPC NW 7 SP2 and I am heading the project starting from 1st June. I have downloaded the Installation guide and still have few questions
1) On which client we deploy BPC server component, I mean on 000 or any other.
2) Initially we are doing on Sandbox, so we are using only one system for both ABAP and NET servers and we are using 64bit machine. How do I run 1.1 Net framework on it, I have read installation guide it says configure to WOW6432 but dont know how to do it
3) When we download the ABAP server component what format will it be .SAR or .CAR or any other
Please do reply.
Thanks in advance
Bobby

Hello Bobby,
1. You will install the BPC server component with SAINT, which has to be executed in client 000, but BPC will actually run in the client you designate for BW.
2. The following article discusses configuring ASP.NET 1.1 to run in 32 bit mode on a 64 bit system [http://support.microsoft.com/kb/894435]
3. The ABAP server component will be a SAR file.
Thank you,
Daniel

For BPC how to enable Wow6432 compatibility to run in 32 bit mode on the 64

Dear friends
I am going to install BPC 7.0 so I want to enable following issues on my windows OS 64Bit
"If you run this on 64 bit hardware, you must configure it to enable
Wow6432 compatibility to run in 32 bit mode on the 64 bit system"
can any tell me solution as soon as possible
regarads
krishna
Edited by: krishna murthy on Feb 24, 2010 11:24 AM

hi,
as you read, your BPC was designed for NET1.1 which build under 32bit platform while NW AS ABAP needs 64 bit environments to run. wow3264 is to enable your 32 bit application to run on 64 bit platform in this case BPC NET component can run on 64 bit. wow3264 is windows registry keys. so you can find it in the registry value using regedit.msc.
may this help you.

SSIS installed on 64 bit SQL Clustered Node.

I'm not looking to run SSIS as a clustered service. Initially I just want to install it on node1 of the cluster, eventually I will install on the second node.
So I install the SSIS component via add/remove programs and point to the 64 bit installation of sql server.
Following that, I installed SQL 2005 SP2.
Everything seemed to run though perfectly.
Next, I installed an SSIS package from 32 bit machine via a manifest file using file system method.. great no errors.
Now I go to create a job and I get:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
===
Suddenly, for reasons unknow, now when I attempt to create a new step, I can get into the menu, but if I attempt to select a package I get:
I'm not looking to run SSIS as a clustered service. Initially I just want to install it on node1 of the cluster, eventually I will install on the second node.
So I install the SSIS component via add/remove programs and point to the 64 bit installation of sql server.
Following that, I installed SQL 2005 SP2.
Everything seemed to run though perfectly.
Next, I installed an SSIS package from 32 bit machine via a manifest file using file system method.. great no errors.
Now I go to create a job and I get:
TITLE: Microsoft SQL Server Management Studio
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
ADDITIONAL INFORMATION:
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
If I attempt to explore SSIS pakages from management studio I get:
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
ADDITIONAL INFORMATION:
The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
I'm wondering if this is because the package I deployed is 32 bit vs 64 bit? Or maybe I needed hot fixes in addion to SP2 after install the SSIS component after the original install?
Or maybe this was caused by registering of 32 bit DTS.dll files at some point trying to fix the original problem?
Thanks for any help or information.
TITLE: Microsoft SQL Server Management Studio
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
ADDITIONAL INFORMATION:
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
If I attempt to explore SSIS pakages from management studio I get:
TITLE: Microsoft SQL Server Management Studio

Just a note here... while this is an issue, the same error can come up if there are multiple instances and the msdb has moved to a location such that more than one instance tries to share an msdb. If this is the case for example, Instance1 points to
C:\program files\microsoft sql server\mssql\data\msdbdata.mdf and instance2 also points there, you will get this error. Check with:
Select name, physical_name as location, state_desc from sys.master_files where name='N'msdb';
If they both point to the same location (mine did), stop both instances, make a copy of the msdbdata.mdf and msdblog.ldg, restart one of the instances (say instance2) and repoint the copy you just made... say c:\program files\microsoft sql server\mssql.instance2\data
as follows:
alter database msdb modify file(name-msdbdata,filename='c:\program files\microsoft sql server\mssql.instance2\data\msdbdata.mdf
do the same for the log. Restart Instance2 and Start Instance1 and it should resolve the problem.
R, J

SQL Agent Permssions With SSIS for each loop not looping through files

Hi I am Having trouble getting a ssis package to iterate through a file directory using a proxy account set up in Sql Server.
So I have a package that loops over csv files. If I run the package manually or set the sql agent job to run as Sysadmin the pakage runs fine all files are processed.
However if I use the proxy account. the package completes but no files are processed. there are no failures, there is no error handling set up in the control flow. the for each loop container simply does not recognise any files when run under a proxy.
Note: the proxy is set up with credentials to access the folder. the credential is also set up with the server admin server role... still nothing
i'm not sure is this is a ssis or permissions problem?
Any comments will be appreciated

Can you check this and see if you've configured all the steps correctly
http://www.mssqltips.com/sqlservertip/2163/running-a-ssis-package-from-sql-server-agent-using-a-proxy-account/
Also enable logging in package and see if you're getting any error messages obtained in output table/file based on the logging option you chose.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How to read 835 files using ssis

Hello Everyone,
It is possible read 835 files using ssis.
Please share your suggestions on this.
Regards,
Vaishu

Hi Vaishu,
None of the canned (standard) SSIS tasks let you do so.
But if you can buy http://www.cozyroc.com/ssis/edi-source (I am not anyhow affiliated with CozyRoc) it states it can read ERA (AKA 835) files. CozyRoc lets you run it for free in Dev.
If there will be a decision not to buy then you can simply crate a transformation out of several manipulations or by creating a custom SSIS component or some other programming methods need to be used.
PS: Again, I just know CozyRoc quality of components is awesome, but I do not make any profit from referring to it.
Arthur My Blog

Unable to access the failure reason inside an SSIS flow, when using DQS Composite domains as part of an SSIS DQS Ceansing step.

Hi,
I have followed the discussions in the (now closed) post titled:
"Composite Domains in SSIS with spaces in the field"
re. how best to approach composite DQS domains when inside a SSIS flow.
I followed the approach recommended i.e.
" If
you map (in SSIS) your 2 individual source fields to both the (DQS) domains in your (DQS)Composite Domain, your composite domain automatically participates in the cleansing activity."
In the example I have, there would be a number of different validation rules , similiar
to the rules in that post which were called 'Circle', 'Square', etc.,, associated with the Shapes&Sides CD.
What I haven't figured out , is how to know from the output of the (SSIS) DQS Cleansing step when I get an
Invalid result
- which precise DQS rule (e.g.'Circle', 'Square'..etc) actually failed. ?
So for an input row (if we take the example from that post) with a 'Shapes' value of 'Square', and a
'Sides' value of '3', I would like to get 'Failed Square' (Square being the DQS rule name) as the reason for failure, and to be able to see that from inside SSIS.
If I use the derived column approach (as discussed at the start of the above discussions) I am able to get
this type of output by using the '...._Reason' DQS output corresponding to the derived column .
However I can't use the latter approach because of the issues with the derived column already highlighted
in that post.
I am also able to get the failed rule displayed when working fully inside the DQS client (no derived columns
of course, just working with the DQS Composite Domains).
However , as I say, I don't seem to be able to find out how to get it (the failed rule) when I map the individual
cols separately to the individual domains.
I do get an SSIS overall 'Record Status' = 'Invalid' but I dont know which rule failed.
I hope I am missing something, as otherwise I don't see how a user is going to figure out why the record is
'Invalid', given that there would typically be multiple rules, any one of which could be causing the record's 'Invalid' status.
Any help would be much appreciated.
Thanks,
Martin

I raised a similar question on the DQS forum. My domain (not a composite) was failing a rule but I didn't know which. I looked a bit further and was able to answer my own question. I've pasted my answer below. Hope it helps.
The SSIS DQS component does specify the domain rule that caused a failure in the 'reason' output column from the DQS SSIS component. It was my mistake.
I added a domain and added 2 domain rules. My source data in my SSIS process failed one of these rules. However, my source data value was already in the Domain Values list in DQS, and so when I ran the SSIS process, it highlighted the fact that my SSIS source
data was an existing domain value but that domain value was invalid as it failed domain rules, hence the 'domain' value in the DQS SSIS component output column.
I removed the value from the Domain Values in DQS, re-ran my package and this time my 'new' value failed but in the SSIS 'Reason' output column from the DQS SSIS component, it told me the rule that it failed on.
One thing to note. If it fails more than 1 rule, the SSIS 'reason' output column concatenates the rule names together.
So, for example, I had a domain with 3 rules. Length>2, Length>9 and Length>10. My new value was 3 characters in length and so it passed the first rule but failed the next two. The SSIS reason column had a value of 'Failed rule: 'Length >9 Length
>10'.

BCP to pass an Error Message to SSIS when the BCP call fails?

Hi,
Within SSIS I have an Execute SQL Task which calls BCP via a source variable given the dynamic nature of the BCP call.
When the BCP call fails it returns a number of records which give instructions on how to use BCP. SSIS then thinks that BCP has executed successfully, the component shows green and then the package continues to run.
But of course what I want the BCP call to do is return an error message which would then trigger the standard on error event handler within SSIS. How do I do this please?
It maybe the “Execute Process Task” could be a better SSIS component to use for this call
Using BCP Utility in SSIS. Does anyone have experience of doing this type of thing?
Thanks in advance,
Kieran.
Kieran Patrick Wood http://www.innovativebusinessintelligence.com http://uk.linkedin.com/in/kieranpatrickwood http://kieranwood.wordpress.com/

Why don't you use the "Fast Load" option = BULK LOAD? Or the BULK LOAD stored proc?
The only other way I can think of this can be done is by directing errors to an error file which can be interrogated from the package and then a precedence constraint used to trigger an error if there was one.
Arthur My Blog

SAP Bpc: automate script logic validation

Is there a way to automate the validation of the SAP BPC script logics?
I ask you that because I have daily SSIS packages and, actually, if I don't manually vaildate the logics every time, using SAP BPC administration interface, the new members are not cosidered into the application.
I tryed the BPC SSIS "Adimin Task" (using Validate Logic mode) but it only checks if the syntax of the logic is correct or not.

Thanx for the replay but, unfortunatly, I think it's not useful for my case.
I use SSIS packages to populate dimensions (such as Employees). In these packages I have BPC Admin Task (in create dimension mode) and it works fine.
The problem is > if I don't go into SAP BPC Administration Console to "Validate and Save" the script logics manually > inside the .lgx file there aren't into XDIM_MEMBERSET the new data I previously imported throught the SSIS packages above (in the exemple the new Employees).
Beeing not into the XDIM_MEMBERSET, the script logic executed by the users excel input schedules cannot manage the new set of data... until I "Validate and Save" the logic manually.
Edited by: Francesco Andolfi on May 26, 2010 4:22 PM
Edited by: Francesco Andolfi on May 26, 2010 4:22 PM

BPC client compatibility

Hi all,
I have few questions regarding BPC for NW. I would appreciate if someone can clarify them for me.
1- Where can I find the sp level of BPC .Net component. (is it from server manager System Information. I can see .06 there. does that mean sp06?)
2- If I want to patch BPC ABAP component from from sp06 to the latest patch. Do I also have to patch .net component to the same level? And also do i also have to patch BPC client to the same level ?
3- Can i patch BPC client to the higher level than that of BPC ABAP component ????
Regards,
Rizwan.

Hi,
Yes, that would mean SP06.
Usually, if you are applying a patch, all the components should be on the same patch level. However, there are few patches which are applicable only to the clients. This means that the the patch level will be different from the .NET server, in this instance. In all the other cases, you should apply the same patch level to all the components.
Hope this helps.

BPC SSIS component permissions (7.0.116)

Similar Messages

Maybe you are looking for