Profile Picture

Error after migrating to Sharepoint 2010

Posted By rpeddeti 8 Years Ago
Rated 4 stars based on 1 vote.
Author
Message
rpeddeti
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)Forum Newbie (3 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 1, Visits: 6
We are trying to upgrade our Sharepoint from wss 3.0 to Foundation Server 2010. We are using Calendar Plus and List Filter Plus from Kwizcom. After are done with initial configuration, we added and deployed both the solutions on the server. We activated both the webparts at Farm Level. Now, after converting the site from WSS 3.0 to 2010, only Calendar Plus works fine but not the List Filter Plus. When try to access the list that has List filter Plus, it gives the following error...

"Could not load file or assembly 'KWizCom.Sharepoint.WebParts.ComboListFilter, Version=2.0.0.1, Culture=neutral, PublicKeyToken=30fb4ddbec95ff8f' or one of its dependencies. The system cannot find the file specified."

Any help is appreciated..

Thanks, 

Ramesh Peddeti
Igor
Posted 8 Years Ago
View Quick Profile
Supreme Being

Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)

Group: Administrators
Last Active: 3 Years Ago
Posts: 415, Visits: 592

Hi,

The web part dll version was changed in 2010. Please add the following lines toyour web.config. Please make sure that everything is case sensitive.

1.   Add the SafeControl entry:
<SafeControlAssembly="KWizCom.Sharepoint.WebParts.ComboListFilter, Version=2.0.0.1, Culture=neutral, PublicKeyToken=30fb4ddbec95ff8f" Namespace="KWizCom.SharePoint.WebParts.ComboListFilter" TypeName="*" Safe="True" />

2.   Add the binding redirect entry:
<dependentAssembly>
<assembly Identityname="KWizCom.Sharepoint.WebParts.ComboListFilter" publicKeyToken="30fb4ddbec95ff8f" culture="neutral" />
<bindingRedirect oldVersion="1.0.0.0-20.0.0.00" newVersion="4.0.0.0" />
</dependentAssembly>


You find attached WSP file which resolves the issue withoud manual config editing.



Igor,
KWizCom 
Attachments
Edited
8 Years Ago by Igor
setsch
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 5, Visits: 27
We also have a problem that during the upgrade from SharePoint 2007 to SharePoint 2010 the List Filter Plus Web Parts stopped working.

New added Filter Plus Web Parts work as expected, only the existing Web Parts show the following message:

Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type could not be found or it is not registered as safe.

 

List Filter Plus Web Part Version on SharePoint 2007: 3.2.00

Upgraded to List Filter Plus Web Part Version on SharePoint 2010: 14.2.00

 

What’s the reason for this error. Do we have to upgrade to 4.2.00 first?

The solution above won’t work for us.

 

Thanks,

Best Regards
Stephan Setscheny
Igor
Posted 8 Years Ago
View Quick Profile
Supreme Being

Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)

Group: Administrators
Last Active: 3 Years Ago
Posts: 415, Visits: 592
Hi,

The error happened because version of "KWizCom.Sharepoint.WebParts.ComboListFilter.dll" was changed 2.0.0.1 to 4.0.0.0.

Unfortunately SharePoint saves the assembly link in the page. You can edit each page in SharePoint designer and change the version number.

Could you please explain why the solution with web.config configuration will not work for you.

Igor,
KWizCom 
Edited
8 Years Ago by Igor
setsch
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 5, Visits: 27
Hi Igor,

I have tried your web.config entries and i have also modified it to include our installed version:

      <SafeControl Assembly="KWizCom.Sharepoint.WebParts.ComboListFilter, Version=3.1.0.0, Culture=neutral, PublicKeyToken=30fb4ddbec95ff8f" Namespace="KWizCom.SharePoint.WebParts.ComboListFilter" TypeName="*" Safe="True" />

      <dependentAssembly>
        <assembly Identityname="KWizCom.Sharepoint.WebParts.ComboListFilter" publicKeyToken="30fb4ddbec95ff8f" culture="neutral" />
        <bindingRedirect oldVersion="1.0.0.0-20.0.0.00" newVersion="4.2.0.0" />
      </dependentAssembly>


 

After these changes and restarting IIS there was no change.
(new WPs work and migrated WP stopped working)

Thus there are a huge amount of list filter web parts instances used, changing / reconfiguring all of them  on our sharepoint environment manually won't be a solution for us.

Version installed on SharePoinr 2007: 3.1.0.0

Version installed on SharePoinr 2010 after migration: 4.2.0.0

Thanks,
Best regards

Stephan
jkuter
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 2, Visits: 6
I have this exact same problem and adding the old safe control and redirect do not seem to solve the issue.  I have uninstalled and reinstalled and that also does not solve the problem regardless of whether I use the ps1 script or install the wsp manually.  I also do not seem to be able to add my licenses in.  When I click on the licensing link it does not detect that I have this product installed.
Igor
Posted 8 Years Ago
View Quick Profile
Supreme Being

Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)Supreme Being (415 reputation)

Group: Administrators
Last Active: 3 Years Ago
Posts: 415, Visits: 592
Hi,

You do not need to change the version number of the DLL. You need to use exactly the same string which we have in our example with version "2.0.0.1". Do not change anything.

Also, please check that you have latest version of KWizCom foundation deployed on each web application including Central administration web application. You need deploy it in Central administration separately of other web applications.

Igor,
KWizCom 
setsch
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)Forum Newbie (5 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 5, Visits: 27
Hi,

1)

- We have installed the newest version of the foundation.

- Modified the web.config for the web application

- iisreset

-> same result (new WPs work and migrated WP stopped working)

"Web Part Error: A Web Part or Web Form Control on this Page cannot be displayed or imported. The type could not be found or it is not registered as safe. "


2)

-newest foundation version is installed

- reset the the web.config (without your fix)

- deploy our fix .WSP

- iisreset

-> same result (new WPs work and migrated WP stopped working)


thanks

Stephan Setscheny
austriamicrosystems AG
jkuter
Posted 8 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)Forum Newbie (2 reputation)

Group: Forum Members
Last Active: 8 Years Ago
Posts: 2, Visits: 6
I solved the problem.  The issue was that the product seems to need to be installed on every machine even if its not a front-end (which is not the default for a product like this and even your installer doesn't install it this way).  Our central admin is not a web front end (6 server farm) and this product would not work until I installed both the foundation package and the web part package on my CA web application.
stephanic
Posted 5 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: Awaiting Activation
Last Active: 5 Years Ago
Posts: 1, Visits: 2
Hi,
The error that you are getting is due to the corruption of SharePoint files. However to repair this, you need to use SharePoint file repair tool as this tool is very powerful and is used to repair the error of SharePoint. This repair tool is very helpful and restores all the corrupt data from damaged SharePoint file.


Similar Topics