Error in Analysis Process (APD)

Dear Guru's,
We have a Analysis process to move Data from a Query -> Flatfile(Csv file on a server).
when i Execute it i get following Error.
Also i didnot found any proper note
Variant '!PERSQBSSMYJ2703U9GOOPWQSYGXN0' for the query was not found
Message no. RSAN_WB010
Diagnosis
Technical key for message: CX_RSAN_MDL_DS_QUERY=>VARIANT_INVALID
Procedure
If you require further assistance, look for a SAP Note containing the key words CX_RSAN_MDL_DS_QUERY=>VARIANT_INVALID or RSAN_WB010.
Thanks in Adv
Dev

Well its a been a few months and I discovered a workable solution. I was able to get the APD process to work in a process chain by creating a variant in RSRT (query monitor screen). The variants I created with 7.x Bex result in the error message.
A 7.x query was built. The variant was created in RSRT. THe process chain works normally.
Apparently the tables where 7.X variants are stored do not get looked at when running a query with the APD process.
I sure hope all of this works when we upgrade to 7.3x.

Similar Messages

Error in Analysis Process Designer

Hi Friends,
I am trying to create an Analysis Process Designer, in that input is nothing but a Query which is built using Cell Editor, (as cell level Logic is different for the Query), now while assigning that Query to DSO in APD it is showing following error,
The technical field name KYF_0001 for field XXXXXXXXXXXXXXXXXX may only appear once per input or output structure
where is the problem exactly?
Thanks in advanced.
Regards,
Rajdeep.

Hi Rajdeep,
The KF of the Query is not mapped properly to the DSO KF.SAme Tech nname of the query has been mapped multiple times.
Do this
1)When u go to mapping in APD u have to map the DSO and the Query,so suppose u have map Quantity of Query to Quantity of DSO.
2)Go to the Query and in the properties of the KF in the Advanced Tab u will having the TECH Name of the KF
3)Map the right KF with DSO and Query
Get bak for any issues !!!!!!
rgds
SVU123

Process chains get an error when run analysis process

When my PRD system‘s process chains run analysisi process, I gets below error message:
Error occurred when starting the parser: Error when opening an RFC connection (FUNCTION: 'R
Message no. BRAINOLAPAPI011
Diagnosis
Failed to start the MDX parser.
System Response
Error when opening an RFC connection (FUNCTION: 'R
Procedure
Check the Sys Log in Transaction SM21 and test the TCP-IP connection MDX_PARSER in Transaction SM59.
It's OK when i test the TCP-IP connection MDX_PARSER in Transaction SM59.
The Sys Log in Transaction SM21(error part):
M Wed Mar 19 09:22:50 2014
M *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35, r, ..) returned -14 [thxxexec.c
M {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
A RFC 1878 CONVID 18933904
A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
A RFC> ABAP Programm: SAPLSTPA (Transaction: )
A RFC> User: JY-LKZ (Client: 900)
A RFC> Destination: CALLTP_AIX (handle: 8, DtConId: 530F4E5C30AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
A RFC SERVER> RFC Server Session (handle: 1, 68443927, {5328109B-5F5D-12A0-E100-8000C0A8642F})
A RFC SERVER> Caller host:
A RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
A RFC SERVER> Called function module: TMS_CI_START_SERVICE
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
FUNCTION: 'RfcExecProgramKernel'
RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18933904 IDX=35
[abrfcio.c    9213]
A {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=5328109B5F5D12A0E1008000C0A8642F}_5
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE
M
M Wed Mar 19 09:23:15 2014
M *** ERROR => ThPOpen: ExecPopen("/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61, r, ..) returned -14 [thxxexec.c
M {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
A RFC 1878 CONVID 18968493
A   * CMRC=0 DATA=0 STATUS=0 SAPRC=0 RfcExecProgramKernel RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
A RFC> ABAP Programm: SAPLSTPA (Transaction: )
A RFC> User: TMSADM (Client: 000)
A RFC> Destination: CALLTP_AIX (handle: 3, DtConId: 530F4E7830AF4550E1008000C0A8642E, DtConCnt: 0, ConvId: ,)
A RFC SERVER> RFC Server Session (handle: 1, 70212851, {53281195-8F75-0F10-E100-8000C0A8642F})
A RFC SERVER> Caller host:
A RFC SERVER> Caller transaction code: STMS (Caller Program: SAPLTMSC)
A RFC SERVER> Called function module: TMS_CI_START_SERVICE
A *** ERROR => RFC Error RFCIO_ERROR_SYSERROR in abrfcpic.c : 1887
FUNCTION: 'RfcExecProgramKernel'
RfcRaiseErrorMessage cmd could not be started by OS (rc = 1)
PROG ="/usr/sap/BWP/DVEBMGS00/exe/tp" bwprd sapgw00 18968493 IDX=61
[abrfcio.c    9213]
A {root-id=532810645F5D12A0E1008000C0A8642F}_{conn-id=532811958F750F10E1008000C0A8642F}_1
A TH VERBOSE LEVEL FULL
A ** RABAX: end RX_GET_MESSAGE.
ps.
1、IT's everything ok in the development system.
2、It’s ok when i repeat this analysis process .
3、It’s ok when i run this analysis process in analysis process designer.
4、Attachment is the sys log in sm21.
Thanks everyone.

Hi Vignesh.B,
Yes,it's not user's problem . But i don't think it APD's problem .Cause all APD has the same problem and .
Below is one of APD souce and target :
Hope this information is useful .
Regards,
Lian

APD Analysis Process Designer - CRM Data Target

Hi,
I have now defined the DataTarget and by "Release data target for Replication from SAP BW" I get the error:
<b>Error when processing function module /SVC/OBJ_F4_<MyDataTarget></b>
what does it mean and how can I solve this situation?
Thanks
FedeX

Hi!
in case if you are not able to find the docu...here is the docu helop for the function group...
"The function group CRMBW_ADAPTERS combines function modules that are necessary for implementing a data target adapter as part of the data upload from SAP BW. You can use the function modules delivered by SAP as a template for new adapters (for example, you can copy them).
The function modules contained in this function group are divided into the following areas on the basis of their naming convention:
o     Function modules for defining data targets
-     CRMBW_OBJ_F4_*
-     CRMBW_DET_F4_*
-     CRMBW_CHECK_*
o     Function modules for designing the analysis process
-     CRMBW_LIST_*
-     CRMBW_DETAIL_*
o     Function modules for the data upload
-     CRMBW_UPDATE_*
The placeholder * stands for a data target adapter defined in the IMG activity .
The corresponding adapter modules are called up dynamically during runtime at the appropriate points in the program, using the name of the data target adapter and applying the following program logic:
CONCATENATE l_namespace l_nameconvention
l_function l_target INTO l_funcname.
TRY.
CALL FUNCTION l_funcname
    EXPORTING
    IMPORTING
    TABLES
CATCH cx_root.
    l_msgv1 = l_funcname.
    CALL FUNCTION 'BALW_BAPIRETURN_GET2'
      EXPORTING
        type   = 'E'
        cl     = 'CRMBW_ATTR_WRITE'
        number = '005'
        par1   = l_msgv1
      IMPORTING
        return = ls_return.
    APPEND ls_return TO et_return.
ENDTRY.
Consequently, if a function module does not exist or errors occurred when calling it up, a runtime error is not issued directly. Instead, the error is returned as a message in the return table for the instance calling up the function module.
If you want to create customer-specific data target adapters, observe the following:
o     Define the ID for the data target adapter in the IMG activity . Ensure that your entry begins with the letter Y or Z to avoid any naming conflicts with subsequent SAP enhancements.
o     In this function group, implement adapter modules that begin with the namespace stored in the IMG activity mentioned above and with the naming convention, and that also fulfil the naming convention listed under Integration. In this way, you ensure that there are no naming conflicts with subsequent SAP deliveries.
o     To provide the data upload with full support, implement all six adapter modules.
With the following entry in the IMG activity , implement the function modules listed below.
Data Target Adapter     Namespace     Naming Convention
ZTARGET     /COMPANY/     MYLOAD_
Function Modules
/COMPANY/MYLOAD_OBJ_F4_ZTARGET
/COMPANY/MYLOAD_DET_F4_ZTARGET
/COMPANY/MYLOAD_CHECK_ZTARGET
/COMPANY/MYLOAD_LIST_ZTARGET
/COMPANY/MYLOAD_DETAIL_ZTARGET
/COMPANY/MYLOAD_UPDATE_ZTARGET
with regards
ashwin

Error in output processing analysis

Hi,
we have maintained ZA output types corresponding to partner number as Personnel number and we have not maintained the address for the Pernr as thats how our business works. now the issue is when we process the output type ZA , we get an error in "output processing analysis" that adrnr is not maintained how can we suppress the error ??
the error comes after it does not receives adrnr in FM 'ADDR_GET_NEXT_COMM_TYPE' for the form output.
below ins the error i get
http://img9.imageshack.us/img9/8894/sdnt.jpg

In your delivery in the Picking tab, check if the Picking status says 'Not relevant for Picking'.
If that is the case, then you have to see if that is intentional or by mistake.
if it is not intentional, then you can change the delivery item category config to make the item relevant for picking.

Error in a process chain

Hello,
i have included one APD in a process chain. If i execute APD manually the data is getting updated in the ODS. But if i include APD in a process chain then it throws an error that You are not authorized to execute this analysis process.
Can anyone suggest how the issue can be resolved.
Thanks,
Kumkum

Hi,
Goto SU53 and see the missed Objects then ask Basis team to include the Missed Obejcts in your roles.
see, Authorization Objects in SAP help.
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a6859e07211d2acb80000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/f3/291542e4b4df2ce10000000a1550b0/frameset.htm
Thanks
Reddy

Graph Error in Analysis

I've created a Decision Tree Datamining analysis in APD, When I click on View Model Results in context menu of active Training Set the graph screen appears blank and the message below thrown.
Default type 0 is not available in link group INST
Message no. CG016
Diagnosis
No default type has been set for the node group.
System Response
Processing stops.
Procedure
If you have the relevant authorization, enter a default type for the node group.
And when I click on that blank screen, it gives OBJ_DUPLIATE error, A RAISE statement in the program SAPLGRAP raised exception condition OBJ_DUPLICATE
What do you offer to resolve this issue ?

Good day,
There is a SAP Note which contains a small report for this error .. SAP Note 841462.
All of the details given there should be helpful.
Hope this helps!
Karen

Analysis Process Designer and Inventory Management

In the How to guide for Inventory Management it mentions that you can you can intialise stock in the Snap shot Cube using the Analysis Process Designer (APD). Has anyone done this and if so can you explain how or outline some steps? Thanks

Hallo,
the APD does`nt be a useful tool for modeling a performant
data flow. A lot of SAP BW user think so.
The performance problems are given by the ddic intern table, using to uploading the extracted data into the apd used wa_table and structures.
To have the best performance on your scenario, please use the following scenario as possible.
Step 1.
upload the extracted data from the psa into a data layer
there you can reduce and harmonize the data by using a transactional ods
Step 2.
build a infoset that joins the data
Step 3.
build one query to reducing data and make two copies of ist
Step 4.
build a useful data mining model
Step 5.
upload the results of the data mining model into a transactional ods
Step 6.
link the uploaded data into a infoset ore write back into a standard ods
Step 7.
query the data
If you use this scenario you have a lot of benefits. Better performance, better quality of persistent data and actual and traininged data.
The recommend next step (if you want a alerting) is to build a reporting agent report - if you have usefull processes in the query.
There are a workshop for Data mining and APD, named BW380.
I hope I helped you.
Otherwise give me a message.
[email protected]

Error message during processing in BI

1.i am loading the data into infoobject.
2.got error in text data load.
3.master info object have compound obj 0COUNTRY
4.and other normal fields are 0TXTSH,0LANGU,sold-to-party.
5.there is no PSA in this..its direct update to INFOobject.
The error message is:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Update
Diagnosis
There are duplicates of the data record 2. with the key '3.' for characteristic 1..
Procedure
If this message appears during a data load, maintain the attribute in the PSA maintenance screens. If this message appears in the master data maintenance screens, leave the transaction and call it again. This allows you to maintain your master data.

Hi KP,
In the details tab,
1.under Transfer (IDOC and Trfc):
   Data Package 1 : arrived in BW ; Processing : Error records written to application log
2.Processing (data packet): Errors occurred
   Update ( 0 new / 0 changed ) : Errors occurred
   Error records written to application log
   0TRZONE : Data record 1 ('0000000001D ') : Duplicate data record
   0TRZONE : Data record 2 ('0000000002D ') : Duplicate data record
   Error 4 in the update
3. Process chain error
these are the error details.

500 Internal Server Error Failed to process request in portal

Hi ,* We face problems to run Dev and Qual systems on our Sap portal devices. Production is OK The error message (see hereafter) does not occur on welcome page but on any page that communicate by Web Dynpro with ECC SAP system 500 Internal Server Error SAP NetWeaver Application Server 7.00/Java AS 7.00 Failed to process request. Please contact your system administrator. [Hide] Error Summary While processing the current request, an exception occured which could not be handled by the application or the framework. If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, ... com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'SSOL_WS_METADATA_DEST' and WS interface 'ZGetListCustomerAgent'. One possible reason is that the metadata destination 'SSOL_WS_METADATA_DEST' has not been properly configured; check configuration. at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248) at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.(WSTypedModel.java:41) at com.bluestarsilicones.ssol.models.customer.WS_GetListCustomersForAgentModel.(WS_GetListCustomersForAgentModel.java:53) at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalListCustomerAgentModel(OrderCreationComponent.java:587) at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalModels(OrderCreationComponent.java:555) at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.wdDoInit(OrderCreationComponent.java:193) at com.bluestarsilicones.ssol.wd.ordercreation.wdp.InternalOrderCreationComponent.wdDoInit(InternalOrderCreationComponent.java:943) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869) at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229) at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344) at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356) at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549) at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193) at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150) at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108) at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215) at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200) at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430) at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783) at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694) at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253) at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62) at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176) Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details. at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:157) at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.(DGenericServiceImpl.java:56) at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88) at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:141) at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429) ... 60 more Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception. at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:284) at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:154) ... 64 more Caused by: java.io.IOException: Compilation fails... Compilation process error : Not enough space at com.sap.engine.services.webservices.jaxrpc.util.Compiler.compile(Compiler.java:53) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:328) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traversThrough(PackageBuilder.java:291) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:485) at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compilePackage(PackageBuilder.java:215) at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:271) ... 65 more Thanks for your help. TY.

Hi,
I think you are accessing the portal via one of the dialog instance and not using the Central instance.So you are not getting the error displayed in iview. If you want to activate navigate to system administration-system configuration-services and in portal runtime central configuration open the object and in portal .runtime .print cause .exception make it to true and restart the service. This may be for print but some where here in the services you can activate that.
For productive environment detailed exception is not recommended.Administrator can see the error log in
log files.
Thanks and regards,
gopal.sattiraju

Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.

Errors in the OLAP storage engine: An error occurred while processing the indexes for the partition of the measure group of the cube from the database.
I have dropped and recreated a fact table to refresh the data as the table is having identity columns. So not able to directly insert data. After that cube is throwing above error.
Please suggest.

Hi Md,
It hard to analyse the issue base on the limited information, Are there any error message on the log? Under C:\Program Files\Microsoft SQL Server\MSAS11.\OLAP\Log (this could be different for your server), there are 3 log files that are generated:
msmdrrv.log
FlightRecorderCurrent.trc
FightRecorderBack.trc
The msmdrrv.log simply points to the other two logs. There might be some detail information for this error. Please provide us the detail information about it, so that we can make further analysis.
Regards,
Charlie Liao
TechNet Community Support

Getting Date error when I process

Hi All,
I have DEV & QA Analysis services on 2 different server. This is 2005 SSAS
I am using same solution so DEV process OK but QA gives me date error
when I check with SSMS , date fields look fine .
But I am getting this error in QA
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_view_ftblCharge, Column: SrvDateKey, Value: 12/13/2005. Errors in the OLAP storage engine: The record
was skipped because the attribute key was not found. Attribute: Date of Dimension: Service Date from Database: Charges, Cube: Charges, Measure Group: Charges, Partition: Charges, Record: 1. Errors in the OLAP storage engine: The process operation ended because
the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'Charges' partition of the 'Charges' measure group for the 'Charges'
cube from the Charges database
Thanks,
Gok

12/13/2005 is an American date format (mm/dd/yyyy) whereas you need a british date format 13/12/2005 (dd/mm/yyyy).
Have a look at this topic on how you can force the correct collation (date format)
http://sqlmag.com/blog/forcing-collation-where-clause-22-jun-2011
Please click "Mark As Answer" if my post helped. Tony C.

Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFact' mea

<Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFact' measure
group for the 'vAMGenericUTC' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
Any idea abt this error
Putting details error ..
<return
xmlns="urn:schemas-microsoft-com:xml-analysis">
<results
xmlns="http://schemas.microsoft.com/analysisservices/2003/xmla-multipleresults">
    <root
xmlns="urn:schemas-microsoft-com:xml-analysis:empty">
      <Exception
xmlns="urn:schemas-microsoft-com:xml-analysis:exception"
/>
      <Messages
xmlns="urn:schemas-microsoft-com:xml-analysis:exception">
        <Error
ErrorCode="3238395904"
Description="OLE DB error: OLE DB or ODBC error: Cannot execute the query
"SELECT
"Tbl1002"."idUTCDateTime"
"Col1145","Tbl1002"."idLocalDateTime"
"Col1146","Tbl1002"."idDateKey"
"Col1147","Tbl1002"."idUTCDateKey"
"Col1148","Tbl1002"."idMinuteKey"
"Col1149","Tbl1002"."idUTCMinuteKey"
"Col1150","Tbl1002"."idInstance"
"Col1151","Tbl1002"."idMetricKey"
"Col1152","Tbl1002"."idKSKey"
"Col1153","Tbl1002"."idMaintenanceKey"
"Col1154","Tbl1002"."MetricMin"
"Col1155","Tbl1002"."MetricMax"
"Col1156","Tbl1002"."MetricCount"
"Col1157","Tbl1002"."MetricSum"
"Col1158","Tbl1002"."MetricLog"
"Col1159","Tbl1002"."MetricSumOfSquares"
"Col1160","Tbl1002"."MetricSumOfLogSquares"
"Col1161","Tbl1002"."idTextData"
"Col1162","Tbl1002"."idLoad"
"Col1143",CONVERT(smalldatetime,"Tbl1002"."idDateKey",0)
"Expr1004",CONVERT(smallint,"Tbl1002"."idMinuteKey",0)
"Expr1006",(1)
"Expr1008" FROM
"DM_VSQL51_SOPM33_QDB"."dbo"."vData"
"Tbl1002" WHERE
"Tbl1002"."idLocalDateTime">=(1362096000)
AND "Tbl1002"."idLocalDateTime"<=(1364774399)
AND "Tbl1002"."idLoad">=(9243)
AND "Tbl1002"."idLoad"<=(9304)"
against OLE DB provider "SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB". ; 42000; The OLE DB provider
"SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB" reported an error. Execution terminated by the provider because a resource limit was reached.;
42000." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFact_201303_INCR_UPDATE_TEMP_he3dx_' partition of the 'vFact' measure
group for the 'vAMGeneric' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3239837698"
Description="Server: The operation has been cancelled."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238395904"
Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFact_201304_INCR_UPDATE_TEMP_kq5tw_' partition of the 'vFact' measure
group for the 'vAMGeneric' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238395904"
Description="OLE DB error: OLE DB or ODBC error: Operation canceled; HY008."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3240034318"
Description="Errors in the OLAP storage engine: An error occurred while processing the 'vFactUTC_201304_INCR_UPDATE_TEMP_qtfcw_' partition of the 'vFactUTC'
measure group for the 'vAMGenericUTC' cube from the AC_OLAP database."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
        <Error
ErrorCode="3238002695"
Description="Internal error: The operation terminated unsuccessfully."
Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
      </Messages>
    </root>
</results>
</return>

against OLE DB provider
"SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB". ; 42000; The OLE DB provider
"SQLNCLI10" for linked server
"DM_DS_SOPM33_QDB" reported an error. Execution terminated by the provider because a resource limit was reached.;
42000." Source="Microsoft SQL Server 2008 Analysis Services"
HelpFile="" />
Hi Born,
Have you check your disk space? This issue might be caused by not enougl disk sapce. Here is a similar thread about this topic:
http://social.technet.microsoft.com/Forums/en-US/sqlanalysisservices/thread/1783c640-5d4d-4086-bbdc-05adc45e3816/
If you have any feedback on our support, please click
here.
Regards,
Elvis Long
TechNet Community Support

500   Internal Server Error Failed to process request

Hi ,
We face problems to run Dev and Qual systems on our Sap portal devices. Production is OK
The error message (see hereafter) does not occur on welcome page but on any page that communicate by Web Dynpro with ECC SAP system
500   Internal Server Error
SAP NetWeaver Application Server 7.00/Java AS 7.00
Failed to process request. Please contact your system administrator.
[Hide]
Error Summary
While processing the current request, an exception occured which could not be handled by the application or the framework.
If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, ...
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Exception on creation of service metadata for WS metadata destination 'SSOL_WS_METADATA_DEST' and WS interface 'ZGetListCustomerAgent'. One possible reason is that the metadata destination 'SSOL_WS_METADATA_DEST' has not been properly configured; check configuration.
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:440)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.readOperationsFromWSDL(WSModelInfo.java:372)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadataInternal(WSModelInfo.java:342)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.importMetadata(WSModelInfo.java:326)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo$Cache.getModelInfo(WSModelInfo.java:199)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:1035)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getModelInfoFromCacheOrCreate(WSModelInfo.java:248)
        at com.sap.tc.webdynpro.model.webservice.gci.WSTypedModel.<init>(WSTypedModel.java:41)
        at com.bluestarsilicones.ssol.models.customer.WS_GetListCustomersForAgentModel.<init>(WS_GetListCustomersForAgentModel.java:53)
        at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalListCustomerAgentModel(OrderCreationComponent.java:587)
        at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.initalModels(OrderCreationComponent.java:555)
        at com.bluestarsilicones.ssol.wd.ordercreation.OrderCreationComponent.wdDoInit(OrderCreationComponent.java:193)
        at com.bluestarsilicones.ssol.wd.ordercreation.wdp.InternalOrderCreationComponent.wdDoInit(InternalOrderCreationComponent.java:943)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingPortal(ClientSession.java:761)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:696)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
        at com.sap.tc.webdynpro.clientserver.session.core.ApplicationHandle.doProcessing(ApplicationHandle.java:73)
        at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.sendDataAndProcessActionInternal(AbstractApplicationProxy.java:869)
        at com.sap.tc.webdynpro.portal.pb.impl.AbstractApplicationProxy.create(AbstractApplicationProxy.java:229)
        at com.sap.portal.pb.PageBuilder.updateApplications(PageBuilder.java:1344)
        at com.sap.portal.pb.PageBuilder.createPage(PageBuilder.java:356)
        at com.sap.portal.pb.PageBuilder.init(PageBuilder.java:549)
        at com.sap.portal.pb.PageBuilder.wdDoInit(PageBuilder.java:193)
        at com.sap.portal.pb.wdp.InternalPageBuilder.wdDoInit(InternalPageBuilder.java:150)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingComponent.doInit(DelegatingComponent.java:108)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.initController(Controller.java:215)
        at com.sap.tc.webdynpro.progmodel.controller.Controller.init(Controller.java:200)
        at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.init(ClientComponent.java:430)
        at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.init(ClientApplication.java:362)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.initApplication(ApplicationSession.java:783)
        at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:303)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:741)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:694)
        at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:253)
        at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
        at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
        at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
        at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
        at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
        at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
        at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
        at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
        at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
        at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.WebserviceClientException: GenericServiceFactory initialization problem. Could not load web service model. See nested exception for details.
        at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:157)
        at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.<init>(DGenericServiceImpl.java:56)
        at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:88)
        at com.sap.engine.services.webservices.espbase.client.dynamic.GenericServiceFactory.createService(GenericServiceFactory.java:141)
        at com.sap.tc.webdynpro.model.webservice.metadata.WSModelInfo.getOrCreateWsrService(WSModelInfo.java:429)
        ... 60 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.ProxyGeneratorException: Proxy Generator Error. Proxy generation problem. See nested exception.
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:284)
        at com.sap.engine.services.webservices.espbase.client.dynamic.impl.DGenericServiceImpl.generateProxyFiles(DGenericServiceImpl.java:154)
        ... 64 more
Caused by: java.io.IOException: Compilation fails...
Compilation process error : Not enough space
        at com.sap.engine.services.webservices.jaxrpc.util.Compiler.compile(Compiler.java:53)
        at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:328)
        at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.traversThrough(PackageBuilder.java:291)
        at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compileExternal(PackageBuilder.java:485)
        at com.sap.engine.services.webservices.jaxrpc.util.PackageBuilder.compilePackage(PackageBuilder.java:215)
        at com.sap.engine.services.webservices.jaxrpc.wsdl2java.ProxyGenerator.generateProxy(ProxyGenerator.java:271)
        ... 65 more
Thanks for your help.
TY.

Hi,
Please check the following,
1. JCO connections are configured properly and working fine.
2. Check the SLD connection is successful.
3. System definition is available for the ECC system.
Thanks.
Sushil

Error occurred while processing the "sales" partition of the "sales" measure group in the cube

Hi
when i ran the job for processing the cube it showing the error like "error occurred while processing the sales partition of the sales measure group in the cube". but in log files no error massage was there. after get that error message we ran
the cube manually
at that time the cube executed successfully.
my aim when the job was run it will be process automatically but it is not like that.
can you suggest the solution.
thank you
satyak248

Hi Satyak248,
According to your description, you get the error when using Windows Task to process a cube on a schedule, however can process the cube on SSMS successful manually, right?
In your scenario, you can process the cube manually, the issue can be cause by Windows Task was not set correctly. So you can try to process the cube using SSIS package. The Analysis Services Processing Task in SQL Server Integration Services (SSIS) allows
for the processing of one to many to all Analysis Services objects in an SSIS package. Once the SSIS package is created, then a job can be created within the SQL Server Management Studio which will allow for scheduling.
http://www.mssqltips.com/sqlservertip/2994/configuring-the-analysis-services-processing-task-in-sql-server-2012-integration-services/
Regards,
Charlie Liao
TechNet Community Support

Error in Analysis Process (APD)

Similar Messages

Maybe you are looking for