The 'CRM_FullName' parameter is missing a value

James

I recieved the error The 'CRM_FullName' parameter is missing a value when
running any report that has a parameter to it, even the ones we have created.
This seems to be happining for every user and I have not been able to resolve
it. I have recently upgrade from SQL 2000 to 2005 which had some issues so I
then had to uninstall SQL and start fresh with 2005.

Tyler Peelen [MSFT]

What kind of result do you get when you execute this query against your
organization database: select fullname from FilteredSystemUser where
systemuserid = dbo.fn_FindUserGuid()

That's the query we use to populate the CRM_FullName in most of our
out-of-the-box reports. With the reports that you've created, do you use
similar code?


Tyler Peelen
Software Development Engineer
Microsoft Dynamics CRM

--------------------
This posting is provided "AS IS" with no warranties, and confers no rights.


"James" wrote:

> I recieved the error The 'CRM_FullName' parameter is missing a value when
> running any report that has a parameter to it, even the ones we have created.
> This seems to be happining for every user and I have not been able to resolve
> it. I have recently upgrade from SQL 2000 to 2005 which had some issues so I
> then had to uninstall SQL and start fresh with 2005.

James

Tyler,

Thank-you for the reply, it seems you are on the right track. The script you
provided returns a blank, I also went ahead and looked at the
filteredsystemuser view and it was empty. Do you have any suggestions on how
to resolve this?



"Tyler Peelen [MSFT]" wrote:

> What kind of result do you get when you execute this query against your
> organization database: select fullname from FilteredSystemUser where
> systemuserid = dbo.fn_FindUserGuid()
>
> That's the query we use to populate the CRM_FullName in most of our
> out-of-the-box reports. With the reports that you've created, do you use
> similar code?
>
>
> Tyler Peelen
> Software Development Engineer
> Microsoft Dynamics CRM
>
> --------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "James" wrote:
>
> > I recieved the error The 'CRM_FullName' parameter is missing a value when
> > running any report that has a parameter to it, even the ones we have created.
> > This seems to be happining for every user and I have not been able to resolve
> > it. I have recently upgrade from SQL 2000 to 2005 which had some issues so I
> > then had to uninstall SQL and start fresh with 2005.

ChrisC

I think you need to verify that the report running AD user is a member
of the CRM specific groups, and also registered in the CRM, because
that is how the filtered views are formed.

James

Chris,

I have checked and the AD user I am running the SQL Reporting Service as
well as the AD user running the report are both members of the CRM Groupd;
ReportingGroup and UserGroup

"ChrisC" wrote:

> I think you need to verify that the report running AD user is a member
> of the CRM specific groups, and also registered in the CRM, because
> that is how the filtered views are formed.
>

Dave S

Hi James, I had the same thing happen to a client of mine.

Check the CRM user logon name in the CRM Users and compare to the Logon name
in the users AD properties.

My client had changed their AD Logon name after I had added them to CRM.
This can (and did for me) mess things up but not always.

Just 1 more possible solution.
Dave

Tyler Peelen [MSFT]

If a query against FilteredSystemUser returns no rows, then I think you are
definitely running into a problem with the fn_FindUserGuid function which
translates logon names to SystemUserId's.

What kind of result do you get with the following query?:
SELECT SUSER_SNAME()

Now compare that result to the contents of the DomainName column in the
SystemUserBase table (or SystemUser view). My guess is that there is a
mismatch between the two pieces of information.

If there is a mismatch, your problem should go away if you can update the
DomainName attributes of your users so that they match the SUSER_SNAME
paradigm. This can be done one-by-one through the application or in bulk
through the SDK.

--Tyler

--------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

"James" wrote:

> Tyler,
>
> Thank-you for the reply, it seems you are on the right track. The script you
> provided returns a blank, I also went ahead and looked at the
> filteredsystemuser view and it was empty. Do you have any suggestions on how
> to resolve this?
>
>
>
> "Tyler Peelen [MSFT]" wrote:
>
> > What kind of result do you get when you execute this query against your
> > organization database: select fullname from FilteredSystemUser where
> > systemuserid = dbo.fn_FindUserGuid()
> >
> > That's the query we use to populate the CRM_FullName in most of our
> > out-of-the-box reports. With the reports that you've created, do you use
> > similar code?
> >
> >
> > Tyler Peelen
> > Software Development Engineer
> > Microsoft Dynamics CRM
> >
> > --------------------
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "James" wrote:
> >
> > > I recieved the error The 'CRM_FullName' parameter is missing a value when
> > > running any report that has a parameter to it, even the ones we have created.
> > > This seems to be happining for every user and I have not been able to resolve
> > > it. I have recently upgrade from SQL 2000 to 2005 which had some issues so I
> > > then had to uninstall SQL and start fresh with 2005.

James

Thank-you for the pointers.

Not sure if this makes sense but I ran the fn_FindUserGuid in a querry and
it seemed to have populated the FilterSystemUser view so now when I run,
select fullname from FilteredSystemUser where
systemuserid = dbo.fn_FindUserGuid() , it populates with my user full name.
I also checked the SELECT SUSER_SNAME() against the DomainName attribute in
the SystemUserBase and they matched up but I still seem to be getting the
same error when I run the reports.

Any further pointers would be greatly appriciated


"Tyler Peelen [MSFT]" wrote:

> If a query against FilteredSystemUser returns no rows, then I think you are
> definitely running into a problem with the fn_FindUserGuid function which
> translates logon names to SystemUserId's.
>
> What kind of result do you get with the following query?:
> SELECT SUSER_SNAME()
>
> Now compare that result to the contents of the DomainName column in the
> SystemUserBase table (or SystemUser view). My guess is that there is a
> mismatch between the two pieces of information.
>
> If there is a mismatch, your problem should go away if you can update the
> DomainName attributes of your users so that they match the SUSER_SNAME
> paradigm. This can be done one-by-one through the application or in bulk
> through the SDK.
>
> --Tyler
>
> --------------------
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "James" wrote:
>
> > Tyler,
> >
> > Thank-you for the reply, it seems you are on the right track. The script you
> > provided returns a blank, I also went ahead and looked at the
> > filteredsystemuser view and it was empty. Do you have any suggestions on how
> > to resolve this?
> >
> >
> >
> > "Tyler Peelen [MSFT]" wrote:
> >
> > > What kind of result do you get when you execute this query against your
> > > organization database: select fullname from FilteredSystemUser where
> > > systemuserid = dbo.fn_FindUserGuid()
> > >
> > > That's the query we use to populate the CRM_FullName in most of our
> > > out-of-the-box reports. With the reports that you've created, do you use
> > > similar code?
> > >
> > >
> > > Tyler Peelen
> > > Software Development Engineer
> > > Microsoft Dynamics CRM
> > >
> > > --------------------
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > >
> > >
> > > "James" wrote:
> > >
> > > > I recieved the error The 'CRM_FullName' parameter is missing a value when
> > > > running any report that has a parameter to it, even the ones we have created.
> > > > This seems to be happining for every user and I have not been able to resolve
> > > > it. I have recently upgrade from SQL 2000 to 2005 which had some issues so I
> > > > then had to uninstall SQL and start fresh with 2005.

ChrisC

Seems like the impersonation is not getting through to the
reportserver - might be a setting in a config file
-Chris

James

Do you have any idea which setting it may be, also would it be in the CRM
web.config or the reportserver web.config?

"ChrisC" wrote:

> Seems like the impersonation is not getting through to the
> reportserver - might be a setting in a config file
> -Chris
>