As I wrote about yesterday, I am in the process of building out virtual images with PerformancePoint. I figured out how to rename the server and have both SharePoint Services and PerformancePoint work (see yesterday's post.)
Today, while working with the server, I realized that none of my Proclarity views were working. I tried several things and finally I gave up, uninstalled the Proclarity Analytics Server and re-installed it. This worked great in getting it up and running. Only took about 10 minutes. Once that was taken care of, the Proclarity reports still didn't work. I thought I had a great idea and I set everything up as http://localhost instead of the server name. So I went through every report on my server and pointed them from the older server to localhost. This was a slow process, but once it was done everything worked great.... FROM my machine. As soon as I ran the dashboard from another box, it failed. The moral of the story is, DO NOT use localhost as the server name in Proclarity reports. I thought I was saving myself some effort if I clone the VS. I then had to go back and reset them all to the new server name. This is a pain because I did it all by hand. Soon I will document the steps to save this off as a BSWX file and modify the xml to change the urls. This is a much more efficient way to go, especially if you have to do it twice.
Once this was done, everything worked great. If I find a better way to handle Proclarity, I'll re-post. In the meantime, this works, so give it a try.