Hi,

It is not exactly the same error but check out the following KB article for instructions on how to exclude the directory in site W from sharepoint: http://kb.k2workflow.com/articles/kb000068.aspx

Essentially sharepoint tries to control any sites that are under the root sharepoint site so you have to configure sharepoint to ingore any directories that have custom applicatons.

I hope this helps.
-Eric

---

Thanks for the tip, but unfortunately I get the same error after following the proposed solution.

Any other ideas?

Thanks,

---

Check and make sure that the virtual directory is using the same application pool as sharepoint.

You might als try resetting IIS if you haven't already.

-Eric

---

Yes they are and I did reset IIS.

Thanks,

---

Try adding the following to the web.config file for your application:

<configuration>
<system.web>
<httpHandlers>
<clear />
<add verb="*" path="*.aspx" type="System.Web.UI.PageHandlerFactory, System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
</httpHandlers>
<httpModules>
<add name="UrlAuthorization" type="System.Web.Security.UrlAuthorizationModule" />
<add name="Session" type="System.Web.SessionState.SessionStateModule" />
</httpModules>
<!-- Enable Session for the pages in your application -->
<pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="true" />
<trust level="Full" originUrl="" />
</system.web>
</configuration>

---

I got it working from the WSS server... Thanks... In other words, when I call my URL (http://WSS_Server/WebApplication/TestForm1.aspx) from the WSS server itself in IE, where "WebApplication" is a virtual directory under default website (WSS), my form does show up perfectly (Which was not the case previously). So at least I'm moving forward.

Now when I try the same URL from a workstation, I get this error in IE:
"NT AUTHORITYANONYMOUS LOGON does not have permissions to start the process"

Thanks,

---

I am glad you are making progress!

Since the WSS server is a seperate server from the K2 server you will need to enable kerberos authentication.

The reason it works from the SharePoint server is because your NTLM credentials can be directly passed to the K2 server. When you connect using NTLM from a client machine your credentials are passed to SharePoint but SharePoint cannot then delegate your credentials to the K2 server. Delegation of credentials between servers can only occur when Kerberos authentication is used.

Here is a link to a KB article on how to setup K2 for Kerberos and another link for how to set WSS up for Kerberos.

http://kb.k2workflow.com/Articles/KB000123.aspx
http://support.microsoft.com/?kbid=832769

---

I already have K2 working with Kerberos... I will give it a shot in trying to get WSS working with Kerberos also!

Thanks again,

---