February 2006 - Posts
Today, thanks to Edwin Garst, I made some major progress with my SRS problem. Edwin mentioned that he had followed Microsoft KB 887787 which replaces a couple of .config files in the Report Server folders. I followed this procedure on top of what I had received from Marie and was able to bring up Reports and ReportServer. I then continued on with Marie's instructions for publishing the reports. I'm still having a few issues (many reports are giving me a 404 error). I'll blog full instructions once I get it all smoothed out.
Well, I haven't blogged for awhile hoping I'd have a solution to the SRS issue. Not yet, but we're working on it with help from the Partner Managed Newsgroups and Marie McFadden.
One of the problems I had was that when I tried to run the CRM installation, it would come up with an error message that totally filled the screen. In the past, since I couldn't see the bottom, I simply stopped the install process. CRM seemed to actually install OK, but of course SRS wouldn't activate and a few other things were missed. The other day I got the bright idea to make the resolution on the server monitor as tight as I could in hopes I would be able to see the whole thing. Didn't help, much. Still couldn't see the bottom. But I figured there still ought to be some kind of button hidden at the bottom so I hit TAB and ENTER and the process continued to completion. Still didn't solve the SRS issue but did let the install complete more or less properly.
Next, I saw a very involved procedure recommended on the newsgroup to solve a related issue. Tried to work through that but it seemed to make things actually a bit worse. But in fairness I hadn't reworked it when I got an suggestion from Marie involving uninstalling SRS and reinstalling that. Unfortunately that didn't work either but we're still working on it.
So, that's a bit of an update. Still plugging. At least the main functionally of CRM is working and it's great.
A week or so ago I blogged about a problem I was having with CRMAppPool errors appearing in my event log. My solution was to clear up a Journal Wrap error in File Replication Services. But I was unsure whether there was a direct relationship or not, or just a coincidence. Recently on the Partner Managed newsgroup, someone else posted that he was experiencing a problem with the CRMAppPool error, just as I had. I suggested he try clearing up the FRS, that it MIGHT help. Tonight I read in the newsgroup where that had in fact resolved his problem. Or at least he hasn't experienced those errors since. That kinda reinforces that there is a connection.
This same poster also indicated that other than his CRMAppPool error, his installation of CRM 3.0 SBE had gone well. I asked whether he was running ISA on his Small Business Server box. He is not. This reinforces to me that the problem folks are having with Activating SQL Reporting Services is related to ISA. That seems to be a factor in every case that has the problem. If you don't have ISA installed, you're good to go. Hopefully this SRS issue will be resolved at some point.
I recently upgraded a client to SBS 2003 using Swing Migration. On one client workstation, which was not in use when we did the migration, we were getting an error in the Event Log every time the user sent a fax. The fax server attempted to send the workstation a notification when a fax had been sent successfully but the notification failed and showed up in the Critical Errors in the 'morning report'. I posted this issue to the Partner Managed Newsgroup and received a recommended course of action. Great!
I logged onto my client's network remotely and used RDP (Remote Desktop Protocol) to access the workstation to make the Microsoft recommened fix. Oops! RDP couldn't find the workstation. I figured the user had shut it down for the evening. I was informed that the workstation was left on always. So, when I went to their office next, I checked to be sure that RDP was properly configured. It was. I then, later and from my office, tried to see if it was available via Remote Web Workplace. It showed up in the list of workstations I could access. But I could not access it when I tried. So I RDP'd into the server and tried PINGing the workstation. The ping failed. I noted the IP address was 10.0.0.100 which seemed somewhat 'convenient'. I looked in the DNS zone and found .100 to be the listed address for this workstation. I checked the DHCP leases and found an entry for the workstation which was 10.0.0.114, a bit different from that listed in DNS. I tried using RDP from the server to 10.0.0.114 and I got in. Apparently when I did the Swing Migration, the workstation's IP address was migrated over in DNS. But, since the workstation had not been in use for while, when it came up with a new IP address, somehow the old DNS record remained.
I deleted the stale record from the forward DNS zone and on the workstation performed IPCONFIG /registerdns from the Command Line to force it to be properly registered in DNS. Then I was able to access the workstation by name from RDP from the server and via Remote Web Workplace. The fax issue was resolved, thanks to Microsoft's Partner Managed Newsgroups, by setting the Messenger service on the workstation to Automatic startup and starting it.
Another Lesson(s) Learned :-)
Well, I was able to reinstall CRM 3.0 from my original MAPS CD and it didn't give me any kind of error regarding the version of my SQL database. So at least I'm back where I was, SRS error and all.
Looking at the 'error' that the setup produces when it hiccups on Activating SQL Server Reporting Services, I notice that it appears to be a permissions error. The message is encased in html so it took a bit of looking to get past all that junk. Here is what apprears to be the pertinent info:
The application attempted to perform an operation not allowed by the security policy. To grant this applicaton the required permission please contact your system administrator or change the application trust level in the configuration file.
<a little more html junk>
Exception Details: System.Security.SecurityException: Request for the permission of type System.WEb.AspNetHostingPermission, System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken =b77a5c561934e089 failed.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Unfortunately the stack trace is then in a portion of the message that is not accessible. But at least I have a little more to go on. And I've got my CRM working again, though still somewhat crippled without SRS.
After a very encouraging and successful test install of the CRM 3.0 90 Day Evaluation on my VPC, I took the plunge and uninstalled my failing CRM 3.0 on my real server. Having recently successfully done this I felt fairly confident all would be OK. I then went to reinstall using the 90 Day Wonder version using my MAPS license keys. It took the keys fine and sailed through the checks concerning SQL Reporting Services. However, it has now come up with a new one:
Setup detected a version mismatch between the specified database and the current product.
The Version of Your Microsoft CRM Database is Lower Than Expected
Cause
Setup has detected that the version of your current Microsoft CRM 1.2 database does not match the version required.
Solution
To resolve this problem, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
I know I upgraded my CRM from 1.2 to 3.0 about 3 weeks ago and have been running it as 3.0 eversince, SRS issues notwithstanding. Now I have to wonder why it still thinks I'm running a 1.2 database. I'll try reinstalling once again using my original MAPS CD so I can (hopefully) get my system back up and running.
Stay tuned!
Microsoft has recently released (for download) a 90 day evaluation version of CRM 3.0. This is meant for to be installed at a prospective CRM user's site so they can evaluate it for a couple of months. If they like CRM, then the installed code can continue to be used with the addition of a proper license code. Otherwise, it expires after 90 days and can't be used, except with a new license code.
Members of our CRM study group have downloaded the 90 Day Wonder to try out and learn from, as well as for their client's to evaluate. One of our members, Jay Leggett of Jay's Toys, Ltd., noted that when it (the Small Business Edition) is loaded (on a Small Business Server) it does NOT report the SQL Reporting Services errors that have been common when installing CRM 3.0 on an SBS 2003 server with ISA 2004 installed. The most prevalent error was related to the loopback address (127.0.0.1) being specified in the Default Web Site. There were no errors related to SQL Reporting Services when Jay installed it. There were no such errors when we loaded it on our CRM study group class machine. And tonight, I loaded it on my test SBS 2003 VPC, and again with no errors reported.
Another problem that's seems somewhat common with the installation of CRM 3.0 on SBS 2003 is an issue with activating the SQL Reporting Service. I was delighted to see that the setup of the 90 Day Wonder breezed over this and produced no SRS activation errors.
Looks like the Microsoft Dynamics dev guys have updated the code for the 90 day evaluation to resolve the many errors/issues we've been experiencing with SBE installatons. Next I'll try using it on my production system. I feel a bit more confident uninstalling CRM and reinstalling it using the existing databases now that I've done it a time or two. We'll see if this resolves the issues I've been having with SQL Reporting Services.
I have an old LexMark inkjet printer that I go back in 2000. It's been sitting on the shelf for several years so I decided to check it out or throw it out. Well, it appeared to work, except that I did not have a black ink cartridge that would work. The ones I had had all dried up, but I do have several of the color cartridges that were sealed and fresh. So I decided to go to the local OfficeMax and pick up a fresh black cartridge. I found it and started to walk to the checkout counter. As I did I walked past the printers display and spied a brand new LexMark inkjet printer sitting there. The printer was current day technology, 4800 DPI, photo quality (supposedly - we'll see) and only $39.99! The black cartridge for my 6 year old printer was $35.99. I took the cartridge back to the rack and picked up a brand new printer and headed to the checkout counter. Go figure!
Recently I noticed a series of errors relating to my CRM 3.0 installation in the Event Viewer on my server. The first was "A process serving application pool 'CRMAppPool' terminated unexpectedly. The process id was '6560'. The process exit code was '0x80'". At this point I was also having difficulty logging onto CRM. Looking this up on Google produced only one hit which wasn't very helpful. However, at the same time I also noticed a number of errors in my File Replication Service event log, "The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR." I remembered the Journal Wrap issue from doing my first Swing migration. Jeff pointed me to that to resolve some issues I was having with the Swing. So, I decided to give it a go. I needed to correct that error anyway. The error message comes with very detailed instructions but basically it's just setting a flag in the registry. Doing so stopped that error from occuring in the FRS log. And since then I have not received any more CRMAppPool errors! And I was able to log onto to CRM again. The FRS Journal Wrap error had been occuring for many months so I'm not sure what the relation was to the CRM issue. But fixing it seems to have had a desirable side effect on my CRM. If you have any insight as to why, I'd be interested in hearing about it.
My second issue was a constant stream of CRMExchangeQueueService errors in the Applications log. These were occuring in pairs.The first would be a warning, "The description for Event ID ( 5896 ) in Source ( CrmExchangeQueueService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: xxxx, http://CRM.LentzComputer.local/MSCRMServices/CrmEmail.srf." followed immediately by error "The description for Event ID ( 5892 ) in Source ( CrmExchangeQueueService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: xxxx." Looking this up in Google was a little more helpful. I found a posting where someone had had this problem and had reinstalled the CRM-Exchange E-mail Router with good success. I went into Add/Remove Programs and actually found two instances of the E-mail Router, probably because I had upgraded from the 1.2 version. I uninstalled both and reinstalled the CRM 3.0 Exchange E-mail Router. The CRMExchangeQueueServices errors have disappeared.
There has been some concern recently that the upcoming Small Business Server 2003 R2 release, which will be available 'sometime' in 2006 (or so) will include SQL 2005 Workgroup Edition. Nice, you might say, but supposedly the Workgroup Edition does not support Web Services which CRM 3.0 depends on. Needless to say, this is of some concern to those interested in CRM Small Business Edition which relies on web services. There has been some 'back channel' discussion about this with some of the developers saying this won't be a problem. Wanting to beleive them, and to prove it to myself, and with nothing better to do on a sunny 80 degree 'winter' Super Bowl weekend, I decided to try for myself.
I installed SQL 2005 Workgroup Edition on my test SBS 2003 Premium Edition VPC with SP1. That installation went relatively well. I then installed CRM 3.0 Small Business Edition. I was surprised that the Environment Diagnostic Wizard sailed through its checks and gave everything a clean bill of health! (I had cleaned up some of the SBS issues previously. The actual install was a little 'rockier' but it did complete. I don't think the issues I encountered were related to SQL 2005.
After installing, I was able to add a user to the system using Deployment Manger. I could create a new Account with a subordinate Contact and then schedule an Activity. Everything seemed to work fine. Granted, I did NOT do extensive testing. I just wanted to see if it 'would work'. From my brief experience, it did. The problems I did encounter are not dissimiliar to the problems I am experiencing with my own system using SQL 2000 SP4. Again, my testing was very superficial, but seemed encouraging.
Looks like SBS 2003 R2 might not be the problem with CRM I once feared. I sure hope so.
The Alamo PC SBS SIG met Friday, February 3rd. Our primary speaker was Matthew Sutton, President and CEO (and Chief Guru) of HyBlue. Matthew gave a great presentation on the benefits of using a monitoring service to keep track of your clients' servers and workstations. This proactive approach is a win/win for both the client and the technology provider. You can view/listen to the meeting via Live Meeting by clicking here.
Please excuse that the recording first asks for you to state your name, several times. Kinda hard to do with a recording. Eventually, it will let you listen to the presentation in progress. Sorry about that, I should have started recording earlier. Hey! I'm still learning how to to do this 'Live Meeting thing'. There's a lot to manage when setting up for a user group meeting, chatting with folks that just 'have to talk' with you while you are trying to set up, etc., etc., etc. :-) Anyway, the meeting went relatively well and Matthew did a super job!
Our next meeting will be March 3rd when we will have Peter Gallagher of Mothership Las Colinas (SBS PSS upper tier Support) and Charles Van Huesen of TS2 Team fame.
I went to the CRM 3.0 Launch in Austin, Texas yesterday. There were about 150 in attendance, a bit lower than the 400 or so they had in Dallas the day before. Today they are in Houston.
The main presentations unfortunately had a bit of marketing fluff. Too much time was spent building scenarios and too little explaining how CRM would have benefitted the situation. I'm sure they will refine this for future events. But it was very worthwhile and thought provoking. My customers who were there seemed to find it worth the trip.
Of particular value to me was visiting with the various vendors who had display tables at the event. Some of the many are:
- C360 - The ever effervescent Jeane O'Neill was at the C360 booth. C360 has a number add ons that improve the functionality of CRM
- CardScan - demonstrated not only how their device can capture data from business cards, but how their software can be used to capture info from e-mail signature blocks and even web pages and put it into CRM.
- factiva - factiva will search an on-line database for information about companies in your CRM database and links with Reuters to provide up to date news about those companies. This could be helpful to use just before going into a meeting.
- Scribe - provides integration and migration software to connect CRM with other products like accounting systems or other CRM type packages.
- Experlogix - their quote system integrates tightly with CRM. I've used QuoteWerks but this one looks really slick.
- Neocase - their package links internal departments and external parties involved in the resolution of customer issues.
There were several others there I did not have an opportunity to visit. If the launch comes to a city near you, I recommend you attend.