A Practical Guide to SharePoint 2013

A Practical Guide to SharePoint 2013
A Practical Guide to SharePoint 2013 - Book by Saifullah Shafiq

Sunday, December 4, 2011

Tip: You don't see shared folder on your guest OS. Here is what you can try!

Here is one of the tips that you can try if you don't see shared folder in your guest OS. Symptons are as following:

1. You enable shared folder but don't see it in guest OS.
2. You restart your guest OS multiple times hoping it would catch the setting and show the shared folder.
3. You had created machine folder. You thought there was a problem with so you created a Transient folder. Still it did not help!
4. You checked network settings in guest but did not find any thing wrong.

Well if these are the symptons and you are sure settings are correct then do this! Go to your virtual machine settings. I am not talking about the guest OS. I am talking about the virtual machine interface where you start and stop the guest OS, where you set settings for the guest OS. Open settings for "Network Adapters". Most probably "NAT" would be selected there. It works for in most cases. Just change this setting to anything. Now go to guest OS and you will notice that you internet has also disconnected that was working before. OK! Now go back to Network Adapters/Settings (in virtual machine settings) again and change the adapter back to whatever it was before. If it was NAT, change  it back to NAT and now after a minute, check guest OS again. Now you will see network to be up again and it will also show shared folders now. This is just a way to refresh the settings. It happens sometimes when things don't work the normal way. Small tips like this can save your time tremendously.

Wednesday, November 23, 2011

The form tamplate cannot be activated because it is still being uploaded to the farm

As the error name suggests, it happens when the form is still being uploaded and you try to activate it. I know this is confusing. You would ask why the option to activate the form is available when the form is still being uploaded. I don’t have an answer to that.

The element comment is used but not declared in the DTD Schema

When you try to open the browser-enabled form from the library, instead of opening the form, it asks you to select the xml form from the storing location to connect to. You think selecting the form will work, so you go ahead and select the published form from your hard disk but then you see the following error:

InfoPath cannot open a new form.
The form contains schema validation errors.

The element ‘comment’ is used but not declared in the DTD/Schema.



The form should be published to the SharePoint library. After you have published the form, make sure you select the correct content type to load the form.



1. You have different options when publishing browser-enabled InfoPath form. Make sure you select “SharePoint Library” when publishing it.
2. By default when you click New button, the default content type is selected. To open your browser-enabled form, make sure you click the arrow with the new button and select the right content type.




3. You can change default content type and even remove it if you want. Go to library settings. Under “Library Tools” select “Library” tab and then select “Library Settings”.




4. Under “Content Types”, select “Change new button order and default content type” link. Here you can change the order and make your browser form default. To delete content type, click it and then delete it.



Tuesday, November 22, 2011

Value cannot be null. Parameter name formTemplate

While removing an InfoPath form template, you get following error:
Value cannot be null
Parameter name: formTemplate



It happens when you are removing the template using the Central Admin site. After you have started the removal process, the form does not disappear immediately from the listed forms and if you try to remove it again, you will get this error because the form had already been removed. Just go back using the browser’s back button and you won’t see the form listed there anymore.

HTTP Error 500.19 - Internal Server Error

Error:

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.





Solution:

Change the .NET framework in application pool to version 2.0 to resolve this problem. You get this error if you change framework version to 4.0.

I dont see Remove solution link

You don’t see “Remove solution” link in solution management.

This is because the solution is still deployed to one of the web applications in your farm. Retract it from all web applications and then you will see the Remove Solution link.