Developer forum

Hi Martin,

Usually, when the providers are missing, that indicates that the assemblies are not all there. You should verify that all Dynamicweb assemblies, especially Dynamicweb.Indexing.Lucene.dll, are present in the bin folder and the same version as each other.

With regard to not being able to delete your repos, can I get you to delete all folders inside the /Files/System/Repositories and try creating a new repository? If that does not work, there might some permission issues with the Repositories folder.

- Jeppe

Hi Jeppe,

I've allready checked this, before posting and all the DLL for this version of dynamicweb is present. 

When i open the "Add instance" dialog i get these error in the Console

Failed to load resource: the server responded with a status of 404 (Not Found)
http://*/Admin/Api/maaTest2/testThis-index/_sys_status Failed to load resource: the server responded with a status of 404 (Not Found)
http://*/Admin/Api/maaTest2/testThis-index/_sys_instance_types Failed to load resource: the server responded with a status of 404 (Not Found)
http://*/Admin/Api/maaTest2/testThis-index/_sys_build_types Failed to load resource: the server responded with a status of 404 (Not Found)
http:/*/Admin/Api/maaTest2/testThis-index/_sys_build_actions Failed to load resource: the server responded with a status of 404 (Not Found)
http://*/Admin/Api/maaTest2/testThis-index/_sys_extension_types Failed to load resource: the server responded with a status of 404 (Not Found)
angular.js:8380 POST http://*/Admin/Api/maaTest2/testThis-index/_sys_status 404 (Not Found)

The last call (angular.js:8380 POST http://*/Admin/Api/maaTest2/testThis-index/_sys_status 404 (Not Found))
keeps firing every 2-3 seconds

maaTest2 is the repository and testThis-index is the index, it looks like, to me, that the repository and index creation aren't creating all the files that are needed?

It seems that the browser is trying to access to old routes for the WebAPI. Try clearing your browser cache. That should solve the issue.

- Jeppe

That didn't solve the problem, still making the same calls.

Is it possible to set the routes of the api?

I have the App_Start with a WebApiConfig in my VS solution, but i looks like the standard setup from the solution creation.

No, it's not possible to set the routes as they are defined in a RouteConfig inside the application. Can you send me a link to the site and I'll take a look? If you don't want to publish the link here, you can send it to me here: jea@dynamicweb.dk.

- Jeppe

Hi, any solutions on this, I have the same problem now after upgrading to 8.7.0.1 from 8.6.1.19 - the provider is missing 

Is your web.config is in sync with the one from Dynamicweb application?

Yes I just copied a new one to be sure, the funny thing is that my search still works in the frontend but i can't touch the index/query/facet it in the backend. The index missing the provider and the query and facet interface is full of empty dropdown boxes.

I just changed the IIS to run directly on the Application(8.7.0.1) folder but it made no difference

Hm, it is not the search that does not work - the reason you get the 404s is a problem with the MVC routes.

Is your Global.asax custom? If not, copy the global.asax from Dynamicweb application - if it is, make sure you have all the Application_* methods routed to Dynamicweb.Frontend.GlobalAsaxHandler.Application_* methods. Do you have your own MVC routes?

Hi, Nicolai I'm not sure your answer is for this thread :) I have no 404 and no MVC. 

Can this missing provider be related with the bug 18325 ?

Whenever this happens, you need to verify that all assemblies from the target version is copied into the local bin folder -- do a manual copy to make sure. Then you need to clear the browser cache. Clearing the cache is important!

This is related to MVC in the sense that we use routes to handle async operations in the UI, and this issue usually occurs because there is a mismatch between the expected route (in the code) and the actual route (in the aspx/js files).

- Jeppe

Hi, Jeppe as I wrote earlier I changed the IIS to running directly on the downloaded Application 8.7.0.1 folder (just to eliminating sources of error) so no local bin here.. I tryed with a new browser but it made no difference. 

Hi Kim

We need access to the solution to do more. You see nothing in the select boxes because MVC is not working - usuallly because of a messed up web.config or global.asax. If you load a profiler before entering the window, you would see the 404s.

Also ensure your app pool is integrated.

Hi Nicolai,
I know this is a late replay, but I talked with a colleague who had the "issue" marked as a bug with #18325 see case 112775 for history, and that was before I tried my upgrade. Mybe this can be the and of this thread :)

18325 has nothing to do with the new indexing. The issue in this thread is regarding MVC routes that are not good.

Hi Nicolai

Now we have the problem with missing repositories again. I have tried all suggested things to do from this thread, but still with no luck. Will you take a look at it? The site with the problem is hosted at Host Nordic. 

Hi Lars

We are looking into this. I'm waiting for an access to the server from HN, should be there first thing in the morning.

BR Nicolai

Hi Lars

We have been looking at this all morning - we have a copy of the site installed on our development servers etc. Our findings untill now is that it has something to do with that specific server (2008). We have it working in our development and test environments. We have reproduced the error with other installations on the same server. So it is not solution specific.

So now we are finding out why or what is the issue. Will keep you posted.

BR Nicolai

Hi Nicolai

Thanks for your answer and work-around on the problem.

Hi Nicolai,

We have the same issue on a server - can you please try to upload the changed web.config file?

Best regards, Anders

Hi Anders

Must be this part:

<handlers>
      <remove name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" />
      <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />
      <add name="globalsettings.xml.aspx_*" path="globalsettings.xml.aspx" verb="*" type="System.Web.HttpForbiddenHandler" preCondition="integratedMode,runtimeVersionv4.0" />
      <add name="Globalsettings.aspx_*" path="globalsettings.aspx" verb="*" type="System.Web.HttpForbiddenHandler" preCondition="integratedMode,runtimeVersionv4.0" />
      <add name="ecom.xml.aspx_*" path="ecom.xml.aspx" verb="*" type="System.Web.HttpForbiddenHandler" preCondition="integratedMode,runtimeVersionv4.0" />
      <add name="updates.xml.aspx_*" path="updates.xml.aspx" verb="*" type="System.Web.HttpForbiddenHandler" preCondition="integratedMode,runtimeVersionv4.0" />
      <add name="_sys_crm_report_xml.aspx_*" path="_sys_crm_report_xml.aspx" verb="*" type="System.Web.HttpForbiddenHandler" preCondition="integratedMode,runtimeVersionv4.0" />
      <add name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" path="K*.K" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness32" responseBufferLimit="0" />
      <add name="ExtensionlessUrlHandler-ISAPI-4.0_64bit" path="K*.K" verb="GET,HEAD,POST,DEBUG" modules="IsapiModule" scriptProcessor="%windir%\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll" resourceType="Unspecified" requireAccess="Script" preCondition="classicMode,runtimeVersionv4.0,bitness64" responseBufferLimit="0" />
    <remove name="ExtensionlessUrlHandler-Integrated-4.0" /><remove name="OPTIONSVerbHandler" /><remove name="TRACEVerbHandler" /><add name="ExtensionlessUrlHandler-Integrated-4.0" path="*." verb="*" type="System.Web.Handlers.TransferRequestHandler" preCondition="integratedMode,runtimeVersionv4.0" /></handlers>

You cannot be sure it works without doing stuff in IIS as well.

BR Nicolai

Thanks for quick reply - the section is exact the same from a standard DW 8.9.

Is it the right part and the right file? :-)

Not sure...

As this thread also touches upon, it probably is an issue in IIS. So you have to fiddle around with it until it works... There is another thread in her on the same/similar issue - from Kevin.

BR Nicolai