ReportPortal
ReportPortal
Home | Profile | Register | Active Topics | Members | Search | FAQ
Username:
Password:
Save Password
Forgot your Password?

 All Forums
 ReportPortal General Forum
 Report Portal General Issues
 Error xFaultcode ->Server xFaultstring -> Unknown
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Jared

New Zealand
9 Posts

Posted - 01/11/2005 :  16:14:17  Show Profile  Reply with Quote
I have an urgent issue that I would appreciate any help with.

I have set my Report Portal URL to be:

http://exonet-main.tpp.ac.nz/reportportal

My XML for Analysis Server is:

http://exonet-main.tpp.ac.nz/xmla/msxisapi.dll

When I attempt to design an OLAP report I get the error:

Error xFaultcode ->Server xFaultstring -> Unknown server error xfaultsoap ->

Why is this error still occurring when I have made sure the servername in the above URL and XML is the same???

I have ensured my datasource file is correct as well:

<DataSourceName>exonet-main.tpp.ac.nz</DataSourceName>
<DataSourceDescription>Microsoft Analysis Server 2000 on local machine</DataSourceDescription>
<URL>http://exonet-main.tpp.ac.nz/xmla/msxisapi.dll</URL>
<DataSourceInfo>Provider=MSOLAP.2;Data Source=exonet-main.tpp.ac.nz</DataSourceInfo>
<ProviderName>Microsoft XML for Analysis</ProviderName>


HELP!!!

admin

1645 Posts

Posted - 01/17/2005 :  06:27:03  Show Profile  Reply with Quote
The latest security pack breaks MSXML 4.0 on some installations. Please reinstall MSXML and XML for Analysis SDK and test XMLA with the Sample Application.
Go to Top of Page

Morten3456

2 Posts

Posted - 02/13/2005 :  08:44:24  Show Profile  Reply with Quote
I'm having the same problem, even after re-install of MSXML and XML for Analysis SDK.

could it may be some rights problem somewhere? kind of lost!

/Morten

Edited by - Morten3456 on 02/13/2005 08:48:15
Go to Top of Page

admin

1645 Posts

Posted - 02/18/2005 :  21:29:46  Show Profile  Reply with Quote
If you still cannot access XMLA with the XMLA SDK Sample Application please try to post the problem on the Microsoft XMLA forum: news://microsoft.public.data.xmlanalysis
Go to Top of Page

admin

1645 Posts

Posted - 02/18/2005 :  21:37:48  Show Profile  Reply with Quote
If you still cannot access XMLA with the XMLA SDK Sample Application please try to post the problem on the Microsoft XMLA forum: news://microsoft.public.data.xmlanalysis
Go to Top of Page

chuckdobbs

20 Posts

Posted - 10/11/2005 :  13:45:33  Show Profile  Reply with Quote
Did you get this worked out. I'm running WINSRV2003 with SQL2000 with the same issue. It really looks like a permissions prob. I'm not as familar with analysis services auth as SQL.
Go to Top of Page

admin

1645 Posts

Posted - 10/13/2005 :  21:02:32  Show Profile  Reply with Quote
Can you please provide a list of all ISAPI filters you have installed on your web server?
Go to Top of Page

apathak123

USA
4 Posts

Posted - 03/06/2008 :  08:46:27  Show Profile  Reply with Quote
I was having the xfaultcode problem. Now I am getting "Class not registered" problem. I have installed and reinstalled the XMLA packages a few times. Any insight into this?
Go to Top of Page

admin

1645 Posts

Posted - 03/06/2008 :  12:11:10  Show Profile  Reply with Quote
Please try to re-register msxisapi.dll manually using regsvr32
Go to Top of Page

apathak123

USA
4 Posts

Posted - 03/11/2008 :  09:16:21  Show Profile  Reply with Quote
When I try to manually register msxisapi.dll I get the following message:

"msxisapi.dll was loaded, but the DllRegisterServer entry point was not found. The file can not be registered."

What does this mean? Does this have any bearing on the problem we are having?

Thanks!
Go to Top of Page

apathak123

USA
4 Posts

Posted - 03/11/2008 :  10:29:51  Show Profile  Reply with Quote
Our problem is resolved - it seems the correct setting was not being used for msxisapi.dll in IIS. One of the accounts that has full priviledges and works from our Windows 2000 web server does not work from the Windows 2003 server. Once that change was made, things were working.

So, the the main thing is to make sure that XMLA SDK connects as a user
with permission to the catalogs.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
ReportPortal © 2000-2002 Snitz Communications Go To Top Of Page