4

'Error: Class does not support Automation or does not support expected interface'

I am getting above error while publishing pages from a certain publication alone. Also, I am unable to open any pages from that pulication, nor able to see the versioning history, where used. When I try to open the page, the same error occurs and for the rest of the actions the window freezes on displaying loading.

What could be the possible issue? It looks more like a template issue than a publishing/workflow issue to me. Thanks for your help!

Improve this question
4
  • If you cannot even open the items in that Publication I would try to restart the server and if the issue remains contact Customer Support. Sounds to me like either you have a simple caching issue or something is seriously wrong.
    – Bart Koopman
    Commented Apr 16, 2013 at 13:53
  • It happens only on a certain publication and when published with a default page template, it is working fine. Templates are localized from a parent publication.
    – Keirthana
    Commented Apr 16, 2013 at 14:00
  • @Keirthana: It looks like you are using vbscript templates. If yes, it might be causing the issue.
    – Siva Charan
    Commented Apr 16, 2013 at 14:10
  • Did you check the available Hot Fixes on SDL Tridion World? In my sheen memory, it was a known issue and there was a hotfix available for the same, though I am not 100% sure. May be you can go through various hot fixes available on SDL Tridion World and try applying the one if found any related one.
    – Pankaj Gaur
    Commented Apr 16, 2013 at 14:48

1 Answer 1

Reset to default
5

Basically - the message is telling you that COM can't instantiate the class you've asked for. This can be caused by lots of things. Maybe a library you are using has been badly installed or corrupted.

Check all the examples of CreateObject() in your template code. Ensure in each case that the class specified can be instantiated on the machine without Tridion. (A simple VBScript run from the command line with cscript should do). In this way you can isolate the issue, and perhaps figure out what to reinstall.

Improve this answer
1
  • Indeed the issue was in the VBScript template. One of the references that were used was not properly resolved. Thanks for your answers
    – Keirthana
    Commented Apr 17, 2013 at 6:11

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.