Admin and Office client connection problems

[Former Member]

Hi there,

I have just come across a problem that I can't seem to fix, and could use some help.

I have built a test application set on a newly-built test server (a VM actually), and this morning I finished my dimensions and launched the Office client in Excel for the first time.

Instead of logged me straight in (as it should, the admin client, Office client, and the entire server and application are on the same machine), it started the Connection Wizard.

I get past the point of entering my ID and password, and it gives me this error:

"The system cannot connect to the <HTTP address of the server> Application Server. Verify that you have specified a valid application server name, or see if the Application server is unavailable at this time."

I ran the diagnostics (both client and server), restarted IIS, restarted the machine, uninstalled and reinstalled the clients, all to no avail; I still get the same message. Oddly, I was able to get into the admin client with no problems until now, but now this gives me the same error.

Even more irritating, I backed up my appset and moved it to a different (up to now fully-working) machine, and now the same things has happened there too!

Is it possible that an appset can cause this problem? Or something unrelated? I can't connect to the other 2 appsets I have on this second machine now, either.

I can, however, get into this appsets via the web client, if that helps at all!?!

I am running this on Windows Server 2003, SQL 2005, Office 2003 and BPC version 7 SP4.

Any ideas would be most welcomed!

Thanks a lot,

Jason

[Former Member]

Tried that,not working still....

had the same problem while connecting to the BPC admin,when I used .NET framework3.5 SP1 I was able to connect to the BPC admin,but again fails when I try to connect via excel...

The error is :

The system cannot connect to the application server....verify u hav specified valid app server name....

Automation Error(Assembly:OsoftComLibclient.dll object:osoft.consumers.common.AuthHelper.ThickClientHelper)

Plz help..??

[Former Member]

This is a known issue with the logging in via the Connection Wizard, the root causes of this behavior maybe :

A corrupted APPINFO.XML.

A corrupted file in the users PC registry.

A missing MS fixes for MS Office installation.

[Former Member]

Hi there,

If you are still having a problem, you can try renaming the users' folder on the server too.

I had this problem once before, and went onto the server and renamed (you can delete if you wish) each of problem users' folders in C:\BPC\Data\Webfolders\<appset>\<APP>\PRIVATEPUBLICATIONS\<Username>

I renamed this folder in all 4 of our apps, and it seemed to work.

Maybe try that and see if it helps?

Cheers,

Jason

[Former Member]

Hi,

you can try to delete C:\Documents and Settings\<username>\Documents\PC_MS(or Outlooksoft) and then retry to logon BPC.

Hope this helps you.

Regards

massimo

[Former Member]

I am also facing the same problem...

"application server not available....."

without logging into BPC how can you goto

eTools > Client Options and then click "clear local application information".

To get the etools option we need to logon first... and that is where we face this probleb....can you give more clarification on this..??

Anyone Plz help...

[Former Member]

Jason,

I didn't see if you said the Osoft landing page was working? (http://servername/osoft)

So what happens when you put the ip address, short name, and long names in the connection wizard?

Can you get to the Default Website?

Is SSAS 2005 running?

What happens if you use the installation id?

[Former Member]

Hi James,

I can get to http://<servername>/Osoft without any problems, and can make "web admin" changes to the appsets, I just can't get into either client.

I've just tried connecting with every variation of name and IP address and still no luck. I am logging onto the machine (and BPC) with the install ID - this is just a test environment, so I haven't set any other users up.

Once thing I stupidly forgot to mention though (I ws very tired last night!) - I built the offending appset in a BPC 7 SP4 environment, then when I backed up and restored it to another environment, I then had to update the other application as it was only "straight" version 7. Would the update have anything to do with it?

Just seems a bit to much of a coincidence to me.

Thanks a lot,

Jason

PS. And Analysis Services is running normally!

Edited by: Jason Maidment on Aug 25, 2009 10:06 AM

[Former Member]

My problem has been solved.

I opened my PC and went to eTools > Client Options and then clicked "clear local application information".

Seemed to do the trick! I didn't just solve this, I was just doing some housekeeping and realised I hadn't posted an update.

Hope this helps someone.

Jason