we’ve got a cube in th SQL Server 2005 Analysis and created a universe based on the OLE DB connection. The universe was created automatically and works.
One excepition: The automatically generated universe created the date containing objects as character. So we changed it to date. Then the error “driver not capable WIS 10901” emerged, when using it in Webi.
We changed in the advanced tab of the object to the date format in the database, in this case german so dd.mm.yyyy, later the hh.mm.ss supplement at the end of format strring did work the same ways. Using this, there is no error message, however there is no data either. However we know there is data in the database, using the object as character formated dimension provides results.
We used the SQL Server Profiler and recorded the mdx query. Runing it directly in the SQL Serverdid work, as well when we used the date format for the object.
So probably the result is created by the query but cannot be re-converted by the universe to the right format. Any ideas?
Sorry, this is a special kind of question. Thanks in advance.
the BO version is edge series 3.0. OLE DB Analysis 9 is used. Meanwhile I’ve seen in the supplement documentation about using olap cubes, that it just supports string and number values. But this this supplement documentation is for the R2 version.
The error is probably the data delivery back from the database, as the profiler has shown, the mdx query is right and works. The return dataset in the end is then misinterpreted by the universe, therefore the “not capable” message. But this is just a presumption.
This documents shows - as far as I can tell - that there’s been some development in using olap universes (OLAP universes best practices September 2008). However it mainly explains creating filters and using the @functions there.
We are getting the same error when using SAP BW. DEfinately on Date “type” objects we run a query and get the “driver not capable” error. A mate has got around this by re-creating the connection and pointing the universe to that and i thinnk it worked. A long process.
(BOB member since 2008-02-25)
(BOB member since 2006-09-08)