5

I am getting the below mentioned error in workflow. I am using the fresh copy of Tridion 2013 SP1.

Tridion.ContentManager.TypeRegistration.WorkflowScriptTypeRegistrationException: Workflow Script Type with Name 'VBScript' was not found in the configuration file.

0
4

That's a simple one - you installed Tridion 2013 SP1 without Legacy support. SDL Tridion 2013 introduced a new model for workflow that does not use VBScript for automatic activities ("Bundle Workflow").

If you need VBScript support, you need to re-run your installer with LEGACY_VISIBLE=TRUE (as described in this answer), and then select to enable Legacy features in the feature selection screen of the installer.

2
  • I am not using the Bundle workflow concept. I am using the same old workflow automatic activity. Do i still need to install the legacy pack ? – Jitender sharma Mar 25 '14 at 11:49
  • If you need VBScript support, you need the Legacy Pack. If you only use Bundle Workflows, then you don't need the Legacy pack. – Nuno Linhares Mar 25 '14 at 11:53
0

In the case you've switched on the 'enforce workflow' at a schema level you will also need to ensure you select an appropriate (and by appropriate I mean none-legacy) workflow such as described here.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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