GeertLarsen


I have "succesfully upgraded" ( ) our SQL2005 from standard to Enterprise version.
Before, following set worked like a charm:

CREATE SET CURRENTCUBE.[Now CY]
AS strtomember("[00 - Time].[00 - H - Calendar].[Day Name].&[" + format(now(),"yyyyMMdd") + "]");

But when I process the cube now, I get this error:

Error 1 MdxScript(Sales) (58, 74) The '[now]' function does not exist. 0 0

It seems like the reference to Visual Basic has been lost somehow
Curiously following calculated member works, even it also uses now()

CREATE MEMBER CURRENTCUBE.[MEASURES].[Now]
AS now(),
FORMAT_STRING = "yyyyMMdd",
VISIBLE = 1;

Any suggestions
please ;-)

/ geert larsen

denmark




Re: Error on using VB in calculated members AFTER stepping up to Enterprise version ??

Deepak Puri


Can you reproduce this problem in Adventure Works Enterprise Edition Another thing to try is the qualified name: VBA![Now]()





Re: Error on using VB in calculated members AFTER stepping up to Enterprise version ??

GeertLarsen

Hello Deepak
Thanks for your reply
unfortunately the VBA![Now]() did not work
(And I have not installed the AdventureWorks )

BUT I have investigated a little further in the Assemblies and found that ie. the VBAMDX
is registred in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdvbanet.dll
But this directory is empty
Now the file(s) are situated in C:\Program Files\Microsoft SQL Server\MSSQL.6\OLAP\bin\

I have tried to copy the files and re-register (regsvr32 msmdvbanet.dll)
but I get this error:
C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdvbanet.dll was loaded, but the DllRegisterServer entry point was not found.
This file can not be registered.

I hope this may give you (and then me) a hint

tia
/ geert larsen
denmark






Re: Error on using VB in calculated members AFTER stepping up to Enterprise version ??

Mosha Pasumansky

Well, msmdvbanet.dll is not a COM server, therefore you cannot register it with regsvr32. There is something that went wrong during setup or upgrade, and the problem with VBA might not be the only one. I recommend reinstalling from scratch.




Re: Error on using VB in calculated members AFTER stepping up to Enterprise version ??

GeertLarsen

Complete un- and reinstall solved the problems *NOT FUNNY*

Thanks for advice

/ geert larsen

denmark