MS Pivot Module

Find trends in user accounts...

DNN Pivot Module Support

We have worked hard with this module to produce a thorough manual. The .PDF version of the manual is included in the DotNetNuke Module Download Package found on our DNN module download page. The Pivot modules along with all our modules are available for free download and trial to all users who are registered on our site.

This is an extract of the install and IIS configuration steps.

InInstalling the Module

Simple Install Steps

The Advanced Login Module will install like any other DotNetNuke Manual. This module requires the following prerequisites:

· DNN 04.05.05 or later (for DNN 4 sites)

· DNN 05.00.1 or later (for DNN 5 sites)

The following videos will assist you if you are not familiar with installing a DotNetNuke Module.

Installing a Module in DNN 4

Installing a Module in DNN 5

Adding the module to a page

This module is added to a DNN web page in the same method as any other DNN module.

1. Login as Host or Admin account.

2. Create a page or navigate to an existing page.

3. From the dropdown menu at the top of you DNN website, locate the iWebs – Pivot

4. Define the location of the module in the Pane selector, and add the module to the page.

Click the Add button or link, and you are done. The module is added to the page.

Configuring your web server

Enabling Silverlight on IIS

This module can either work in the browser using Silverlight 4. Or using the Microsoft Pivot Browser that is downloaded from http://www.getpivot.com

To enable the Silverlight application to run on your web server, you will need to enable Silverlight if you have not done so already.

Purpose & Scope

Microsoft® Silverlight^TM is a cross-browser, cross-platform plug-in for delivering the next generation of .NET based media experiences and rich interactive applications for the Web. Silverlight offers a flexible programming model that supports AJAX, VB, C#, Python, and Ruby, and integrates with existing Web applications. Silverlight supports fast, cost-effective delivery of high-quality video to all major browsers running on the Mac OS or Windows.

In most cases, hosters do not need to perform particular deployments to support Silverlight. However, check for the following basic items that could prevent Silverlight from functioning correctly.

Procedure

MIME Types

In Windows Server 2008 IIS 7.0

All MIME types needed to support Silverlight are implemented by default in Windows Server 2008 IIS 7.0 and Windows Vista SP1. Windows Vista RTM customers can add mime types by running ‘IIS Manager’, clicking on ‘Mime Types’, then clicking ‘add’ and adding the following mime types:

· .xap application/x-silverlight-app

· .xaml application/xaml+xml

· .xbap application/x-ms-xbap

Alternatively, you can add the following mime types to your %windir%\system32\inetsrv\config\applicationHost.config file in the <staticContent> section.

<mimeMap fileExtension=’.xaml’ mimeType=’application/xaml+xml’ />
<mimeMap fileExtension=’.xap’ mimeType=’application/x-silverlight-app’ />
<mimeMap fileExtension=’.xbap’ mimeType=’application/x-ms-xbap’ />

In Windows Server 2003 IIS 6.0

To enable IIS 6.0 in Windows Server 2003 or IIS7 in Windows Vista RTM with the appropriate MIME Types, add:

· .xap application/x-silverlight-app

· .xaml application/xaml+xml

· .xbap application/x-ms-xbap

Here is a VBS script you could run to enable each of these types:

Const ADS_PROPERTY_UPDATE = 2
‘
if WScript.Arguments.Count < 2 then
WScript.Echo ‘Usage: ‘ + WScript.ScriptName + ‘ extension mimetype’
WScript.Quit
end if
‘
‘Get the mimemap object.
Set MimeMapObj = GetObject(‘IIS://LocalHost/MimeMap’)
‘
‘Get the mappings from the MimeMap property.
aMimeMap = MimeMapObj.GetEx(‘MimeMap’)
‘
‘ Add a new mapping.
i = UBound(aMimeMap) + 1
Redim Preserve aMimeMap(i)
Set aMimeMap(i) = CreateObject(‘MimeMap’)
aMimeMap(i).Extension = WScript.Arguments(0)
aMimeMap(i).MimeType = WScript.Arguments(1)
MimeMapObj.PutEx ADS_PROPERTY_UPDATE, ‘MimeMap’, aMimeMap
MimeMapObj.SetInfo
‘
WScript.Echo ‘MimeMap successfully added: ‘
WScript.Echo ‘    Extension: ‘ + WScript.Arguments(0)
WScript.Echo ‘    Type:      ‘ + WScript.Arguments(1)

If you copy and paste the code above into a VBS file and save it as ADDMIMETYPE.VBS the syntax to add each type would be:

ADDMIMETYPE.VBS .xap application/x-silverlight-app ADDMIMETYPE.VBS .xaml application/xaml+xmlADDMIMETYPE.VBS .xbap application/x-ms-xbap

Using the IIS Manager User Interface in Windows Server 2003 IIS 6.0

1. Go to Start\Administrative Tools and run IIS Manager, see figure below:

2. Right click on the server name and select ‘Properties’, see figure below:

3. In the Properties Dialog, click on the ‘MIME Types’ button, see figure below:

4. In the ‘MIME Types’ Dialog, click the ‘New’ button, see figure below:

5. In the ‘MIME Type’ Dialog enter one MIME Type at the time:

· .xap application/x-silverlight-app

· .xaml application/xaml+xml

· .xbap application/x-ms-xbap

see figure below:

For detailed information on Silverlight, visit http://silverlight.net/.

/Admin/SilverlightMIMEIISError/tabid/2337/language/en-US/Default.aspx

Pivot Background

Normally we try to ensure that our module run using all standard DNN or recommended DNN configuration settings. In the case of this Pivot technology, we are limited to provide the technology that has come from the Microsoft Labs. Because DotNetNuke does not use the latest MVC technology, we must make some small changes in IIS to get the Pivot running.

Special Pivot Requirements for IIS 7 (Windows 2008, Vista, Windows 7)

The Application Pool that runs your DotNetNuke website needs to be set as “Integrated Mode” for the managed pipeline.

What is Classic VS Integrated Mode

Classic mode

(the only mode in IIS6 and below) is a mode where IIS only works with ISAPI extensions and ISAPI filters directly. In fact, in this mode, ASP.NET is just an ISAPI extension (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). IIS just treats ASP.NET as an external plugin implemented in ISAPI and works with it like a black box (and only when it's needs to give out the request to ASP.NET). In this mode, ASP.NET is not much different from PHP or other technologies for IIS.

Integrated mode

, on the other hand, is a new mode in IIS7 where IIS pipeline is tightly integrated (i.e. is just the same) as ASP.NET request pipeline. ASP.NET can see every request it wants to and manipulate things along the way. ASP.NET is no longer treated as an external plugin. It's completely blended and integrated in IIS. In this mode, ASP.NET HttpModules basically have nearly as much power as an ISAPI filter would have had and ASP.NET HttpHandlers can have nearly equivalent capability as an ISAPI extension could have. In this mode, ASP.NET is basically a part of IIS.

To set Integrated Mode:

1. Ensure you are running DNN 4.8 or greater if you want to run on IIS 7. (or in DNN 5x we suggest 5.4.2 or later)

2. Start IIS

3. Select Application Pools

4. Find the Application Pool for your website.

5. Double click the application pool, and ensure that Integrated is set in place of Classic

6. Ok and close.

7. Test your website and others, to ensure normal behaviour. Note the recommendations at point 1 for the versions.

Special Requirements IIS 6 (Windows 2000, 2003 Server)

If you are running II6 and wish to access the Microsoft Pivot Labs technology, you will need to enable some special configurations. To do this:

1. Login to your web server and start IIS

2. Browse to your Web Site or Virtual Directory for the website in question and Rick Click selecting Properties.

3. Select the Home Directory Tab / Configuration

4. On the Mappings Tab, select Add

5. The following data depends on what type of server you are running. 64 bit vs 32 bit, and if you have .net 4 installed or not. The only thing that changes is the path for the .dll file.

Add the following data: 64 Bit server with .Net 4 installed

- Executable: C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
Extension: .cxml
Limit to: GET
Script engine: checked
Verify that file exists: unchecked

this gives you something like this above. Click OK and repeat the process for the following extensions:

- Executable: C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll
   Extension: .dzc
   Limit to: GET
   Script engine: checked
   Verify that file exists: unchecked

- Executable: C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll

   Extension: .dzi
   Limit to: GET
   Script engine: checked
   Verify that file exists: unchecked

- Executable: C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\aspnet_isapi.dll

   Extension: .jpg
   Limit to: GET
   Script engine: checked
   Verify that file exists: unchecked

Add the following data: 34 Bit server without .Net 4 installed

Not that the location of the four extensions described above will change, depending on your server status. As an example of the change for a 32 bit server without .Net 4 installed the location would change

From

C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\

To

c:\windows\microsoft.net\framework\v2.0.50727\

So the location of the first file in the example above would be:

c:\windows\microsoft.net\framework\v2.0.50727\aspnet_isapi.dll
still giving a setup that looks the same but with a different path

You can browse to your servers .net path (C:\WINDOWS\Microsoft.NET\Framework) to work out the location of the aspnet_isapi.dll file.

CRM in-line search fails with SQL error

After upgrading Microsoft CRM from earlier versions we found that the global search function when enabled failed to return any results, and once the index for the global search had run over a 24-hour period, the in-line search function for any entity would cause a crash and SQL error message to be displayed on page.

The problem

In our particular instance this CRM environment had been upgraded from much earlier versions of CRM and included an attempt to solve some upgrade issues by dropping indexes. Initially our thoughts were that the dropping of the indexes were responsible for the problems. However it appears retrospectively that was a fragmentation of indexes that cause the issue. I cannot be exactly sure why the maintenance procedure that is run on the SQL Server did not rebuild and reorganise the indexes sufficiently that the global social function. However the following solution did work for us.

We had pretty much followed the recommendation of this discussion forum.

The Solution

After submitting a support ticket to Microsoft they requested us to:

Run following command on CRM database to check fragmentation percentage:

SELECT object_id AS ObjectID, index_id AS IndexID, avg_fragmentation_in_percent AS PercentFragment,

fragment_count AS TotalFrags, avg_fragment_size_in_pages AS PagesPerFrag, page_count AS NumPages

FROM sys.dm_db_index_physical_stats(DB_ID(”), NULL, NULL, NULL , ‘DETAILED’) WHERE avg_fragmentation_in_percent > 0 ORDER BY ObjectID, IndexID

In case the fragmentation percent is more than 25-30% we have to rebuild the indexes.

Reference: https://msdn.microsoft.com/en-us/library/ms189858.aspx

the reference provided by Microsoft was helpful, but not as helpful as we would have liked. We ended up running the following query that automatically rebuilt all the indexes.

DECLARE @TableName VARCHAR(255)
DECLARE @sql NVARCHAR(500)
DECLARE @fillfactor INT
SET @fillfactor = 80
DECLARE TableCursor CURSOR FOR
SELECT OBJECT_SCHEMA_NAME([object_id])+‘.’+name AS TableName
FROM sys.tables
OPEN TableCursor
FETCH NEXT FROM TableCursor INTO @TableName
WHILE @@FETCH_STATUS = 0
BEGIN
SET @sql = ‘ALTER INDEX ALL ON ‘ + @TableName + ‘ REBUILD WITH (FILLFACTOR = ‘ + CONVERT(VARCHAR(3),@fillfactor) + ‘)’
EXEC (@sql)
FETCH NEXT FROM TableCursor INTO @TableName
END
CLOSE TableCursor
DEALLOCATE TableCursor
GO

After doing this, we were then able to turn on the global search and weight the relevant period of time for it to complete the indexing. It appears to have fixed our problem with both global search returning valid results, and in-line search no longer broken when global search was unable.

Changing your password in ZenDesk may affect your Microsoft CRM integration

if you are to upgrade or change the password that you utilise in your ZenDesk system for the account that has been set to synchronise data with the Microsoft CRM platform, you will notice that the synchronisation may not function correctly or may only perform a one-way synchronisation.

You will remember from the instructions that you likely followed in your initial configuration: http://www.interactivewebs.com/blog/index.php/zendesk/zendesk-to-crm-2015-integration/

that part of these configuration settings is to set up your password and username in the SETTINGS / ZD Personal Settings – area of your Microsoft CRM system.

Below is an extract from the vendor’s configuration portal found here

Step 2: Setting up new security roles

The Zendesk integration introduces two new security roles to Microsoft Dynamics CRM that must be assigned before you can proceed to the next step:
- Zendesk – Read configuration settings – grants the user access to Zendesk ticket details in read-only mode To gain access to create/edit Zendesk tickets functionality directly from Microsoft Dynamics CRM, these users must have a valid Zendesk liecense and enter their own personal Zendesk credentials on the ZD Personal Settings page.
- Zendesk administrator – grants access to the global Zendesk Settings page and the Zendesk Entity mappings . Have full access to create/edit Zendesk tickets directly from Microsoft Dynamics CRM.
By default, all users can view Zendesk ticket information in Microsoft Dynamics CRM if the panels are enabled.

To enable the roles, do the following:
1. In Microsoft Dynamics CRM, select Settings > System > Administration > Users .
2. In the Users page, click New if you need to add new users.
  If you are editing a list of existing users, select the user you want to modify and click on the Manage Roles button.
3. In the Add Users dialog box, select the role for the group you want to configure.
  The two new roles created by the Zendesk integration are at the bottom. Click Next to select and assign the users to a particular role and to send email invitations. Make sure you give yourself the Zendesk administrator role for now so you can complete the setup.
Users are now configured to use the Z endesk for Microsoft Dynamics CRM integration! If you have pre-existing users, you can simply add the appropriate roles to each of your uses.

Note: For users with the Zendesk – Read configuration settings permission, they can individually add their own credentials by navigating to Settings->ZD Personal Settings in Microsoft Dynamics and clicking the New button to add credentials. Enter the Zendesk User ID andPassword then save the record and it will be applied when they access Zendesk tickets. The password will be encrypted so others cannot see the value.
Mac Mail using Exchange Connection to SmarterMail InteractiveWebs

To Set up your mac mail with and Exchange Connection using Mac Mail you will need to follow these instructions carefully.
1. On your Mac, open System Preferences.
2. Click Internet accounts.
3. Click Exchange.
4. Complete the display name, full email address and password fields.
5. Click Sign In.
6. Ensure that you’re email address is et for your User Name, and Type the internal and external URL to read: https://mail.interactivewebs.com/ews/exchange.asmx
7. Click Sign In.
8. An account summary screen will display. You can select or unselect any features that you do not wish to sync.
9. Click Done.
10. Click Add Account.