Compartilhar via

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

  • Artigo

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.

Comments

  • Anonymous
    April 06, 2008
    The comment has been removed

  • Anonymous
    April 07, 2008
    Hi JD, Thanks for the heads up! I've went through and changed them to the standard character. -Mike

  • Anonymous
    April 22, 2008
    How do you fix this problem if you don't have Sharepoint designer?

  • Anonymous
    April 23, 2008
    You can use Visual Studio 2005 or later.

  • Anonymous
    April 29, 2008
    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

  • Anonymous
    May 07, 2008
    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.

  • Anonymous
    May 13, 2008
    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.

  • Anonymous
    June 06, 2008
    @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?

  • Anonymous
    June 12, 2008
    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.

  • Anonymous
    July 14, 2008
    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

  • Anonymous
    November 18, 2008
    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

  • Anonymous
    November 19, 2008
    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!

  • Anonymous
    March 23, 2009
    Great post.  This worked for me.  Thank you.

  • Anonymous
    March 31, 2009
    Hey, great! It workls! Thanks a lot!

  • Anonymous
    June 04, 2009
    Thank you so much, worked like a champ!

  • Anonymous
    June 18, 2009
    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.

  • Anonymous
    June 23, 2009
    I 2nd what Matt said, The fix didn't work untl I right-clicked on MWSdefault.master and selected  "Set as Custom Master Page".  

  • Anonymous
    August 13, 2009
    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

  • Anonymous
    February 28, 2010
    Is there a way to update the custom master page at that level, but not override the styling that is inherited from top level master pages, several sites up?  I don't want to pull the code from the top level master page and paste in to the MWSdefault.master, and then have these one-off master page cases each time we have a Meeting Workspace issue like this, but also don't want to edit the top level page w/this code snippet. Is there any way to just have a small include file, or some other way to run this code at the Meeting Workspace level - and JUST this code? thanks!

  • Anonymous
    March 16, 2010
    thanks so much for the post. it worked out perfectly. those two lines in a master page solved all those meeting workspace problems.

  • Anonymous
    March 21, 2010
    Hi I'm having the same problem as jriesen where on multi-page meeting sites the page tabs disappear. Does anyone have a fix for this?

  • Anonymous
    April 08, 2010
    I'd check this fix out. It looks like it might be a better work around for some folks. http://blogs.msdn.com/pavankumar/archive/2009/04/09/working-with-mwsdefault-master-page-along-with-meeting-workspace-definition.aspx

  • Anonymous
    June 21, 2010
    Hi, Thanks for the fix. It worked for myself and the other admins but non-admin users still get the same error on page. I have give Full Controll permissions to my test user on the workspace and the calendar but it still gets the same thing. Any suggestions would be much appreciated. Thanks

  • Anonymous
    July 07, 2010
    I'm getting an error  'g_thispagedata' is undefined on SharePoint 2010 meeting workspace when I click the dates on the left hand side. I had saved the site as a template and brought it back on a different web application. both web apps use the default masterpages.

  • Anonymous
    August 24, 2010
    i cannot believe that... got SP2010 and that error still seems to be there!!! tried everything, compared the two master pages of a working (original M$ workspace), and a non working instance (my saved template based on M$) and found no difference (despite a WebPartId). also looked for both the Tagprefix and Meetings:PropertyBag - both are there. any new suggestions for a Sharepoint 2010 Meeting Site???

  • Anonymous
    November 08, 2010
    For SharePoint 2010, do the same thing but change version of the assembly from 12 to 14 <%@ Register Tagprefix="Meetings" Namespace="Microsoft.SharePoint.Meetings" Assembly="Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>

  • Anonymous
    November 24, 2010
    The comment has been removed

  • Anonymous
    December 01, 2010
    The comment has been removed

  • Anonymous
    January 26, 2011
    I've got the same problem in SharePoint Foundation 2010! The masterpage is correct (otherwise I should receive the "g_instance_id is undefined") but the SharePoint javascript still contains a bug which results in "g_thispagedata is undefined"). DoubleD is right: why is this bug still in SP2010?!?! is their any chance that MS create a patch for this?

  • Anonymous
    August 25, 2011
    I got similar problem and fixed per this message link. Very useful. The important thing I missed the first time is Matt's text about right-click in designer MWSDefault file and set it as custom default. It would be good to put this in the "workaround" solution top part.

  • Anonymous
    October 30, 2011
    When i follow above procedure, I get "File Not Found Error". we are in Sharepoint 2010

  • Anonymous
    August 08, 2013
    In my list of masterpages I had default, minimal, MSWDefault, MWSDefaulv4, and v4 .. First I set default master as default master and set mwsdefault as custom master page .. was prompted about changing the interface from v4 to v3 and chose yes .. huge mistake .. messed up my whole interface .. in an attempt to swiftly dig my way out of that one, I changed default master to v4.master and custom master to MWSDefaultv4.master, was prompted to change interface to v4, click yes, and voila .. the appearance is as it should be an all the links work and all the content on previous meetings is there...everything appears fine except no more java error

  • Anonymous
    October 16, 2013
    HI All, Even though  i have updated the master page its not  working  in some other systems. What are the system specifications to work??