If you've ever tried to start a CDO Workflow project using Office Workflow Designer and encountered the infamous Can Register Workflow error, you're not alone. I've seen users with that error a few times so far and their problem seems to be the same in each case. The most helpful hint is not the one you get from Office Workflow Designer, but the one in the Application event log on your Exchange server. Chances are, your event log will tell you that Enforce Access Restrictions are not enabled. If that's the case, You need to drill into your COM Configuration settings and click the properties on your CdoWfEvt.EventSink.1 and go to the Security Tab and click the checkbox to enforce component-level access restrictions.
Here are some other helpful troubleshooting hints for Workflow problems:
- Verify that you can access and are an Owner of the Public Folder to which you are trying to publish the workflow. Verify that you can access the folder using OWA by navigating to http://<server>/public/<foldername> and that the public folder is "Homed" on that server.
- Make sure you have the Can Register Workflow role and the Priviledged Workflow Author role explicitly.
- Verify that NT System\Authority also has Priviledged Workflow Author
- Make sure that Enforce Access Restrictions is turned on on both the Workflow Event Sink and CdoWfEvt.EventSink.1 items.
- Verify that your Workflow Event Sink component is set to use the identity of a domain user who
- Is a domain user
- Has a mailbox on the same server.
- Is in the Can Register Workflow and Priviledged Workflow Authors roles (explicitly)
- is in the Exchange Domain Servers AD group
- In Exchange System Manager, drill into the HTTP Protocol on your server and right click on Public to go to Properties. Make sure that Basic Authentication is Checked and that Scripts and Executables are enabled.
Hopefully one of these troubleshooting steps can help you be able to create Workflow projects successfully!