5/14/12

Office 365 Missing Create New Document Menu


The Office 365 platform provides users with the ability to add Office 2010 documents from the ribbon menu. In some cases, these menu options are missing from the document library. The reason for this is that perhaps the library does not have the content type definition to know about those documents. Another reason is that the content type is defined, but the site is not associated with them.

Verify if Content Type Exists

We will go thru the process of adding the Excel content type to the document library by following these steps: (note that the same can be repeated for other documents: Word, OneNote and PowerPoint)
  • Click on Team Site
  • Click on site actions
  • Site Settings
  • Under Galleries, click on Site Content Type

Under document types, check to see if you find the Excel entry, if it does not exist, we will create the new content type by taking these steps:

Create Content Type - Document

Click on the Create Link (top) and fill out the form as you see on the image. Notice the parent content type and existing group.


Add Content Type

Now upload an Excel document  template that you will like to use as the default template and press OK.


Associate Template


This has added a content type with an associated document template. At this point, the site is not associated to this content type.

Associate Library to the Content Type

To enable the menu options on the ribbon menu, we need to follow these steps:
  • From Team Site, click on the document library
  • Click on the Library tab. This displays all the library functions
  • Click on Library Settings (left side - see below)


  • Make sure the library is able to manage content types, so click on Advanced settings
  • Under Allow management of content types, select yes (see below)



This change allows for additional functions to be visible on the site settings. Continue with these steps:
  • Click Ok
  • Click on Add from existent content types
  • Find the Excel Content type, and click Add
  • Click Ok


The content type is now associated to the library. If you need to add additional documents, repeat the process and finish adding the other document content types. After you complete this, visit the document library again and click on the document tabs. You should now see the menu options which allows the user to create new documents.




I hope this helps
og-bit.com

5/13/12

Office 365 Documents Do Not Open in the Browser


Office 365 allows users to create and open Office 2010 compatible documents using the Office Web Apps. This is basically the office web client which frees the user from the need to have the Office 2010 client installed.  There may be some cases when the editing or creation of new documents is not done by the web client, and instead the browser tries to download the file showing you this dialog:

Download File Dialog


This is usually due to an add-on installed on the IE browser.  To disable this add-on, do the following:
  • Click on tools
  • Click on Manage Add-ons
  • Click on the dropdown that displays Currenlty loaded add-ons and change this to show all add-ons
  • On the right panel, look for Sharepoint OpenDocuments Class and click Disable



Disable OpenDocument Class



The browser will no longer try to download the document, and the file will be open right on the browser. Keep in mind that this is only applicable to Office 2010 compatible documents like:

  • Word
  • Excel
  • OneNote
  • PowerPoint

I hope this helps

og-bit.com

4/22/12

SharePoint Use Correlation Id to Get Error Detail

When activating a SharePoint feature or creating a sub-site from a custom web template, you have probably received a few errors from SharePoint which show a correlation id and nothing additional that can indicate what the problem is. The purpose of this id is to allow you to find additional information about the errors by reading the ULS trace log (Unified Logging System). You can find the details of the error by using PowerShell. To use this, first open the SharePoint Management Shell. You can then type this command in the shell:

Get-SPLogEvent | Where{$_.Correlation -eq "GUID"} | Format-Table Category, Message  -wrap -autosize | Out-File -filepath c:\log.txt

Replace the word GUID by the correlation id that you see in the error message. This command basically reads the log information associated to the id. It formats the message in a table by reading the category and message columns. You should also notice that we want to read the entire message with no truncation, so we need to use the -wrap switch. The out-file parameter sends the output to a file on the C: drive.

The output should provide detail information on what the actual error is. This can allow you to correct the problem.

I hope this helps.

og-bit.com

SharePoint Exception 0x8107026E When Activating Module

When you encountered the 0x8107026e exception during the activation of the error, you should read the stack trace information to see if the error is related to the ONet.xml file. There would probably be a LocalizedXml function call which returned the error. This however does not provide the root of the problem. To find out what is going on, you need to open the SharePoint log files. These files can be found in a path similar to this:


%Program Files%\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS 

or if your system has the environment variable set properly, you can use this:

%SHAREPOINT ROOT%\\LOGS

Open the current file using notepad, so you can find more detail information on what is going on. This error is usually associated to the fact that the ONet.xml file is deployed to a different folder or just was not deployed. So if you look at the log, you can probably find this error:

Failed to open the file 'Features

and

The specified path "" does not exist

To resolve this problem, look into your project definition. First select the Web template folder and read the folder name under it. This is the expected folder name where the files should be deployed. Now make sure that this matches the name of the actual web template. Expand the folder and select the Element.xml file. Look for the Name property and make sure that this matches the folder name.

If the folder and template name are matching, you can now look to see how the ONet.xml file is being deployed. Select the ONet.xml file and look at its properties. The following properties should read as follows:

Build Action: Content
Deployment Type: ElementFile

Also look at the deployment location. This should match the folder name.Make the necessary changes and re-package your solution. This should address the error.

I hope this helps.
og-bit.com

3/4/12

How to Install SSMS 2008 on Windows 7

If you are trying to install SQL Server 2008 Management tools, and you are finding this install somewhat difficult, you are not alone. The installation for this product became very confusing.  I am hoping to help some of you out there with this blog entry. The first thing to notice is that you need to get the correct version of SSMS. You need the 2008 version not 2008 R2.  I found the correct version at this location:


*Note: Select the 64-bit or 32-bit version that matches your work station.

Take the following steps to install the software:

  • Click on Installation
  • Click on New SQL Server stand-alone installation


SSMS installation

  • On Setup Support Rules click OK

SSMS support rules

  • The next dialog is kind of misleading. It says that is gathering user settings, but there is no progress. Just ignore this and click on Install.

SSMS install

  • The next dialog shows a set of rules. All rules should be on Passed status. Windows firewall may give you a warning.  This is if you need to open a port for external access. Since this is for development purposes, we will ignore this rule and just click on Next.

SSMS rules validation

  • The installation type dialog is also a bit confusing. You would think that you just need to add a feature, but in fact we need to select “Perform a new installation…”.  The installation of the client tools is under this option. Select it and click Next.
SSMS install type

  • On product key, just click Next. It should be on Specify a free edition by default
  • Accept the terms and click Next
  • We are finally getting there. On the Feature Selection dialog, we can check the Management Tools - Basic option.  Now click Next.

SSMS features

  • Click Next on the Disk space requirements.
  • If you feel like reporting errors to Microsoft, check the error and usage reporting. If not, just click Next
  • Another Installation Rule dialog is displayed, just click Next
  • We are finally there. On Ready to Install click Install. The installation process should start. Let it run until you get the Setup process complete message and click Next.

SSMS progress

  •  We should now see the Complete dialog. YES!!!. Just close the dialog and let’s verify that the software is there by looking at Microsoft SQL Server 2008 program group.

SSMS complete


  • We find the SQL Server Management Studio program shortcut


SSMS program group


That was a long process, but if successful you should be able to connect to SQL Server using SSMS. Let’s just hope that for the next versions this installation process becomes much easier. 


OG-BITechnologies Inc