I've been asked to help move a website from one server to another by a client of mine due to the supplier of the website and existing hosting going bust, meaning they are unreachable.
I've copied the files across to the new hosting via FTP and imported a database backup.
When I try and view the site, I receive the following error message:
Parser Error Message: Could not load file or assembly 'Telerik.OpenAccess, Version=2010.1.312.2, Culture=neutral, PublicKeyToken=7ce17eeaf1d59342' or one of its dependencies. The system cannot find the file specified.
It cites the following line of the web.config file:
<add assembly="Telerik.OpenAccess, Version=2010.1.312.2, Culture=neutral, PublicKeyToken=7CE17EEAF1D59342" />
Is there anything special that needs doing on the hosting in order to get this running (e.g. any Telerik software that needs installing or any specific configuration changes)? Or is simply having the relevant files in the bin directory enough?
I've had a search for the above error messages but haven't been able to find anything that helps - probably due to me having a relatively limited understanding of .NET applications and hosting.
The following 'Telerik' files exist in the bin directory of the site:
Telerik.OpenAccess.35.Extensions.dll
Telerik.OpenAccess.35.Extensions.xml
Telerik.QuickStart.dll
Telerik.QuickStart.dll.refresh
Telerik.Reporting.dll
Telerik.Reporting.Interfaces.dll
Telerik.Reporting.Processing.dll
Telerik.ReportViewer.WebForms.dll
Telerik.Web.UI.dll
Telerik.Web.UK.dll.refresh
Telerik.Web.UI.XML
Any help would be gratefully received,
Chris
3 Answers, 1 is accepted
Based on the scenario and the exception you are receiving I would assume that OpenAccess is installed locally on the source server, but it is not installed or a different version is installed on the target server. Please correct me if I am wrong in this statement.
The reason behind such error is that while most of the OpenAccess assemblies are referred directly as DLL files, the Telerik.OpenAccess assembly is deployed on the development machine in the Global Assembly Cache. For this reason it is not copied locally, and if you move your application to a machine where the GAC does not contain the assembly, the application will not be able to find it.
The best possible solution is to start deploying the assembly to the server. An alternative would be to install the same version of OpenAccess on the target server as well, but I wouldn't recommend this approach.
In case you already have a wrong version of OpenAccess installed on the server, you should uninstall it.
For more information regarding OpenAccess deployment you can take a look at this article.
Kindly let us know if my assumptions were not correct or in case the described steps are not resolving your issue.
Ivailo
the Telerik team
Rank 1
Thanks for the reply.
I haven't installed any software on the target server, and it's a completely new (to the site) hosting platform so if this is a non-standard library/package, it's unlikely to be on there.
I uploaded all the files referenced in that help article to the /bin directory but that hasn't helped.
When you say 'install' do you simply mean to copy relevant files to the application's bin directory as I have done so, or is there an installer that needs running by the server administrator?
If so, what would I need to instruct the host to do to install this on the platform? The only download I've found for this software seems to be for developers.
Finally, is there a way to find out what version of OpenAccess the application uses?
Thanks for your help,
Chris
First let me clarify - it will be best if you don't install OpenAccess on the target server. It should be enough to fix the references and place the proper version of the OpenAccess assemblies in the /bin folder, as you did. Installation of OpenAccess ORM on the production environment is a workaround rather than a best practice.
There are two possible causes of the reference problem - one is that some of the projects that are referring to the OpenAccess assemblies is bound to a wrong version of them - this is the place to start checking. The next thing is to verify that all the OpenAccess assemblies are exactly the same version as mentioned in the web.config.
On a development environment, you can check the version of OpenAccess that is installed if you go to the Telerik menu in Visual Studio -> OpenAccess -> About. On the source server for your migration, you can just see the properties of the Telerik.OpenAccess.35.Extensions.dll.
To summarize, there is no additional installations that need to be made for the migration, and we should just ensure that the proper assemblies are provided so that your web site is up and running on the target server. Let us know if those checks do not lead to any improvement and we will explore other possibilities.
Ivailo
the Telerik team