Since I had to build myself a whole new OM12 test environment at home I decided to use the .NET test application Talking Heads for demonstrating the APM (Application Performance Monitoring) component of OM12.
All credits go to VIAcode for sharing this APM Test Lab for FREE!!!
Even though the website of Talking Heads makes one think it’s a Next > Next > Finish experience, there are some caveats to reckon with. Otherwise this APM demo lab will never take off and become a frustration which would be bad. In this posting I describe the caveats to reckon with.
- Download ALL the files, to be found here on the bottom of the webpage (no registration needed which saves some valuable time);
- The file talkingheads.zip contains the two MSI files which must be installed: TalkingHeads.msi and TalkingHeadsMidtier.msi
Use these settings when installing TalkingHeads.msi:
And these settings when installing TalkingHeadsMidtier.msi:
- In order to work a SQL Server must be present (SQL Server Express is OK here but PLEASE install the version with SQL Server Management Studio, SQLEXPRWT_x64_ENU.exe (SQL Server Express with TOOLS) since it makes it much more easier to manage your SQL Express Server). A good alternative is to use the same SQL Server which hosts the OM12 databases and SSRS instance.
Until now it’s a straight forward process, just as stated on the website of VIAcode. But now the fun starts. Since many times the configuration won’t do for the SQL Server Connection string as stated in the web.config file for the TalkingHeadsMidTier part:
When the website of TalkingHeads is opened (http://localhost/TalkingHeads/) and one goes to the menu option Setup in order to create the database and seed it with bogus information, this error is shown:
On itself nothing wrong here. The database must be created so nothing wrong there. So an applicable time frame is selected and the button Seed Database is hit. For a second or two this screen is shown:
And indeed, when I checked, there wasn’t a new database created on the SQL Server instance…
And yet, SQL Server (full blown version) was available and operational. But the Application log of that SQL Server told me nothing about a connection attempt made by TalkingHeads.
This website tells it all. I adjusted the web.config file to this: (local) instead of (local)\SQLEXPRESS:
Saved the modifications and tried it again. Now everything seemed to work just fine. However, another error was thrown: ‘…Login failed for user 'IIS APPPOOL\ASP.NET v4.0'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: <local machine>]…’
This has everything to do with the Application Pool (ASP.NET v4.0 remember?) and it’s identity. SQL Server doesn’t accept the ApplicationPoolIdentity which is default for this Application Pool.
So it’s time to change that as well:
- Open IIS Manager;
- Go to Application Pools and select the ASP.NET v4.0 Application Pool, right click it, select Advanced Settings and change the Identity to LocalSystem, like this:
- Save the changes and run the TalkingHeads website again and go to the Setup menu.
Now you can start configuring APM! Have a nice day everybody!