Service Calendar error

I am getting a "Record Is Unavailable" error whenever I click on the
Service Calendar. This only started happening recently.

I suspect that this may have something to do with the fact that I
deleted cases/service appointments (using the CRM application) that
used to be on the service calendar. Has anyone else encountered this
error? Do you know how it can be resolved? I have pasted the stack
trace below in case it is useful. Help will be very much appreciated.

SoapException: Server was unable to process request.]

System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean
asyncCall) +1496
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters) +218
Microsoft.Crm.Platform.Proxy.ScheduleWebService.QueryMultiple(Guid[]
resourceIds, CrmDateTime start, CrmDateTime end, TimeCode[] timeCodes)
+103
Microsoft.Crm.Application.SMWrappers.Schedule.QueryMultiple(Guid[]
resourceIds, DateTime startDateTime, DateTime endDateTime) +59
Microsoft.Crm.Application.Controls.GanttContent.Render(TextWriter
writer) +438
Microsoft.Crm.Application.Controls.AppGantt.Render(HtmlTextWriter
output) +176
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +72
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +243
System.Web.UI.Page.ProcessRequestMain() +1926

Nahi
Thu Dec 29 20:39:44 CST 2005

Never mind. Problem went away.

knezi
Wed Jan 11 06:51:02 CST 2006

How did you solve this problem?

Need help, becuase i've got exact the same problem :-(

"Nahi" wrote:

> Never mind. Problem went away.
>
>

Nahi
Wed Jan 11 16:48:40 CST 2006

In my case it's because I was doing something illegal :{.

I had an issue where for some unknown reason a user could not log into
CRM. Didn't make any sense so I went about fixing the problem the brute
force way i.e. removing the user from the database and re-adding them
from the front end. Problem is that I didn't clean up properly - the
user is also added to a table called ResourceBase that does not seem to
have the proper referential integrity as all the other tables do (i.e.
let me delete a user without deleting the user from the ResourceBase).

Anyway that caused the issue. Once I deleted the user from ResourceBase
the problem went away. Don't feel so bad about the above approach
because a) what can you do when all else fails? and b) it was our own
internal beta version.