Crystal Reports Server - Error 404 for CMC

suddenly cannot access our CMC

So it's been running perfectly fine before this? If so, I would avoid making any configuration changes until you figure out what went wrong, otherwise you run the risk of breaking it further.  If it's been working fine--for years, presumably, since it's an old version--then something must have changed in your environment in order for it to no longer be working.  Possible causes are changes to security software or Windows updates.

If this is a brand new install, please provide a little more info about your environment, such as the OS, version of IIS, 32-bit vs. 64-bit, etc...  Also, you state it's XI, but is it literally "XI" or just shorthand for either XI R2 or XI 3.X?

Yes, it has been running for years with no problems. The only change we made was the domain administrator password was changed over the weekend (which we have done in the past with no issue.) I even changed the password back in case that was somehow the issue, but the problem persisted. I have run windows updates since this incident started, but none were performed before.

It is Crystal Reports Server XI, no further releases, so it is an older version. It is running on Windows Server 2003 R2, 64bit. IIS version looks like 6.0.3790.

Thanks for your response.

The application doesn't stop working unless something in the environment has changed.  Do you have your services in the CCM (Crystal Configuration Manager) running under something other than a Local System account? If so, do the services need to be stopped so the passwords can be changed?   Also, were any of the updates specific to IIS, the .NET framework or to ASP.NET? There may be multiple issues masking the original problem.

Also, you stated 64-bit, but Crystal Reports Server XI is a 32-bit application, so presumably you've got the 64-bit  IIS running as 32-bit.  If not, you wouldn't be able to use Infoview, I assume.

Something you might verify is to remove \ from the end of the URLs within IIS. There was a Microsoft patch, long ago, that broke Enterprise when there was  \ at the end of the url.  That shouldn't be the case now, but it doesn't hurt to check.

Please forgive the delay in my reply, our IT dept. is stretched thin.

To answer your questions:

They are all running under either local service or service admin account. At any rate, the services in CCM are all running properly.

None of the updates appear to relate to IIS, .net or asp.net.

IIS is configured to run as 32-bit.

The "\" is removed within IIS, no change.

While talking to a former colleague, he seems to recall us having a similar issue and it turned out to be a corrupt file in Crystal Enterprise. He doesn't recall if it was a binary or config file, but replacing it seemed to work last time. Unfortunately, I was not involved with that incident so I have no notes or references. Is there a specific file that would "break" the handler for handler for .cwr extensions?

Again, thanks for your suggestions.

This problem was solved by my former colleague over the weekend. Here's what he did:

Here is a solution to this problem, for anyone who may be interested:

*On the 'App Mappings' tab, click the 'Add' button. The 'Add/Edit Application Extension Mapping' dialog box appears.  
 
*In the 'Executable' box, type "C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll" and in the 'Extension' box, type ".csp".  
 
*Click 'OK'. The 'Inheritance Override' dialog box appears.  
 
*Do not click 'businessobjects' or 'crystalreportsviewers11' nodes and then click 'OK'.  
 
*Repeat steps:  
 
Extension: .cwr  
Excutable: C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll  
 
Extension: .cri  
Excutable: C:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_isapi.dll  
 
Extension: .wis  
Excutable: C:\Progra ~1\Busine~1\Busine~1\win32_x86\cdzISAPI.dll  
 
*Restart IIS.  


Thanks for helping me troubleshoot, rhinok.