Alan Faulkner's Forefront Security Blog

So you finally get Commerce Server events recorded in your site and you’re wondering why it doesn't show up in your Data Warehouse Reports!?

• First, let's make sure that you are actually seeing the events.  Open your IIS logs (usually found in C:\windows\system32\logfiles\w3svc1).  You should see something similar to below your CS events in your log files.  I'll pick three common event types to illustrate:
• Campaign Event:
• CEVT={T=CAMP,CI=2,EVT=REQUEST,PG=0}
• Order Event (Submit Order)
• CEVT={T=ORD,ORID=%7b037ef285-26b1-4ce4-993f-f3850b46ce37%7d,EVT=SUBOR}
• Basket Events (Add Item to Basket)
• CEVT={T=BSK,EVT=AIBSK,PRID="Adventure+Works+Catalog%3bAW031-14",BSKT=}
• Second, If you site uses SSL, you need to make sure your server is configured for the SSL port in Commerce Server Manager.
• To Verify this, Open Commerce Server Manager -> Expand Commerce Sites -> Expand your site -> Expand the Applications for your site -> Then for each server that the application uses right click and hit properties. You should see the tab “Identities” at the top. In the SSL Identities, be sure to add your port here. The default SSL port is usually 443.
• Third, In order for Data warehouse to resolve the IIS user against the Commerce Server/ASP.NET Authenticated user, the Data warehouse httpModule needs to be added to your site. Just add the following in the <httpModules> section of your web.config file.
• <add name="CommerceDataWarehouseAuthenticationModule" type="Microsoft.CommerceServer.Runtime.CommerceDataWarehouseAuthenticationModule, Microsoft.CommerceServer.Runtime, Version=6.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
• To verify that you have this added, you should see something similar to the following in your IIS Web log:
• MSCSAuth=4615EE3B2C3E55008DA4F………….

After you have done those items, you should now see your event items in the Data Warehouse Analytic reports!

Hope this helps!