locked
The Request Record was not found or you dont have sufficient permision to view it ... RRS feed

  • Question

  • When I tried to Access CRM4.0 I got the Follwoing Error

    The Request Record was not found or you dont have sufficient permision to view it ...

    the Event Log error is the below ...  Any suggestion to kill this issue ...

    Event Type: Warning
    Event Source: ASP.NET 2.0.50727.0
    Event Category: Web Event
    Event ID: 1309
    Date:  10/04/2009
    Time:  12:09:48 AM
    User:  N/A
    Computer: TCF2
    Description:
    Event code: 3005
    Event message: An unhandled exception has occurred.
    Event time: 10/4/2009 12:09:48 AM
    Event time (UTC): 10/3/2009 9:09:48 PM
    Event ID: 1fa40eebbccd48c48b3e36f4700d0f53
    Event sequence: 3
    Event occurrence: 1
    Event detail code: 0
     
    Application information:
        Application domain: /LM/W3SVC/2/ROOT-1-128990777263858739
        Trust level: Full
        Application Virtual Path: /
        Application Path: C:\Program Files\Microsoft Dynamics CRM\CRMWeb\
        Machine name: TCF2
     
    Process information:
        Process ID: 4464
        Process name: w3wp.exe
        Account name: TCF\CrmServices
     
    Exception information:
        Exception type: CrmObjectNotFoundException
        Exception message: systemuser With Id = 49b8468c-4db0-de11-8f01-005056c00008 Does Not Exist
     
    Request information:
        Request URL: http://172.16.16.5:5555/default.aspx
        Request path: /default.aspx
        User host address: 172.16.16.5
        User: TCF\crmadmin
        Is authenticated: True
        Authentication Type: Negotiate
        Thread account name: TCF\CrmServices
     
    Thread information:
        Thread ID: 10
        Thread account name: TCF\CrmServices
        Is impersonating: True
        Stack trace:    at Microsoft.Crm.BusinessEntities.BusinessProcessObject.Retrieve(BusinessEntityMoniker moniker, EntityExpression entityExpression, ExecutionContext context, Int32[] deletionCodes, Int32 languageCode)
       at Microsoft.Crm.BusinessEntities.BusinessProcessObject.Retrieve(BusinessEntityMoniker moniker, EntityExpression entityExpression, ExecutionContext context)
       at Microsoft.Crm.Caching.UserDataCacheLoader.LoadCacheData(Guid key, ExecutionContext context)
       at Microsoft.Crm.Caching.ObjectModelCacheLoader`2.LoadCacheData(TKey key, IOrganizationContext context)
       at Microsoft.Crm.Caching.BasicCrmCache`2.CreateEntry(TKey key, IOrganizationContext context)
       at Microsoft.Crm.Caching.BasicCrmCache`2.LookupEntry(TKey key, IOrganizationContext context)
       at Microsoft.Crm.BusinessEntities.SecurityLibrary.GetUserInfoInternal(WindowsIdentity identity, IOrganizationContext context, UserAuth& userInfo)
       at Microsoft.Crm.BusinessEntities.SecurityLibrary.GetCallerAndBusinessGuidsFromThread(WindowsIdentity identity, Guid organizationId)
       at Microsoft.Crm.Authentication.CrmWindowsIdentity..ctor(WindowsIdentity innerIdentity, Boolean publishCrmUser, Guid organizationId)
       at Microsoft.Crm.Authentication.WindowsAuthenticationProvider.Authenticate(HttpApplication application)
       at Microsoft.Crm.Authentication.AuthenticationStep.Authenticate(HttpApplication application)
       at Microsoft.Crm.Authentication.AuthenticationPipeline.Authenticate(HttpApplication application)
       at Microsoft.Crm.Authentication.AuthenticationEngine.Execute(Object sender, EventArgs e)
       at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
     
     
    Custom event details:

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Saturday, October 3, 2009 9:49 PM

Answers

  • It looks like the user doesn't have exist.

    You might want to do a

    SELECT DomainName 
    FROM SystemUserBase
    WHERE SystemUserId='49b8468c-4db0-de11-8f01-005056c00008'

    on the database to get more information about the user it couldn't find.
    Sunday, October 4, 2009 3:04 AM