on 08-19-2014 1:35 PM
Hi Gary - I just tried this on our BI4.1 SP4 and I can't recreate this issue.
I am using a BEx query as a data source
Can your BI admin look at the logs on the BI platform to troubleshoot further?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tammy,
I am also using a BEx query as a source.
Here is a sample from the log generated with the error.
FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
ENCODING:UTF-8
RECORD_SEPARATOR:30
COLUMN_SEPARATOR:124
ESC_CHARACTER:27
COLUMNS:Location|Guid|Time|Tzone|Trace|Log|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text
SEVERITY_MAP: |None| |Success|W|Warning|E|Error|A|Assertion
HEADER_END
.\sisecserver_impl.cpp:366:-: TraceLog message 1975
|9f7ece35-be1d-2d14-1bc2-7bff07613dad|2014 08 18 11:08:47:073|-0400|Error| |>>|E| |cms_<systemname>.CentralManagementServer| 3064|3912|| |16|0|2|0|.pleaseDoIt|<systemname>:4672:77.17037:1|BIPSDK.SecurityInfo2:getKnownRightsByPlugin|<systemname>:4672:77.17037:8|cms_<systemname>.CentralManagementServer.processSerializedBatch|localhost:3064:3912.1341290:1|Cms7JKToqE96nzxl5QO0Pa4b6|||||gmartins||||||assert failure: (.\sisecserver_impl.cpp:366). (wireProps != NULL : no message).
.\sisecserver_impl.cpp:366:-: TraceLog message 1976
....repeats the message for a bit....
.\DatabaseSubsystem_impl.cpp:239:-: TraceLog message 2016
|12bb289b-9a11-3d24-baab-52530a8702d3|2014 08 18 11:09:21:115|-0400|Error| | |E| |cms_<systemname>.CentralManagementServer| 3064|3376|| |1|0|1|0|BIPSDK.InfoStore:query|<systemname>:4200:180.2885205:1|BIPSDK.InfoStore:query|<systemname>:4200:180.2885205:1|cms_<systemname>.CentralManagementServer.queryEx3|localhost:3064:3376.1341396:1|Clv9aDJov0qNppgGcs7bqRE145af6|||||||||||Database deadlock encountered. Ensure database is correctly tuned and that data statistics are up to date.
the final message in the log...
.\apsfactory.cpp:581:-: TraceLog message 6704
|6bfeabe8-db02-3604-0bca-6d8f8ef5dfea|2014 08 19 08:58:14:514|-0400|Error| | |E| |cms_<systemname>.CentralManagementServer| 3064|3820|| |41|0|3|0|BIlaunchpad.WebApp|<systemname>:1388:139.5236:1|BIPSDK.SessionMgr:getSession|<systemname>:11220:3743.13726:3|cms_<systemname>.CentralManagementServer.newService|localhost:3064:3820.1810951:1|Cm6vhIXsBENNl1QI42PAtf817c9|||||||||||Failed to get session id from handle and handle is not set to bypass nor server-server discovery
Hi Gary,
I've never heard of similar problem before. The log file you've included is highlighting a problem with the CMS database and not Analysis for OLAP. I would start your troubleshooting there.
Are any other products (CR, WebI) displaying odd behaviour? What is the underlying database type of the CMS?
Regards,
Philip
We had a similar issue and I was able to duplicate the resizing crash 100% of the time by pausing the Analysis panel using the "Auto Update" button on the top right, followed by changing the Layout then attempting to resize the screen. I worked with SAP on this and they fixed the issue with SP 4.1 SP5 Patch 4. *knock on wood* We haven't had it happen since upgrading! Hope this helps, if you want you can PM me with any questions.
Jonathan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gary,
I got the same error. I tested with different users and the issue resolved by changing the window zoom to 100%. If I zoom it to anything other than 100% (greater or lesser) you will get this error while resizing the panes.
Give it a try !!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I'm not sure if this is same root cause as initial issue reported in this thread, but for this zoom problem I'm currently investigating this in relation to SAP Note 2193397. It seems problem is caused by a decimal value provided by browser for mouse position when releasing button, and rendering engine expects instead an integer value.
There is another SAP Note 1496565 created by Rendering team which advises to stick to 100% zoom.
You can subscribe to Note 2193397 to be notified if a solution is found and delivered in BI Suite.
Regards,
Loic
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.