SiebelDave
Technical User
Hello Everyone. I am having some issues with iBots and I was wondering if anyone has experienced somethig similar and what corrective actions they took to solve it.
When the iBots are executed for datasets that build very large tables, the initial iBots complete but any iBots left queued for execution fail. Here's what I see in the logs:
+++ ThreadID: 2280 : 2006-01-19 02:20:50.000
[nQSError: 77006] Siebel Analytics Web Error: Invalid iBot session ID.
Error Codes: MV5BAQPD
File: ./project/ibotapi/ibotrpcproxy.cpp, Line: 187
There is a related article in Support Web (don't remember the number offhand) but it states that this can be caused by the session timeout setting for the iBot, and can be fixed by setting certain analytics web config params - this has not worked for me, but here's the config file anyway:
Any insight/suggestions would be appreciated.
Thank You
instanceconfig.xml
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<JavaHome>D:/j2sdk1.4.2_08</JavaHome>
<CatalogPath>d:/SiebelAnalyticsData/web/catalog/JNJSiebelAnalytics.webcat</CatalogPath>
<DSN>AnalyticsWeb</DSN>
<CatalogMaxAutosaves>10</CatalogMaxAutosaves>
<Alerts>
<ScheduleServer>NCSUSRAEPHARM66</ScheduleServer>
</Alerts>
<Prompts>
<MaxDropDownValues>200000</MaxDropDownValues>
</Prompts>
<UnaccessedRunningTimeoutMinutes>750</UnaccessedRunningTimeoutMinutes>
<RPC>
<IdleTimeoutSecs>60000</IdleTimeoutSecs>
</RPC>
<ConnectionExpireMinutes>750</ConnectionExpireMinutes>
</ServerInstance>
</WebConfig>
When the iBots are executed for datasets that build very large tables, the initial iBots complete but any iBots left queued for execution fail. Here's what I see in the logs:
+++ ThreadID: 2280 : 2006-01-19 02:20:50.000
[nQSError: 77006] Siebel Analytics Web Error: Invalid iBot session ID.
Error Codes: MV5BAQPD
File: ./project/ibotapi/ibotrpcproxy.cpp, Line: 187
There is a related article in Support Web (don't remember the number offhand) but it states that this can be caused by the session timeout setting for the iBot, and can be fixed by setting certain analytics web config params - this has not worked for me, but here's the config file anyway:
Any insight/suggestions would be appreciated.
Thank You
instanceconfig.xml
<?xml version="1.0" encoding="utf-8"?>
<WebConfig>
<ServerInstance>
<JavaHome>D:/j2sdk1.4.2_08</JavaHome>
<CatalogPath>d:/SiebelAnalyticsData/web/catalog/JNJSiebelAnalytics.webcat</CatalogPath>
<DSN>AnalyticsWeb</DSN>
<CatalogMaxAutosaves>10</CatalogMaxAutosaves>
<Alerts>
<ScheduleServer>NCSUSRAEPHARM66</ScheduleServer>
</Alerts>
<Prompts>
<MaxDropDownValues>200000</MaxDropDownValues>
</Prompts>
<UnaccessedRunningTimeoutMinutes>750</UnaccessedRunningTimeoutMinutes>
<RPC>
<IdleTimeoutSecs>60000</IdleTimeoutSecs>
</RPC>
<ConnectionExpireMinutes>750</ConnectionExpireMinutes>
</ServerInstance>
</WebConfig>