Generic Ssa Notok Error Message Siebel

fundamental configuration mistake, like syntax errors or missing workflows or incorrect joins are configured. This error can be very difficult to fix, as it leaves very thin trace behind and there is no indication to start with. When I faced this error I narrowed it sbl-bpr-00119 down by going through the most common reasons of this error and started to rule them (sbl-bpr-00162)--(sbl-dat-00472) out one by one. Following is the list which I followed from various support web articles. 1. Deleted Workflows Runtime events that are created automatically by workflow deployment have row id of workflow specified on them, and if that workflow does not exist in system then run time event can throw this error. To debug this turn on the personalisation logs and narrow down which runtime event is causing the trouble. 2. Explicit Joins on 1:1 tables Someone has created explicit join based on 1:1 extention table and name of the join is same as the table name. For example table S_SRV_REQ1_FNX is extension table of S_SRV_REQ, so one should not create join in Service request BC with table S_SRV_REQ1_FNX to avoid getting this error. 3. Calculated Fields This is the most common cause of this error. Any syntax mistake in calculation or calculation which compares a two different data types can result into SSA NOTOK Error. For example following calculation will cause this error : IIf ([Status] = 1, 10, 0) This because the status field is DTYPE_TEXT and it is compared to integer value. In my case I had a field in BC with syntactically incorrect calculation. Which was easy to find as it popped up as first thing in BC validation. 4. BC field Validations This is another place where calculated fields can be referred and could cause this error. This might not error out every time as calculation might not be evaluated in all conditions. So do check field level validations as well when trying to fix this issue. 5. Run-time events or DVMs Another place I would look for would be RTE and DVMs as they also use Siebel query language to identify records and validate things and any syntax goof up can cause this error to popup. Another place you might get this error is while generating sample XML for BIP reports, this happens because application is not able to find the folder location specified in component parameter for XMLPReportDataDir . Please feel free to share and discuss your experiences with this error in comments below. Labels: SBL-DAT-XXXXX Siebel Errors Email This BlogThis! Share to Twitter Share to Facebook Share to Pinterest No comments : Post a Comment Newer Post Older Post Home Subscribe to: Post Comments ( Atom ) Please promote

NOTOK Error in SiebelThis error occurs in Siebel when there is some fundamental configuration mistake, like syntax errors or missing workflows or incorrect joins are configured. This error can be very difficult to fix, as it leaves very thin trace behind and there is no indication to start with. When I faced this error I narrowed it down by going through the most common reasons of this error and started to rule them out one by one.Following is the list which I followed from various support web articles.1. Deleted WorkflowsRuntime events that are created automatically by http://howtosiebel.blogspot.com/2016/05/guide-to-resolve-generic-ssa-notok.html workflow deployment have row id of workflow specified on them, and if that workflow does not exist in system then run time event can throw this error. To debug this turn on the personalisation logs and narrow down which runtime event is causing the trouble.2. Explicit Joins on 1:1 tablesSomeone has c... 1 Comments Go to page leave a comment Comments vijay kona 2016-05-25 22:20:29 http://howtosiebel.blogspot.com.metacomment.io/2016/05/guide-to-resolve-generic-ssa-notok.html 0 very useful info..Thanks Alex!! Ads Your Comment Login to leave a comment Google Facebook Twitter See also How to send error information How to send error information How to send error information Last Updated: Apr 05, 2016 06:19AM PDT S... How to guide 2015/16 Search for: How to guide 2015/16 DISCLAIMER: Please note that this website is for educational purpos... Error Message: I created a post about this yesterday but I focused too much on how this error only happens when pla... [SR-1394] Implement SE-0061 - Add Generic Result and Error Handling to autoreleasepool() - Swift Timothy Wood added a comment - 3 May 2016 3:44 PM Closing as duplicate. Timothy Wood added a commen... How to Resolve 404 Not Found Problems Articles How to Resolve 404 Not Found Problems 404 Not Found issues can be a common windows error wh... How to write a great error message Imagine being in an office. In your cubicle. You’ve worked long hours this week for an upcoming prod... Welcome to SSA Best | SSA Best No front page content has been created yet. Welcome to the Benefit Eligibility Screening Tool (BEST)... H

Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX Visual Basic Web Design http://siebel.ittoolbox.com/groups/technical-functional/siebel-analytics-l/generic-ssa-notok-error-message-20316 and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries MacProTX Inside-ERP VoIP_News Inside-CRM I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker Ramnath.Awate http://siebel-conf.blogspot.com/2013/04/sbl-srb-00047-could-not-route-message.html JoeTorre Locutus bracke Dennis Stevenson PCMag Craig Borysowich DukeGanote Richard mircea_luca iudithm Nikki Klein Clinton Jones AbhaiTripathi knowscognosdoi Iqbalyk bluesguyAZ59 COMPANIES HP, Voltage Security and ... Hitachi America, LTD Arbor Networks, Inc. Quest Software View generic ssa All Topics View All Members View All Companies Toolbox for IT Topics Siebel Groups Ask a New Question Siebel Analytics For discussion on Siebel Analytics , please visit the Oracle BI group. More Siebel Groups Your account is ready. You're now being signed in. Solve problems - It's Free Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 generic ssa notok and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Generic SSA NOTOK error message. Unknown User asked Jul 10, 2000 | Replies (1) ITtoolbox Portal for CRM - http://CRM.ITtoolbox.com hi, while configuring a business component i added an mvg applet for position and performed a data validation for a field as well as set a search specification for the business component.everything was working ok yesterday but today when i opened the relevant screen i am getting the following error"Generic SSA NOTOK error message." can anybody throw light on the possible reasons for this error. Thanx Join this group Popular White Paper On This Topic The Death of Traditional Data Integration: How the Changing Nature of IT Mandates New Approaches and Technologies 1Reply Best Answer 0 Mark this reply as the best answer?(Choose carefully, this can't be changed) Yes | No Saving... Unknown User replied Jul 10, 2000 ITtoolbox Portal for CRM - http://CRM.ITtoolbox.com This error normally means the DB has

previously published as Siebel SR 38-3070028991.SymptomsCustomer has several custom workflow monitor agent components created. These workfine until the last few days wherethe agents fail with the following logs:SrmLayerLogError102006-06-19 16:51:28(srbroute.cpp(2052) err=5700035 sys=0) no other serverSrmLayerLogError102006-06-19 16:51:28(srbmsgfn.cpp(387) err=5700047 sys=0) Could not route message to WfProcMgr with registered key (null)GenericLogGenericError102006-06-19 16:51:28(srmconn.cpp (3049) err=5700047 sys=126) SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)GenericLogGenericError102006-06-19 16:51:28(srmconn.cpp (2703) err=5700047 sys=0) SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)GenericLogGenericError102006-06-19 16:51:28(srmconn.cpp (2303) err=5700047 sys=0) SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)CauseThe workmon is not able to communicate to wfprocmgr because this component is currently unavailable.SolutionAfter Reviewing Siebns.dat, it was observed that the wfprocmgr had a status of Offline a for the particular server. When a component is in a Offline status, it is not automatically started when the Siebel Server is bounced.Following steps to set the component online that helped resolve the issue :(1) Navigate to the Administration - Server Management > Enterprise. In this view, select the appropriate enterprise on the first applet (Enterprise). On the same view for the second applet (Server) select the appropriate server. On the same view again for the third applet (Component) select the appropriate component (wfprocmgr).(2) Then click the 'Startup' button. Refresh the list applet and again for the same component you need to click 'Online' button. Each time you click the button you need to give it a minute for the compont to startup or online but keep trying this until you see the component is 'Online'.(3) Navigate to the Administration - Server Configuration > Enterprises > Synchronization, to synchronize your batch components.It is also suggested can create a new custom workmon, You can refer following document.How Do You Start a Workflow Monitor Agent in Siebel Version 7.x? (Doc ID 476425.1)This document directs that how to create a new component , but it is always recommended making a copy of the vanilla workmon component and then setting the new component names according to the above d