Error Processing Cube on 64-bit server

We are in the process of migrating to a new 64-bit server. We changed the data provider for the cube from "Microsoft OLE DB Provider for Oracle" to ".Net Provider\OracleClient Data Provider" for the 64-bit and when we try and process this cube, we get the following error:

Errors in the high-level relational engine. The following exception occurred while the managed IDataReader interface was being used: Value was either too large or too small for a Currency..

This very same cube was able to process on the 32-bit server just fine. The field that the error refers to is a number(28,0) in oracle and is fully populated in the database. I set up a simple cube on my laptop and if I cut the value in the field down to 15 numbers it will process correctly. I have maxed out the precision of the number type to 38 as well and I am still getting the error when more than 15 numbers are populated in a single field.

Does anyone know what is keeping the cube from processing with ODP.Net when it is processing fine with the other data provider?

This has to do with the conversion of that data type in the Oracle Provider, Analysis Services wouldn't be generating that error, it would be just passing it on. I would consult with Oracle to find out more regarding it.

Is the data type in the dimension or Fact for this field Currency? If so you may want to change it in AS so there is no conversion.

David

Error open/accessing a MSSQL Linked Server

Hi!

Im having the fallowing error when I try to open/access a linked server
Error:
Error 7302: Could not create an instance of OLE DB provider 'MSOLAP.2'.
OLE DB error trace [Non-interface error: CoCreate of DSO for MSOLAP.2 returned 0x80004005].

I have already tried to create the server using SEM and also with SQL syntax in ISQLW.
Code:
EXEC sp_addlinkedserver
@.server='LINKED_OLAP',
@.srvproduct='',
@.provider='MSOLAP.2',
@.datasrc='MyServerName.MyDomain,
@.catalog='MyDataBase'

Im allowed to create the linked server but I cant use it.

Information:
OS: Windows 2003EE
SQL: MSSQL 2000 + SP3a
MDAC: MDAC2.8 rtm

Thanks,
Paulowhen referring to objects defined in a linked server, you should use the convention:
servername.databasename.userid.object|||That it's not the problem for sure.|||I'd see if any of Microsoft's (http://search.microsoft.com/search/results.aspx?view=msdn&st=b&na=82&qu=0x80004005+OLAP&s=1) ideas help.

-PatP|||Thanks, but none of the links apply to.

Paulo

Error on link Servere

HI,
I am getting below error on link server. And the performance between
link server is really pathatic.

Executed as user: NT AUTHORITY\SYSTEM. OLE DB provider 'SQLOLEDB'
reported an error. Execution terminated by the provider because a
resource limit was reached. [SQLSTATE 42000] (Error 7399) [SQLSTATE
01000] (Error 7312) OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ICommandText::Execute returned 0x80040e31: Execution terminated by the
provider because a resource limit was reached.]. [SQLSTATE 01000]
(Error 7300).Hi,

It looks like that's a generic error. Pretty hard to troubleshoot..

Please read the following for more info on this.. Also, if/when you've
got more details (using the trace) and you're still experiencing issues
please post the query you're executing and the volume of data being
transferred between the servers..

http://support.microsoft.com/default.aspx?scid=314530

Greg

Error on creating cube file from Excel 2003, AS 2005

Hi,

I tried to create a cube file in Excel 2003. Data source is SSAS 2005.

On the last step of wizard I get the following error:
Microsoft OLE DB Provider for Analysis Services 2005:
Query (3,2) Parser: The syntax for 'DIMENSION' is incorrect.

Seems like a bug. Is there any fix?
Tried to search google, found nothing...

SQL Server 2005 Developer SP2
Excell 2003 SP2

Thx for any tip...

certainly sounds like a bug. Can you provide a repro' that the product team can look at?

thanks,

Bala.

Error on creating cube file from Excel 2003, AS 2005

Hi,

I tried to create a cube file in Excel 2003. Data source is SSAS 2005.

On the last step of wizard I get the following error:
Microsoft OLE DB Provider for Analysis Services 2005:
Query (3,2) Parser: The syntax for 'DIMENSION' is incorrect.

Seems like a bug. Is there any fix?
Tried to search google, found nothing...

SQL Server 2005 Developer SP2
Excell 2003 SP2

Thx for any tip...

certainly sounds like a bug. Can you provide a repro' that the product team can look at?

thanks,

Bala.

Error of Microsoft OLE DB Provider for SQL Server

Hi All:

I have a ASP page which use external DLL load data from SQL 2000 server, but it keeps give me error as following:

HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

Microsoft OLE DB Provider for SQL Server (0x8004000)

the line cause the error is as:

<%

dim newRS

dim visiter = Server.CreateObject("ExternalDLL.visit")

newRS = visiter.enews.getENews

%>

visit and enews are all class file inside ExternalDLL.

any body can help me out what's wrong with my page? the external DLL and sqloledb.dll are both registed on the machine.

Your help is great appreciate

Regards

Echo

Echo,

"Microsoft OLE DB Provider for SQL Server (0x8004000)" is related to the forum. However, for ASP related issue, you might want to check ASP forum as well.

|||

Hi !

As another poster said, this is defintely not a SQL Server related problem. You are loading an external DLL which does some SQL stuff and which has probably a bug inside or is not configured probably. So ask the vendor how to trace or how to configure this the right way. If you have no support, you can go the long way, tracking the users which try to login to SQL Server (if the server is configured the right way for this application) and see what statement are executed for the server. As I said thats the long way using the profiler. :-(

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Error msg in OLD DB provider

I use OLE DB to call a series of stored procedures to add records to databas
e
tables within one transaction. I got the following errors:
Description: Cannot create new connection because in manual or distributed
transaction mode.
Source Description: Microsoft OLE DB Provider for SQL Server
The stored procedures are very simple. I do not try to create a new
connection explicitly. Neither do I try to use distributed transactions. The
only thing that might be a little complicate is I use ISequentialStream to
write blobs to table fields. The error msg confuses me. Any one has ideas
about this?Anothing might be interesting is that the error happens randomly and if I se
t
a break point in the code where it crashed and wait for a while before the
rest of stored procedures, you will not see the error and the save is
successful.
Roy
"Roy" wrote:

> I use OLE DB to call a series of stored procedures to add records to datab
ase
> tables within one transaction. I got the following errors:
> Description: Cannot create new connection because in manual or distributed
> transaction mode.
> Source Description: Microsoft OLE DB Provider for SQL Server
> The stored procedures are very simple. I do not try to create a new
> connection explicitly. Neither do I try to use distributed transactions. T
he
> only thing that might be a little complicate is I use ISequentialStream to
> write blobs to table fields. The error msg confuses me. Any one has ideas
> about this?|||The URL below mayhelp.
http://support.microsoft.com/defaul...&NoWebContent=1
Thomas
"Roy" wrote:

> I use OLE DB to call a series of stored procedures to add records to datab
ase
> tables within one transaction. I got the following errors:
> Description: Cannot create new connection because in manual or distributed
> transaction mode.
> Source Description: Microsoft OLE DB Provider for SQL Server
> The stored procedures are very simple. I do not try to create a new
> connection explicitly. Neither do I try to use distributed transactions. T
he
> only thing that might be a little complicate is I use ISequentialStream to
> write blobs to table fields. The error msg confuses me. Any one has ideas
> about this?

Error message SQL server

I have recently installed SQL server and keep getting this
error message. Error #-2147467256 (Description: connection
failure) (Source: Microsift OLE DB Provider for SQL Server)
(Module: basEH.bas)(Procedure:
General_EHProcessContinuousEVENTS)
Can anyone spread a bit of light on what to do?
Thanks,
MikeHi:
It does not seems that it is a error of SQL or OLEDB, I guest it is
caused by (Module: basEH.bas)(Procedure:
General_EHProcessContinuousEVENTS).
According the Error #-2147467256, I look up KB and get the article list
below.
http://support.microsoft.com/defaul...KB;en-us;270061
It says thet this error caused by
"The callee (server [not server application]) is not available and
disappeared; all connections are invalid. The call did not execute. "
So I suggest you check thw connect string and see if it work.
Best Wishes
Wei Ci Zhou

Error message SQL server

I have recently installed SQL server and keep getting this
error message. Error #-2147467256 (Description: connection
failure) (Source: Microsift OLE DB Provider for SQL Server)
(Module: basEH.bas)(Procedure:
General_EHProcessContinuousEVENTS)
Can anyone spread a bit of light on what to do?
Thanks,
MikeHi:
It does not seems that it is a error of SQL or OLEDB, I guest it is
caused by (Module: basEH.bas)(Procedure:
General_EHProcessContinuousEVENTS).
According the Error #-2147467256, I look up KB and get the article list
below.
http://support.microsoft.com/default.aspx?scid=KB;en-us;270061
It says thet this error caused by
"The callee (server [not server application]) is not available and
disappeared; all connections are invalid. The call did not execute. "
So I suggest you check thw connect string and see if it work.
Best Wishes
Wei Ci Zhou