VBA - Setting SessionMgr on 64-bit/Office 2010 ActiveX error

Hi,

We have a Windows server that is being retired, via which we have a couple of Excel VBA macros docs that we use on a consistent basis. We have a new Windows virtual machine setup with our BO Client Tools and MS Office.

However, the same macros that work on the old server do not work on the new server.

Environments:
Old - Win2003, 32-bit, Excel 2003, BO Enterprise 12.0 client tools
New - Win2008, 64-bit, Excel 2010, SAP BO Enterprise XI 4.0 client tools
Both - Using the same Excel macro docs that are stored on our team sharedrive
Our BO - BO 4.1

The VBA Reference libraries have been remapped accordingly, and we now get the following:
Run-time error ‘429’; ActiveX component cannot create objects

The error highlights the 2nd line of this code:
Dim oSessionMgr As CrystalEnterpriseLib.SessionMgr
Set oSessionMgr = New CrystalEnterpriseLib.SessionMgr

As per some other BOB posts, I have tried changing the 2nd line to:
Set sessionmanager = CreateObject(“CrystalEnterprise12.SessionMgr.1”)

…with no luck. I tried removing the 12 and .1, changing the 12 to a 14 and removing the .1 also.

On the attached pics, you can see that on the new server, (2) libraries are “14.0” vs. “12”…Framework Library and InfoStore Library. I also tried copying the “12” versions from my older server onto a separate directory on the new server, then remapping those two VBA references to them, but even when all my VBA references are to 12.0 the same issue happens.

I suspect that the root of the issue is the 64-bit environment.

Has anyone been able to use SessionMgr successfully on a 64-bit box?

Any assistance would be great.

Thanks!!
OldServer VBA References.jpg
NewServer VBA References.jpg


Andrea_ajs :us: (BOB member since 2002-08-27)

Hi Andrea.

I have same problem now, did you have any solution?


crazybii (BOB member since 2015-02-20)

Hi,

Unfortunately, no solution yet. I’ve had to go back to running my macros locally on my 32-bit laptop vs. our server.

If you come across a solution or correct syntax, please go ahead and post it here. :slight_smile:


Andrea_ajs :us: (BOB member since 2002-08-27)

I neither don’t have solution. The problem is not because of Window 64bit ( I using window 7 64bit enterprise) but it’s cause of Office 2010.

office 2010 not support CreateObject like office 2007.


crazybii (BOB member since 2015-02-20)