In the installation directory, edit the two files *.SetParameters.xml:



Web Meeting Manager

Start with Solutions2Share.Solutions.MeetingManagerWeb.SetParameters.xml


We need to update following key:

Please change the values for the SQL connection string to:

  • "Contoso-SQL,1433" = SQL Server and Port, comma separated, No SQL Alias at this stage!
  • "Catalog=MeetingManager" = SQL database name


This could look like this:

<setParameter name="MeetingManagerAppFrameworkConnectionString" value="Data Source=Contoso-SQL,1433;Initial Catalog=MeetingManager;Persist Security Info=True;Trusted_Connection=True;Pooling=False" />

<setParameter name="MeetingManagerHangfireConnectionString" value="Data Source=Contoso-SQL,1433;Initial Catalog=MeetingManagerHangfire;Persist Security Info=True;Trusted_Connection=True;Pooling=False" />


Change lines three lines to match your values:

  • IIS Web Application Name is the name of the IIS Website you've created before.
  • MeetingManagerClientId and MeetingManagerIssuerId are the same and are generated in Appregnew).
  • MeetingManagerClientSigningCertificateSerialNumber can be retrieved from the SPTrustedToken - make sure you're using uppercase characters and do not copy from certificate management console as it adds invisible characters)


<setParameter name="IIS Web Application Name" value="MeetingManager" />

<setParameter name="MeetingManagerClientId" value="d540e8cb-f0ea-4a2d-97b9-cacd4f2c8d6a" />

<setParameter name="MeetingManagerClientSigningCertificateSerialNumber" value="550000000B90DA51E9A3B61DB400000000000B" />

<setParameter name="MeetingManagerIssuerId" value="d540e8cb-f0ea-4a2d-97b9-cacd4f2c8d6a" />


All other parameters which are not mentioned here, can be left to its default.

Save and validate the XML file by opening in a browser (optional).

Web Invitation Manager

Next Solutions2Share.Solutions.MeetingManagerInvitationsWeb.SetParameters.xml


We need to update following key:

Please change the values for the SQL connection string to:

  • "Contoso-SQL,1433" = SQL Server and Port, comma separated, No SQL Alias at this stage!
  • "Catalog=MeetingManager" = SQL database name


This could look like this:

  <setParameter name="InvitationToolDefaultConnectionString" value="Data Source=Contoso-SQL,1433;Initial Catalog=InvitationManagerConfig;Persist Security Info=True;Trusted_Connection=True;Pooling=False" />

  <setParameter name="InvitationToolHangfireConnectionString" value="Data Source=Contoso-SQL,1433;Initial Catalog=InvitationManagerHangfire;Persist Security Info=True;Trusted_Connection=True;Pooling=False" />


Change lines three lines to match your values:

  • IIS Web Application Name is the name of the IIS Website you've created before.
  • InvitationToolSPUsername Farm Administrator username
    For on-premise high-trust environments set credentials for accessing the SharePoint instance through basic authentication. The user needs to have write access to all site collection on which SharePoint is installed.
  • InvitationToolSPPassword Farm Administrator password
  • InvitationToolLogPath Change the log file to a directory which exists, the file will be created automatically


<setParameter name="IIS Web Application Name" value="MeetingManagerInvitation" />

<setParameter name="InvitationToolSPUsername" value="Contoso\sp_farm" />

<setParameter name="InvitationToolSPPassword" value="password!" />

<setParameter name="InvitationToolLogPath" value="C:\MeetingManager\log\InvitationToolLog.txt" />



All other parameters which are not mentioned here, can be left to its default.

Save and validate the XML file by opening in a browser (optional).