I am getting the following message on some 4.1 reports when I try to Refresh them in WebIntelligence:
Automation error BusObj server process raised an Automation exception (This error may be caused by a bad password)
Does anybody have an idea what might be causing this?
I can create another report from the same universe and it works fine.
Greg Mills
Conoco Inc.
(580) 767-5597 ETN 442-5597
s-greg.mills@usa.conoco.com
Listserv Archives (BOB member since 2002-06-25)
We have experienced this error also when trying to refresh full-client reports in WebI 2. BusinessObjects told us it was related to the security privileges of the user you are logging in as. The user must have the BusinessObjects module enabled as well as WebIntelligence.
We also had to go through and limit the BO commands we disabled (all we disabled were 6 commands). This did fix a lot of our “Automation Error” problems but it did not resolve them completely. Is your company releasing (or have already released) version 2 of WebI? If so, have you experienced “Communication Errors”, “Cannot Bind to Report Server Errors”, or “Bad Login Parameters”? We are having a difficult time even testing because of all the errors we have returned. Thanks!
I am getting the following message on some 4.1 reports when I try to Refresh them in WebIntelligence:
Automation error BusObj server process raised an Automation exception (This error may be caused by a bad password)
Does anybody have an idea what might be causing this?
I can create another report from the same universe and it works fine.
Greg Mills
Listserv Archives (BOB member since 2002-06-25)
We have experienced this error also when trying to refresh full-client
reports in WebI 2. BusinessObjects told us it was related to the
security privileges of the user you are logging in as. The user must
have the BusinessObjects module enabled as well as WebIntelligence.
We also had to go through and limit the BO commands we disabled (all
we disabled were 6 commands). This did fix a lot of our “Automation
Error” problems but it did not resolve them completely. Is your
company releasing (or have already released) version 2 of WebI? If
so, have you experienced “Communication Errors”, "Cannot Bind to
Report Server Errors", or “Bad Login Parameters”? We are having a
difficult time even testing because of all the errors we have returned. Thanks!
I am logging in as the general supervisor!!!
Yes I have been getting all those errors - not consistent though. It seems to be mostly related to the Report Server.
Greg Mills
Conoco Inc.
(580) 767-5597 ETN 442-5597
s-greg.mills@usa.conoco.com
Listserv Archives (BOB member since 2002-06-25)
There is a default setting that is wrong within WebIntelligence that will cause this error.
Under WIREPORTSERVER the life time document setting must be GREATER than or EQUAL to the Session time out setting under WIQTMANAGER. I have made this setting to be 1800 sec (30min) in both settings and this error has disappeared.
The only other way you will get this error or “cannot bind to server” is when the user is browsing a report and his session times out. Business Objects does not handle this error very well. What happens here is the user is prompted to log back in and everything looks good until he clicks on a tab or index. This error will show up. Nothing any of us can do, I have reported it to Business Objects and hopefully it gets into a maintenance release.
Any other tuning questions give me a call. I went through 2 weeks of hell trying to tune this product (WIREPORTSERVER is critical) but everything works great now. I am still trying to get an explaination on SHUTDOWN delay and MAX ACTIONS at SHUTDOWN.
Sincerely,
Thomas Nather
Penske Logistics
email: Tom.Nather@Penske.com
Ph: 216-765-5787
Fax: 216-765-5666
“Mills, S. Greg” S-GREG.MILLS@USA.CONOCO.COM 10/28 3:57 PM >>>
I am getting the following message on some 4.1 reports when I try to Refresh them in WebIntelligence:
Automation error BusObj server process raised an Automation exception (This error may be caused by a bad password)
Does anybody have an idea what might be causing this?
I can create another report from the same universe and it works fine.
Listserv Archives (BOB member since 2002-06-25)
X-cc: Tom Nather Tom.Nather@penske.com
Under WIREPORTSERVER the life time document setting must be GREATER than or EQUAL to the Session time out setting under WIQTMANAGER. I have made this setting to be 1800 sec (30min) in both settings and this error has disappeared.
The WIQT does not have session timeout. Are you referring to Max Active Time? WISESSION has a session timeout.
Greg Mills
Conoco Inc.
(580) 767-5597 ETN 442-5597
s-greg.mills@usa.conoco.com
Listserv Archives (BOB member since 2002-06-25)
Check page 110 in the systems administrator guide. This session time setting controls when WIQTMANAGER shuts down. When this happens it has a bug that doesn’t allow it to start back up effectively. By setting this equal to LIFE TIME will allow all session activity to clear at the same time.
WIQTMANAGER is like to traffic cop for running the system access to different reports.
Sincerely,
Thomas Nather
Penske Logistics
email: Tom.Nather@Penske.com
Ph: 216-765-5787
Fax: 216-765-5666
“Mills, S. Greg” S-GREG.MILLS@usa.conoco.com 10/29 10:19 AM >>>
Under WIREPORTSERVER the life time document setting must be GREATER than or EQUAL to the Session time out setting under WIQTMANAGER. I have made this setting to be 1800 sec (30min) in both settings and this error has disappeared.
The WIQT does not have session timeout. Are you referring to Max Active Time? WISESSION has a session timeout.
Greg Mills
Conoco Inc.
(580) 767-5597 ETN 442-5597
s-greg.mills@usa.conoco.com
Listserv Archives (BOB member since 2002-06-25)
Sincerely,
Thomas Nather
Penske Logistics
email: Tom.Nather@Penske.com
Ph: 216-765-5787
Fax: 216-765-5666
“Mills, S. Greg” S-GREG.MILLS@USA.CONOCO.COM 10/29 1
The WIQT does not have session timeout. Are you referring to Max Active Time? WISESSION has a session timeout.
Listserv Archives (BOB member since 2002-06-25)
I’ve installed WebIntelligence 2.5 on our Sun Solaris server. I can get the login screen fine, but when I enter a user name and password I get the message
Cannot access network layer.
The bomain.key file is stored in the LocData directory on the server. I can get into the repository database from the server directly. I called the problem in to tech support on Friday and have yet to hear from them. Can anyone help?
I’m the supervisor and yes, I did give myself access to WebIntelligence in supervisor. We are using Sybase 11.9, open client 11, Sun Solaris 2.7, Business Objects 5.0.1 WebI 2.5.1. We did not install BOManager as we don’t want to deal with an NT server. And we know that that means we can’t access full client reports and that’s ok. But my understanding was that you didn’t need to have the BOManager installed if everyone was using WebI.
I know what to do in the full client when I get this message but with WebI I’m stumped.
Thanks.
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu
Listserv Archives (BOB member since 2002-06-25)
Did you install the database client before WebI? I know I had a problem logging in because the database client was not installed before WebI.
Jodie
Listserv Archives (BOB member since 2002-06-25)
Debbie,
I had similar problem but I am using Oracle V 7.3. Check the following things:
(a)Check the server setting to make sure it is set up to NT/challenger response.
(b)Check the service pack in place.
©Check to see how the servers operating system was set up. (D)Make sure that the same BOMAIN KEY is also located in locdata under WIQT. (E)Make sure that the tnsnames.ora file has the name of the data base and the IP address in place.
Hope this helps.
Aris
Listserv Archives (BOB member since 2002-06-25)
Aris,
Since I’ve installed WebI on a unix box most of your suggestions probably aren’t relevant. However, the suggestion about the bomain.key file existing in a LocData directory under the wiqt directory is a possibility. I looked in the wiqt directory and didn’t see a LocData folder there at all. The only place where a LocData directory exists is under the main webi directory. When you installed webi, did the LocData folder under wiqt get created automatically or did you have to go in and create it yourself. I didn’t see anything in the installation documentation about copying the bomain.key file to another directory. Not sure why you would need a duplicate of the file.
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu
Listserv Archives (BOB member since 2002-06-25)
Debbie
Just as a translation from Oracel to Sybase … Do you have the correct entry in your INTERFACES file on the WEBI server to access the security domain? If you can use ISQL to connect to the security domain database then you should be able to get past this error.
One other thing to check would be the middleware. I recently had problems that generated the infamous “Unable to access Network Layer” message and it was due to trying to use Oracle 8 middleware insteads of SqlNet 7.3.
Check to see if there was a recent upgrade to Sybase middleware.
Mike McErlain
At 03:25 PM 2/14/2000 -0800, you wrote:
Aris,
Since I’ve installed WebI on a unix box most of your suggestions probably aren’t relevant. However, the suggestion about the bomain.key file existing in a LocData directory under the wiqt directory is a possibility. I looked in the wiqt directory and didn’t see a LocData folder there at all. The only place where a LocData directory exists is under the main webi directory. When you installed webi, did the LocData folder under wiqt get created automatically or did you have to go in and create it yourself. I didn’t see anything in the installation documentation about copying the bomain.key file to another directory. Not sure why you would need a duplicate of the file.
Debbie Kelly
Listserv Archives (BOB member since 2002-06-25)
Mike,
I got into our Sybase repository database using isql successfully, so I know the interfaces file is ok. I’ve logged a case with Business Objects tech support, but I have little hope of hearing from them any time soon. They seem to be totally backed up.
I’m wondering if this might have anything to do with the BOManager. I have not installed it because it requires an NT server. We’d rather not have to put anything on ours. We just planned on not letting people access full client reports.
Any other ideas?
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu
Listserv Archives (BOB member since 2002-06-25)
That should be the problem - make sure the bomain key is under the WIQT folder
Brent
(D)Make sure that the same BOMAIN KEY is also located in locdata under WIQT.
(E)Make sure that the tnsnames.ora file has the name of the data base and
the IP address in place.
Hope this helps.
Aris
Listserv Archives (BOB member since 2002-06-25)
Aris is right… We had consultants here way back when, and the process for setting up the server was always install Webi, install BO, copy tnsnames, copy bomain key to BO and Webi…
Not sure why either, but they can both exist on their own - that is the only reason I see for 2 keys…
Brent
Since I’ve installed WebI on a unix box most of your suggestions probably aren’t relevant. However, the suggestion about the bomain.key file existing in a LocData directory under the wiqt directory is a possibility. I looked in the wiqt directory and didn’t see a LocData folder there at all. The only place where a LocData directory exists is under the main webi directory. When you installed webi, did the LocData folder under wiqt get created automatically or did you have to go in and create it yourself. I didn’t see anything in the installation documentation about copying the bomain.key file to another directory. Not sure why you would need a duplicate of the file.
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu
Listserv Archives (BOB member since 2002-06-25)
Kelly,
The location for the Bomain key in "WEBI is C:\program files\webintelligence\wiqt\locdata\bomain.key.
If you don’t have a bomain key there copy the one from the BO directory.
Aris
Listserv Archives (BOB member since 2002-06-25)
Sorry I meant Debbie Kelly,
Listserv Archives (BOB member since 2002-06-25)
Debbie:
Since your installing on Solaris, did you run the mainkey.sh script to create the BoMain.key file? Also check the env to ensure that the Sybase middleware path is defined. The methhod of creating the connection to the repository is different than the Windows NT version.
I hope this helps.
Ketan
Listserv Archives (BOB member since 2002-06-25)
Debbie
One other process you can try is to recreate your BOMain.key file using the safe recovery technique and see if there is a middleware issue. As I may have mentioned I recently received the same message and it was caused by using the wrong middleware connection. In my case it was Oracle. Once I used the correct version on the middleware I was able to connect.
I’m not certain about the BOManager on the NT server. We have a NT server for our Broadcast Agent set up and we also had to install the WebI piece to use BCA although we do not use WEBI here.
Hope this helps.
Mike McErlain
McErlain Consulting
MikeMcErlain@Netscape.net
(408)378-4442 Home Office
(408)799-1795 Cell
At 04:40 PM 2/14/2000 -0800, you wrote:
Mike,
I got into our Sybase repository database using isql successfully, so I know the interfaces file is ok. I’ve logged a case with Business Objects tech support, but I have little hope of hearing from them any time soon. They seem to be totally backed up.
I’m wondering if this might have anything to do with the BOManager. I have not installed it because it requires an NT server. We’d rather not have to put anything on ours. We just planned on not letting people access full client reports.
Any other ideas?
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu
OR search: Mail to listserv@listserv.aol.com, ‘search a_phrase in BUSOB-L’ Unsubscribe: Mail to listserv@listserv.aol.com, ‘unsubscribe BUSOB-L’
Listserv Archives (BOB member since 2002-06-25)
Thanks everyone for your suggestions, but I’m beginning to think the problem is not with the network layer/repository connection. The bomain.key file works fine on my full client install so I don’t think a safe recovery is going to do it. I can login to the repository database from the Sun/Solaris machine that is our web server and where WebIntelligence is installed fine.
When I use the URL that includes the index.html file as the entry to WebIntelligence I get the welcome screen, but when I click on the login button I get a not found message giving a strange directory and file name that looks more like windows than unix. One of the directories names includes a ! in it. When I go in through HomePage.html I again get the welcome screen. I click on the login button, get the login window, enter my userid and password and click ok I get the Cannot access network layer message.
I’m wondering if there is a problem with 2.5.1 given that another lister seems to be having the same kind of problem.
I called tech support on Friday about this, but have yet to get even a callback from them to discuss in detail what the problem is.
Has anybody out there installed WebI 2.5.1 for Sun/Solaris successfully and has it up and working? I’d like to know what you did.
Thanks,
Debbie Kelly
Museum Informatics Project
University of California, Berkeley
dkelly@socrates.berkeley.edu
Listserv Archives (BOB member since 2002-06-25)