Addsolution Error
Contents |
dependent lookups created on this primary lookup field that should be deleted first. → Quick Tip: Error occurred in deployment step ‘Add Solution’ This is one of those things that error occurred in deployment step 'add solution' a feature with id I commonly forget because it doesn’t crop up too often. Sometimes when
Error Occurred In Deployment Step 'add Solution' Failed To Load Receiver Assembly
deploying a solution to SharePoint 2010 using Visual Studio, you’ll get an error like this: Error occurred in deployment
Add-spsolution
step ‘Add Solution': Error: Cannot add the specified assembly to the global assembly cache: MyCompany.Namespace.widget.dll. There are a few reasons for this. For example, OWSTimer.exe may be using the dll in question or Visual Studio may have it locked. However, rather than stopping and starting services indiscriminately and restarting Visual Studio, we can find out exactly which process is causing us grief by using the TaskList application. Open up a command prompt and type: tasklist /M MyCompany.Namespace.widget.dll You’ll see results such as: Image Name PID Modules ========================= ======== ============================================ WebAnalyticsService.exe 2040 MyCompany.Namespace.widget.dll w3wp.exe 4716 MyCompany.Namespace.widget.dll w3wp.exe 1164 MyCompany.Namespace.widget.dll Armed with this info we know what to shut down to resolve the issue. Another SharePoint mystery unravelled! by chaholl Posted on January 31, 2011 This entry was posted in Deployment, Development, SharePoint, SharePoint 2010, Tip, Visual Studio 2010. Bookmark the permalink. ← The skinny on SPPersistedObject and the Hierarchical Object Store in SharePoint 2010 SharePoint 2010 bug: The primary lookup field cannot be deleted. There are dependent lookups created on this primary lookup field that should be deleted first. → http://geekswithblogs.net/venkatx5 Venkatesh R This is Great Tip Dude. Thanks. I faced similar issue. Then I retracted the Solution. After I deploy the solution, it's getting deployed without any error. Then I found issue due to Deployment Step which created by me. I changed it to Default (which include pre-post deployment steps). It may help. Rebecca Gordon Thank you, very useful. I still had to close visual studio and restart the timer service, but this put me in the right direction Sunil Khaniya Its work for me, thanks sharing Search for: Follow Me: Twitter RSS Grab Thi
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Cannot add the specified assembly “Microsoft.Practices.ServiceLocation.dll” up vote 4 down vote favorite For a while now, me and my team having been having an issue where when we http://www.chaholl.com/archive/2011/01/31/quick-tip-error-occurred-in-deployment-step-lsquoadd-solutionrsquo.aspx try and deploy a project we very frequently end up with the error Error occurred in deployment step 'Add Solution': Error: Cannot add the specified assembly to the global assembly cache: Microsoft.Practices.ServiceLocation.dll. We get around this by restarting IIS and once we do the project will deploy fine. But now our project is getting big and deployment take a long time and it is becoming incredibly annoying having to deploy twice. So, we have decided to tackle this issue and clearly failed. http://sharepoint.stackexchange.com/questions/46286/cannot-add-the-specified-assembly-microsoft-practices-servicelocation-dll Thus, I have turned to the internet and I'm hoping someone out there might know why this happening and how we can prevent it in the future. deployment share|improve this question edited Sep 24 '12 at 18:08 asked Sep 24 '12 at 18:02 Caesar 20028 Try IISReset and then deploy, it work like a charm –user45051 Aug 12 '15 at 18:36 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted I can think of a few things, but try these for starters : Verify that your development environment and your other SharePoint servers have the exact same version of the Enterprise Library installed Check each WSP that your team is creating to make sure that it is not bundling an older version of the DLL in your WSPs Library as well. You may need to manually inspect each WSP by renaming them to .CAB and then browsing the content in Windows Explorer Make sure that you do not have an older copy of that DLL anywhere on your dev machines or on your sharepoint servers. People are notorious for manually copying troublesome DLLs to the /bin/ or /_app_bin/ of the web application If you have other older WSPs that are deployed to that farm make sure that they do not reference and include the older version of the library If you have a build server that checks and builds your WSPs then do all of the above
to deploy solution from Visual Studio: Error occurred in deployment step ‘Add Solution’: https://ljayaprakash.wordpress.com/2012/08/17/error-message-cannot-add-the-specified-assembly-to-the-global-assembly-cache/ Error: Cannot add the specified assembly to the global assembly http://stackoverflow.com/questions/5401818/deploy-dll-with-resource-files-to-sharepoint-2010-in-visual-studio-2010 cache: MyLibrary.dll. Manually uninstalling dll from GAC and Visual Studio restart fixed my issue. Also, restarted owstimer, not sure if that makes any difference. Like this:Like Loading... Related Post navigation ← Previous post Next post → Leave a Reply Cancel error occurred reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) error occurred in You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. August 2012 M T W T F S S « Jul 12345 6789101112 13141516171819 20212223242526 2728293031 C# Certifications Customization Excel Services General Google Analytics India LINQ Managed Metadata Field MOSS PowerShell Publishing Search SharePoint SharePoint 2010 Taxonomy Uncategorized User Groups User Profiles VS 2008 Web Parts WSS Archives August 2012 July 2012 June 2012 November 2011 October 2011 July 2011 May 2011 April 2011 March 2011 November 2010 April 2010 October 2009 September 2009 August 2009 July 2009 June 2009 May 2009 Recent Posts SPUtility.Redirect - Open In NewWindow Elevated Privilages in EventReceivers Error Message: Cannot add the specified assembly to the global assemblycache Enable Term Store Managerment on BlankSite MSDN Developer Training: SharePoint2013 GravatarBlog Stats 19,814 hits Search: Blog at WordPress.com. %d bloggers like this:
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Deploy dll with resource files to sharepoint 2010 in visual studio 2010 up vote 4 down vote favorite I have problem to add a assembly to my sharepoint project. I have a assembly that contains resource files for different language. I have one file for English, Utility.resx och one for Swedish Utility.sv-SE.resx. When I build it, it will be one dll for the project and one for the swedish language. The problem is when I should deploy it to Sharepoint with Visual Studio. I have added the assembly for the project to my packagefile in my sharepoint project. But when I trying to deploy it but I got the message: Error occurred in deployment step 'Add Solution': Error: Cannot add the specified assembly to the global assembly cache: Utility.resources.dll I have tried to specified both sv-SE\Utility.resources.dll and Utility.resources.dll as Location when I added the assembly i package. Note that I want to add it as assembly from project output. Anyone having an ideas how to solve this problem? visual-studio-2010 dll resources sharepoint-2010 gac share|improve this question asked Mar 23 '11 at 6:57 Daniel 213 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote This should help - http://blogs.visigo.com/chriscoulson/deploying-localized-satellite-assemblies-with-sharepoint-2010/ You have to add the resource assemblies using "Add Existing Assembly" and hard code the path to the BIN\release\ folder and NOT "Add Assembly from Project Output" for some reason... And no - you can't use bin\$(ConfigurationName) -- GAHH! share|improve this answer answered Jan 21 '13 at 17:04 Ryan 14.4k1764113 For me (VS2012 + SP2013), there was no need to hard code the path (i.e. relative path), but "Add Existing Assembly" was necessary. –kevin Dec 5 '14 at 3:07 add a comment| up vote -1 down vote Why not deploying the resource files as resx? They need to be added to the manifest.xml as "RootFiles"