D
dmitchell40
I am having issues with the OWC10 PivotTable component. When I run the
following C# console program on my production server:
static void Main(string[] args)
{
OWC10.PivotTable _pivotObj = null;
_pivotObj = new OWC10.PivotTableClass();
_pivotObj.ConnectionString = @"Provider=MSOLAP.2;Data
Source=http://.../msolap;Initial Catalog=...;user
id=...;password=...;Persist Security Info=True";
try
{
Console.Write(((object[])_pivotObj.DataMemberStrings)[0]);
}
catch (Exception e)
{
Console.Write(e.ToString());
}
}
I receive the following COMException:
System.Runtime.InteropServices.COMException (0x80004005):
Error HRESULT E_FAIL has been returned from a call to a COM component.
at OWC10.PivotTableClass.get_DataMemberStrings()
This code works on my development server with the same connection
string, but does not seem to work on the production server.
Both servers have:
- OWC10 with SP3
- Windows Server 2003 with SP1
- MDAC 2.8
The console program is executed using an adminstrator account, so I
don't think it's a security-related issue.
Any ideas as to why this exception is happening?
following C# console program on my production server:
static void Main(string[] args)
{
OWC10.PivotTable _pivotObj = null;
_pivotObj = new OWC10.PivotTableClass();
_pivotObj.ConnectionString = @"Provider=MSOLAP.2;Data
Source=http://.../msolap;Initial Catalog=...;user
id=...;password=...;Persist Security Info=True";
try
{
Console.Write(((object[])_pivotObj.DataMemberStrings)[0]);
}
catch (Exception e)
{
Console.Write(e.ToString());
}
}
I receive the following COMException:
System.Runtime.InteropServices.COMException (0x80004005):
Error HRESULT E_FAIL has been returned from a call to a COM component.
at OWC10.PivotTableClass.get_DataMemberStrings()
This code works on my development server with the same connection
string, but does not seem to work on the production server.
Both servers have:
- OWC10 with SP3
- Windows Server 2003 with SP1
- MDAC 2.8
The console program is executed using an adminstrator account, so I
don't think it's a security-related issue.
Any ideas as to why this exception is happening?