New Posts New Posts RSS Feed: IIS BOS Cannot Find valid License
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

IIS BOS Cannot Find valid License

 Post Reply Post Reply
Author
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454
Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Topic: IIS BOS Cannot Find valid License
    Posted: 08-Nov-2010 at 1:00pm
I believe I have followed all the steps. I am setting up in IIS 6.0.
bin
 
I get the following error:
Cannot find a valid license key in any domain model assembly.

bin consists of:

BOS.dll
DomainModel dll
Server dll
IdeaBlade.Core
IdeaBlade.EM
IdeaBlade.EM.Server
IdeaBlade.EM.Web
IdeaBlade.Linq
IdeaBlade.VAlidation
 
root consists of (both setup from the template):
Global.asax
Web.Config
//not sure if these are needed i have got conflicting info from the forums
EntityServer.svc
EntityService.svc
 

 
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454
Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 08-Nov-2010 at 3:55pm
I believe I got it to run.
 
But now I run into the following error:
 
Type conflict:  the DefaultManager is currently of type EntityManager
 

This error occurs when I try and do EntityManager.SaveChanges();

 

Also, I am using port 80 not 9009 due to a failure of communication on port 9009.

Back to Top
kimj View Drop Down
IdeaBlade
IdeaBlade
Avatar

Joined: 09-May-2007
Posts: 1391
Post Options Post Options   Quote kimj Quote  Post ReplyReply Direct Link To This Post Posted: 08-Nov-2010 at 6:03pm

When deploying to IIS you should use port 80, or port 443 if using SSL.   We use port 9009 in DevForce almost as a legacy:  if you deploy the BOS as a console or Windows service you need to assign a port, and 9009 seemed like a good default.  In the n-tier and Silverlight templates we continued setting 9009 as a default, but I want to emphasize it is not in any way a DevForce requirement that you use this port.  In IIS you can't use it, and non-IIS deployments aren't that common in DevForce 2010. 

The *.svc files - you do not need them if you've registered a VirtualPathProvider in the global.asax.  If your global.asax is the standard one from our templates or samples then the registration will be done.  If you keep the .svc files you need to make sure they contain the correct information (which you can find in our Deployment samples).  It's far easier to just remove the .svc files altogether.
 
The Type conflict error - the first EntityManager created by default becomes the DefaultManager.  You can also explicitly set the DefaultManager.   On the server side you should NEVER use the DefaultManager, since that would mean you're sharing the EM among threads.   If you see the error on the client that means that "something" already created a non-subtyped EntityManager.  If you're using the new Business Application templates, that "something" would be the AuthenticationManager, which uses an EntityManager for login processing.  If you're not using the BAT, then it's hard to say what happened.  To fix the problem, explicitly set the DefaultManager to your sub-typed EM first thing in your code.
Back to Top
orcities View Drop Down
Senior Member
Senior Member
Avatar

Joined: 28-Aug-2007
Location: United States
Posts: 454
Post Options Post Options   Quote orcities Quote  Post ReplyReply Direct Link To This Post Posted: 09-Nov-2010 at 3:24pm
tx
Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down