SharePoint Designer Support Team Blog

Providing insight on hot and common issues, supportability, and how-to's for Microsoft SharePoint Designer. Coming direct from the support engineers themselves. Read who we are.

How to fix: Recurring Meeting Workspace error: ‘g_InstanceID’ is undefined

Note: I'm lifting this from my DataFormWebPart.com blog post, in hopes of the workaround getting more traffic.

Scenarios:

After changing the master page on a Meeting Workspace site, the recurring meeting workspace hyperlinks under “Select a date from the list below” do not work and throw a JavaScript error.

If you create a custom master page and use it for your Meeting Workspaces, a JavaScript error is thrown.

Error:
‘g_InstanceID’ is undefined

Cause:
The g_instanceId global JavaScript variable is declared in a script registered runtime by the Microsoft.SharePoint.Meetings.PropertyBag web control. This control is used in the master page that’s used by Meeting Workspace sites called “MWSDefault.master” (located on server in 12 hive\TEMPLATE\GLOBAL\).

Steps to Reproduce:

  1. Create a new Workspace: Site Actions-> Create Site -> Select [Meetings] Basic Meeting Workspace, click Create.
  2. On Workspace site, add a Calendar list: Site Actions -> Create -> [Tracking] Calendar.
  3. Add a new event to Calendar list, make recurring event, and select [x] Use a Meeting Workspace to organize attendees, agendas, documents, minutes, and other details for this event. Click OK.
  4. Follow steps to create workspace for Calendar event. Go to workspace.
  5. Change master page for workspace: Site Actions -> Site Settings -> [Look and Feel] Master page -> select any master page for Site Master Page and System Master Page. Click OK. Go back to workspace.
  6. Now the links under “Select a date from the list below:” do not work and throw a JavaScript error message: ‘g_InstanceID’ is undefined .

Workaround:

  1. Open SharePoint Designer 2007. Go to File | Open Site and connect to SharePoint site.
  2. Expand out _catalogs -> masterpage -> open master page used on Meeting Workspace.
  3. In Code View, add the following line of code under <%@ Import Namespace="Microsoft.SharePoint" %> tag:
    <%@ Register Tagprefix="Meetings" Namespace="Microsoft.SharePoint.Meetings" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
  4. Add the following line of code after opening <body …> tag: <Meetings:PropertyBag runat="server"/>
  5. Save master page, check in (if necessary), and publish major version.
Published Monday, March 24, 2008 10:54 PM by michmon

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

jd said:

Thanks for this, I just found this problem!  

One comment though, when copy and pasting the above code into SharePoint designer it inserted slanting quotation marks, not the standard character, which is obviously invalid, so I had to go through and replace them.  Not a problem, but slightly annoying.

April 7, 2008 4:51 AM
 

michmon said:

Hi JD,

Thanks for the heads up! I've went through and changed them to the standard character.

-Mike

April 7, 2008 12:19 PM
 

Kathy said:

How do you fix this problem if you don't have Sharepoint designer?

April 22, 2008 9:31 AM
 

Nathan said:

You can use Visual Studio 2005 or later.

April 23, 2008 3:39 PM
 

michmon said:

To be sure, you can also download SharePoint Designer trial version from here: http://www.microsoft.com/downloads/details.aspx?FamilyID=6bfa7447-a88d-4780-a981-b508a94ca120&DisplayLang=en

-Mike

April 29, 2008 1:16 PM
 

Charles said:

FYI - I found that in our particular scenario we're using cusotm master pages at the site level. In my case I was not successful editing the master pages on the meeting workspace level. I had to navigate up to the parent site in which the meeting workspace was created under and edit that custom master page per the instructions.

May 7, 2008 10:30 AM
 

Haries said:

Hey,

I get a similar error when I cofigure meeting. Other than the current occurance of the meeting, If I try to click on any other occurance it says " This occurance has not yet beenactivated".

I created a new webapplication on our test environment with default masterpage. Then created a new meeting workspace. associated a meeting with that meeting workspace, there is no error I can click on any recurring meeting.

So how do I resolve the issue with the custom master page can you please suggest.

May 13, 2008 1:27 PM
 

michmon said:

@Haries: Have you checked to see what SharePoint controls or Content Placeholders you might be missing from your custom master page when compared with default.master?

June 6, 2008 10:31 AM
 

Ashok said:

After making these changes I find that the master page for the meeting worspace gets reset to the default and I lose the master page selection that I made before the error.  How do I retain the master page changes to retain the look and feel and yet be able to get the recurring meeting links to work w/o any errors?

Anyhelp is greatly appreciated.

June 12, 2008 7:18 PM
 

Aurora Gustin said:

I have the exact some error as Ashok's last post:

After making these changes I find that the master page for the meeting worspace gets reset to the default and I lose the master page selection that I made before the error.  How do I retain the master page changes to retain the look and feel and yet be able to get the recurring meeting links to work w/o any errors?

Has anyone found a fix?

Thanks,

Aurora

July 14, 2008 4:33 PM
 

Matt said:

I've made these changes to both the default.master and MWSdefault.master pages in _catalogs | masterpage and am still having both the "g_InstanceID is undefined" for previous meeting dates as well as the "occurance has not yet been activated" error for future instances.

Did I edit the wrong  page?  I did verify that the pages were saved and are at version 2.0

November 18, 2008 11:11 AM
 

Matt said:

I was able to get this to work.  However, After making the changes and saving the file, I had to R-Click on MWSdefault.master and select "Set as Custom Master Page".  After that, everything worked again!

November 19, 2008 4:27 PM
 

Aaron said:

Great post.  This worked for me.  Thank you.

March 23, 2009 4:13 PM
 

Martin said:

Hey, great!

It workls!

Thanks a lot!

April 1, 2009 7:35 AM
 

Chad said:

Thank you so much, worked like a champ!

June 4, 2009 11:23 AM
 

HB said:

Thanks a lot for this.

It did work for me - but only for me, not for any other users. I got a Microsoft Internet Explorer is required error message when I tried to publish a major version and it was saved as a draft. I then had to find the master page gallery on my Sharepoint site and approve the modified page.

After that, the error was fixed for all users.

June 18, 2009 8:55 AM
 

Jim said:

I 2nd what Matt said,

The fix didn't work untl I right-clicked on MWSdefault.master and selected  "Set as Custom Master Page".  

June 23, 2009 5:14 PM
 

jriesen said:

I applied these code changes to our custom master page and this does fix the recurring meeting workspace error ‘g_InstanceID’ is undefined.  Yeah!  But for some reason on a Multi-page Meeting Site all the page tabs disappear.  Do you have any suggestions for fixing that?  T

August 13, 2009 10:29 AM

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Submit

This Blog

Syndication

Tags

No tags have been created or used yet.

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker