Last month I started working for a company to finish a project for them. The visual studio solution file had a single project that took around 5 minutes to deploy just from how bulky it had gotten; additionally there is a lot more work to be done. To save myself development time and just organize the project more efficiently I created a new solution fragmented to several projects.
After setting up the event receivers and features to affect only their pieces, it was time to deploy. The main home page is deployed to SERVER/_layouts/name/filename.aspx, so I’ll check there first (I know, deploying your home page to _layouts is silly, but I inherited it and after several recommendations to rebuild using SharePoint standards they still want to use this file).
Uh oh, seems like I got an error. The good news is the page is found and SharePoint is attempting to parse the file. So at this point I run through some basic steps for what could be the cause.
- reset iis
- manually uninstall and remove the farm solutions and redeploy with a clean slate
- deactivate/activate features
- check assembly to ensure a program is not holding it, the “Last Modified” should match the time deployed. (See pic below)
Looks like the correct “last modified”… wait, what’s the Public Key Token I am using in my file? Looks like when i created the new project the project was assigned a new Token. I switched out the old token with the new token in all places in my project and redeployed which did the trick.
This is an error I have seen a few times now. I attempt to open Cisco VPN client and nothing happens. After several minutes i get a popup with the following message:
After some digging around and ignoring advice to re-install just about everything I was finally able to fix it.
In the start menu make a search for Services which will have a gear symbol next to it. Open that up and find Cisco Services, right click and click Enable. Now it should start up no problem.
Another issue I have seen:
Sometime Cisco VPN virual device will fail to enable when you log on. Normally this is switched on when the client application attempts to connect to the VPN. If the device is unable to be switched on you will get an error that it was not able to connect to the network. To solve this issue type “Device Manager” into the search box in the start up menu and open Device Manager. Open Network Adapters, right click on Cisco Systems and enable this device. That should enable it to work.
If you attempt to reconnect and after a few seconds the Cisco device switches itself to disabled, go back to Services and find Internet Connection Sharing service. Change the start up type from automatically to manual to finally allow the connection.
http://www.lamnk.com/blog/vpn/error-56-the-cisco-systems-inc-vpn-service-has-not-been-started/Continueing with cisco vpn, need to start up service in services
One common problem with modern web development is displaying a consistent look of your site cross platform. CSS3 provides developers some pretty incredible design tools, but without a modern web browser many users will not see them. Suddenly your polished modern looking website looks like a middle school kid hacked html together. Luckily there are some tools out there which provide CSS3 functionality to IE6,7,8 users.
There are a couple tools out there which work well, but the one i chose to use is PIE. The steps to using it are simple:
- Download PIE.zip from the getting started page and unpack the contents.
- Upload the PIE.htc file somewhere on your server.
- Reference it somewhere in your CSS rule with the following line: behavior: url(path/to/pie_files/PIE.htc);
A complete guide can be found on their site under Documentation -> Getting Started.
Unfortunately SharePoint developers will require a few more steps. By default SharePoint 2010 blocks the .htc file from running on the site. This is a security measure to prevent malicious scripts from being run through the UI. There are two options to allow access to PIE.htc. The first is to disable the security which prevents the file from running or to install the file in _layouts.
If you are only allowed to deploy a sandbox solution you will not be able to deploy PIE.htc to _layouts. So the next option is to reference it from the style library. To get this to work you must either be in permissive file mode or add the MIME type “text/x-component” to the “AllowedInlineDownloadedMimeTypes” list for each web application using PIE. To enable Permissive File Mode go to Central Administration -> Application management –> Manage Webapplications –> General settings. Find the option called “File Browser Handling” and change this to “permissive”. Additionally this will allow PDF files to open in browser on your site.
The second option is to add the MIME type to the Web Application using PowerShell using the following code:
<code>$webapp = Get-SPWebApplication <name or URL of web app>
This will add functionality to each Web Application which will be running PIE. Making this change will also let you store the PIE.htc inside a document library.
Today I opened up a branch of code in TFS for the first time in a week to find this error.
This is an error i have seen in the past. From what i can understand the old .dll file is being used by some unknown process. SharePoint sometimes gets “stuck” on different files, and this is one of them. Since some process has the file opened Visual Studio cannot overwrite it, and the error is a result. Here is how I fixed the issue.
- Open up a windows explorer and navigate to C:\windows\assemblies.
- Find the ProjectName.dll file which is causing the error and delete this from the folder.
- Restart the machine.
- Rebuild the project and deploy.
This time I got a second error after I fixed the .dll error:
An error occurred in deployment step ‘Retract Solution’: The language-neutral solution package was not found
This error was new to me, so I did a quick search online and found this article: http://pankajspoint.blogspot.com/2011/01/error-occurred-in-deployment-step.html
The solution is to open up SharePoint Management shell and run the command “(get-spsolution mysolution.wsp).Delete()”. This should take care of the error and you should be able to redeploy it.
Hey all! This is my first blog so bear with me as i go through a painful learning period over my first few dozen (hundred?) posts. My ultimate goal is more to utilize this blog as a learning experience than anything but if i help out anyone along the way that’s great! I really do appreciate anyone who reads this and want to thank you before i even get started.
One of the things i learned a long time ago about myself was that i do not learn well from a technical document or book. Give me a visual representation of it and good things happen, things just click. That is why I have always been appreciative of learning materials which cut out the extreme technical language and explain it using real life examples and down-to-earth language. With that in mind my first few posts are not going to be technical or cover 100% of the material, especially since my goal is for personal growth 🙂
Anyways, hope you enjoy my blog!