Component Links not working in 64 bit mode

Brief Summary: We are using Tridion 2009 SP1, however we never used .NET templating, we are still using R5 concept i.e. (VBScript, XSLT etc), we are using broker database for our linking etc.

Our Tridion Server/Presentation Server/services are running perfectly on 32 bit environment/mode, our IIS is running on 32 bit mode. Everything is running perfectly.

Problem: We recently decided to move all our server to 64 bit mode, so now everything moved to 64 bit (IIS, Tridion Server/Services etc), everything is working perfectly except the Component Links. Due to that we again moved our Tridion services to 32 bit mode as well as IIS to 32 bit mode and then component links start working

Error: When all the things are running on 64 bit mode, we are getting component link resolving error and getting below error when it trying to resolve the component.

Error Failed to resolve component uri tcm:233-218990 while called from ComponentLink.ResolveLink on /english/index.aspx
... EGIT.CCIT.Tridion
... Object reference not set to an instance of an object.
... at EGIT.CCIT.Tridion.COM.ComponentLink.GetLink(String pageURI, String componentURI, String componentTemplateURI, String attributes, String text, Boolean textOnFail, Boolean anchor)
... at EGIT.CCIT.Tridion.Broker.LinkResolver.ComponentUrl(String pageUri, String uri, String componentTemplateUri, String publicationUri)
...
09:50:58.90 Error Error in Core Tridion call
... netrtsn
... Attempt to load JVM failed on native side
... at Codemesh.JuggerNET.JvmLoader.Load(Boolean bAcceptPreloaded)
... at Codemesh.JuggerNET.JvmLoader.Load()
... at Codemesh.JuggerNET.JavaClass.init()
... at Codemesh.JuggerNET.JavaClass.get_JObject()
... at Codemesh.JuggerNET.JavaMethod.init()
... at Codemesh.JuggerNET.JavaMethod.get_MethodPtr()
... at Codemesh.JuggerNET.JavaMethod.get_Handle()
... at Codemesh.JuggerNET.JavaMethod.CallObject(JavaProxy jpo, JavaMethodArguments args)
... at Com.Tridion.Linking.ComponentLink..ctor(Int32 publicationId)
... at Tridion.ContentDelivery.Web.Linking.ComponentLink..ctor(Int32 publicationId)
... at EGIT.CCIT.Tridion.COM.ComponentLink.GetLink(String pageURI, String compo开发者_开发百科nentURI, String componentTemplateURI, String attributes, String text, Boolean textOnFail, Boolean anchor)

Please suggest!!

Thanks.

Best Regards, Manu

---

Manu,

You can use VBScript templates (thought it is a good idea to start moving off this platform anyway) in your CMS backend and 64-bit on the front end, if your front end is .NET or Java.

What you cannot do is use COM on the Front-end (even if being called from .NET) and be on 64 bit, since the Tridion COM-based linking API is 32 bit only.

The .NET linking libraries and the Java linking libraries are 32 and 64 bit compatible, but not the COM libraries.

Hope this helps

N

---

Which version Java did you install on the presentation server? Is it 64-bit? Try the 32-bit version of Java. Otherwise try the 64-bit version.