Home » Community » Developer Space » Telligent Evolution Platform Discussion » Hotfix upgrade error - Couldn't resolve type 'CommunityServer.Rest.Resources.Search.ISearchService, CommunityServer.Rest' defined in 'service' attribute.

Hotfix upgrade error - Couldn't resolve type 'CommunityServer.Rest.Resources.Search.ISearchService, CommunityServer.Rest' defined in 'service' attribute.

Open Support Ticket

Call Support:
Direct: (214) 420-1337
Toll Free: (877) 522-6334

Monday through Friday
8 a.m. to 6 p.m. Central (GMT-6)

Join our Community
Details
  • 6 Replies
  • 1 Subscriber
  • Postedover 3 years ago
Options

Hotfix upgrade error - Couldn't resolve type 'CommunityServer.Rest.Resources.Search.ISearchService, CommunityServer.Rest' defined in 'service' attribute.

This question is answered
Adam Seabridge
Posted by
on Tue, Jan 26 2010 4:27 PM

Hi Support,

I recieved the hotfix: ( TC 5.0 SP1 HOTFIX (Build: 40807.9167) Our Telligent Community project is in Visual Studio and SVN so I used this article to merge the hotfix changes: http://telligent.com/support/telligent_evolution_platform/w/documentation/upgrading-from-a-previous-version-of-the-telligent-evolution-platform.aspx (dll's, pages, config files etc). 

I have also checked this article to ensure that the System.Web.Routing and System.Web.Abstractions are set Copy Local to True.

(http://telligent.com/community/developers/w/wiki/developing-on-top-of-the-telligent-evolution-platform.aspx)

However I get this error:

Server Error in '/' Application.

Couldn't resolve type 'CommunityServer.Rest.Resources.Search.ISearchService, CommunityServer.Rest' defined in 'service' attribute.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Configuration.ConfigurationErrorsException: Couldn't resolve type 'CommunityServer.Rest.Resources.Search.ISearchService, CommunityServer.Rest' defined in 'service' attribute.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace: 

[ConfigurationErrorsException: Couldn't resolve type 'CommunityServer.Rest.Resources.Search.ISearchService, CommunityServer.Rest' defined in 'service' attribute.]
   Ninject.Extensions.Xml.Handlers.BindElementHandler.GetTypeFromAttributeValue(XAttribute attribute) +211
   Ninject.Extensions.Xml.Handlers.BindElementHandler.Handle(XmlModule module, XElement element) +128
   Ninject.Extensions.Xml.XmlModule.Load() +309
   Ninject.Modules.NinjectModule.OnLoad(IKernel kernel) +59
   Ninject.KernelBase.Load(IEnumerable`1 modules) +221
   Ninject.Extensions.Xml.XmlModuleLoaderPlugin.LoadModules(IEnumerable`1 filenames) +76
   Ninject.Modules.ModuleLoader.LoadModules(IEnumerable`1 patterns) +557
   Ninject.KernelBase.Load(IEnumerable`1 filePatterns) +89
   Ninject.ModuleLoadExtensions.Load(IKernel kernel, String[] filePatterns) +37
   CommunityServer.Web.KernelFactory.CreateKernel() +206
   CommunityServer.Global.Application_Start(Object sender, EventArgs e) +36


Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053

 

Thanks in advance for the help.

 

Adam
Verified Answer
  • Alex Crome
    Posted by
    on Tue, Jan 26 2010 4:43 PM
    Suggested Answer

    Did you install the 5.5 preview APIs ?  If so, the hotfix would likely have overwritten the 5.5 preview binary, but left the ninject module configuration for the 5.5 preview API.
  • Adam Seabridge
    Posted by
    on Tue, Jan 26 2010 4:50 PM

    Hi Alex, yes we did as we wanted the v2 search endpoints. I thought it may be something to do with that so tried replacing the hotfix REST.dll with the one from the 5.5 preview but that didn't work. Where is the ninject module configuration - RestModule.config / web.config? and what do I need to change to keep the 5.5 preview / rest v2 search endpoints but keep the upgrade?

    Thanks

    Adam
  • Alex Crome
    Posted by
    on Tue, Jan 26 2010 5:14 PM

    The 5.5 REST apis are correctly configured - the CommunityServer.Rest.Resources.Search.ISearchService type was only added in the 5.5 Preview APIs .

    You mentioned you used the procedure from telligent.com/.../developing-on-top-of-the-telligent-evolution-platform.aspx for setting up your project.  If you did so, can you confirm that you updated the CommunityServer.Rest assembly in both the /bin/ directory of the web site, and the /references/ folder.  
  • Adam Seabridge
    Posted by
    on Tue, Jan 26 2010 5:32 PM

    Hi Alex, I updated this assembly in both these folders with the one from the hotfix. Is this wrong should I be using the one from the 5.5 preview instead?
  • Alex Crome
    Posted by
    on Tue, Jan 26 2010 9:07 PM
    Verified Answer
    Verified by

    If you want to use the 5.5 Preview APIs (e.g. the search endpoint), then yes.

    If you don't need the 5.5 preview apis, then you shouldn't, but you will need to revert the configuration files in /modules/ to the state from before you applied the 5.5 preview APIs  (best way to do this is to delete the modules folder, copy the folder from the original SP1 release and then apply the hotfix changes to that folder).
  • Adam Seabridge
    Posted by
    on Wed, Jan 27 2010 10:47 AM

    I now have this working, thanks Alex. One think I am not sure of is if the theme.config and the some style sheets in the /css folder need updating in our custom theme?. I noticed that the markuptranslations and some css has changed in the fiji theme.

    To help anyone else with the issue of applying the hotfix but using the REST v2 search endpoints here is what I did to get it to work:

    1) Apply the hotfix updates (I used winmerge to help do this)

    2) Replace the CommunityServer.Rest.dll in /bin with the one from the 5.5 preview

    2) Replace the RestModule.config file in /modules with the one from the 5.5 preview

    Thanks

    Adam
All Replies
  • Alex Crome
    Posted by
    on Tue, Jan 26 2010 4:43 PM
    Suggested Answer

    Did you install the 5.5 preview APIs ?  If so, the hotfix would likely have overwritten the 5.5 preview binary, but left the ninject module configuration for the 5.5 preview API.
  • Adam Seabridge
    Posted by
    on Tue, Jan 26 2010 4:50 PM

    Hi Alex, yes we did as we wanted the v2 search endpoints. I thought it may be something to do with that so tried replacing the hotfix REST.dll with the one from the 5.5 preview but that didn't work. Where is the ninject module configuration - RestModule.config / web.config? and what do I need to change to keep the 5.5 preview / rest v2 search endpoints but keep the upgrade?

    Thanks

    Adam
  • Alex Crome
    Posted by
    on Tue, Jan 26 2010 5:14 PM

    The 5.5 REST apis are correctly configured - the CommunityServer.Rest.Resources.Search.ISearchService type was only added in the 5.5 Preview APIs .

    You mentioned you used the procedure from telligent.com/.../developing-on-top-of-the-telligent-evolution-platform.aspx for setting up your project.  If you did so, can you confirm that you updated the CommunityServer.Rest assembly in both the /bin/ directory of the web site, and the /references/ folder.  
  • Adam Seabridge
    Posted by
    on Tue, Jan 26 2010 5:32 PM

    Hi Alex, I updated this assembly in both these folders with the one from the hotfix. Is this wrong should I be using the one from the 5.5 preview instead?
  • Alex Crome
    Posted by
    on Tue, Jan 26 2010 9:07 PM
    Verified Answer
    Verified by

    If you want to use the 5.5 Preview APIs (e.g. the search endpoint), then yes.

    If you don't need the 5.5 preview apis, then you shouldn't, but you will need to revert the configuration files in /modules/ to the state from before you applied the 5.5 preview APIs  (best way to do this is to delete the modules folder, copy the folder from the original SP1 release and then apply the hotfix changes to that folder).
  • Adam Seabridge
    Posted by
    on Wed, Jan 27 2010 10:47 AM

    I now have this working, thanks Alex. One think I am not sure of is if the theme.config and the some style sheets in the /css folder need updating in our custom theme?. I noticed that the markuptranslations and some css has changed in the fiji theme.

    To help anyone else with the issue of applying the hotfix but using the REST v2 search endpoints here is what I did to get it to work:

    1) Apply the hotfix updates (I used winmerge to help do this)

    2) Replace the CommunityServer.Rest.dll in /bin with the one from the 5.5 preview

    2) Replace the RestModule.config file in /modules with the one from the 5.5 preview

    Thanks

    Adam