Login failed for user '(null)'

I have several reports using the same database with the same credentials
(using a specific Username and Password). All display fine, except for one
that gives me the following Reporting Services Error:
An error has occurred during report processing. (rsProcessingAborted) Get
Online Help
Cannot create a connection to data source 'BCSpotBonus'.
(rsErrorOpeningConnection) Get Online Help
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
I've configured the data in the same way as the other reports and I've tried
using the "Shared database option" and not using the "Shared database
option." Nothing works. How can this be happening?That shouldnt be happening , but even i had the same
problem.
In the Report Designer try to delete the datasource and
then add it again and re deploy the report. Then try to
view the report.
Hope this helps!
>--Original Message--
>I have several reports using the same database with the
same credentials
>(using a specific Username and Password). All display
fine, except for one
>that gives me the following Reporting Services Error:
>An error has occurred during report processing.
(rsProcessingAborted) Get
>Online Help
>Cannot create a connection to data source 'BCSpotBonus'.
>(rsErrorOpeningConnection) Get Online Help
>Login failed for user '(null)'. Reason: Not associated
with a trusted SQL
>Server connection.
>I've configured the data in the same way as the other
reports and I've tried
>using the "Shared database option" and not using
the "Shared database
>option." Nothing works. How can this be happening?
>.
>

Login does not exist - Error 15401

Hello,
Our IT Infrastructure group had recently renamed the Windows login username
from Bob_J to JBob. When I tried to add the new login with the new username
after the change, I received the error '15401: Windows NT user or group 'Cor
porate\JBob' not found. Che
ck the name again.' I used the sp_revokelogin to drop that login but it stil
l did not allow me to add the new username. I know the issue related to SID
but I had removed the login according KB324321.
If I added the login 'Corporate\Bob_J' back, it was fine. Under User Manager
, user Bob_J no longer exists. Have anyone had experience with this? If so,
how can I correct it? Do I not have a choice by either using the old usernam
e or create a new Windows l
ogin user? Any help will be greatly appreciated. Thank you.This could be ralated to the following article:
http://support.microsoft.com/?kbid=329420.
SQL Server uses the function mentioned in the article. If you have SP4 of
Windows 2000 installed this may not be the problem. The quick resolution is
to reboot all serves involved starting with the SQL Server to see if that
will resolve the problem and then the domain controller.
Rand
This posting is provided "as is" with no warranties and confers no rights.

login case senssitive

I would like to have a login page that is case senssitive. Right now the userName field in DB store Example :"John", but it allow the user to log in even if he types "john". Is the any SQL statement that select only if if name match and the case are match?::Is the any SQL statement that select only if if name match and the case are match?

=

I assume you use "Like". "Like" ignores case.

Now- otos - does your request make sense? I mean

::I would like to have a login page that is case senssitive. Right now the userName field in
::DB store Example :"John",

If "John" and "john" are different users, you open pandora's box for people mixing this up.

Our security systems ware case insensitive and store - besides the "DisplayName" also a "UniqueName" (name in lower cases), which triggers a unique constraint.

Having two users that differentiate their name only by casing sounds to me like a terrific bad idea. I can imagine the support calls coming in.|||The reason for case sensitive is because later on in my application i am using the user name and it has to be at certain form.
my select statement is:
"SELECT* FROM[FrenchRoast].[shikozel_db].[Chef] WHERE (([Chef].[Name] = @.Name) AND ([Chef].[Password] = @.password))"

I dont use like.
thank you.help...|||::The reason for case sensitive is because later on in my application i am using the user
::name and it has to be at certain form.

With all respect, this is no rason to make logins case sensitive. All my arguments are true - you willget into trouble with people spelling their name wrong when logging in.

Btw - if this:

::AND ([Chef].[Password] = @.password))"

indicates that you store the password in clear text in the database, then PLEASE get an introduction book on security. Storing the paswords in the database opens you up for a lot of not-funny things, including a tremendous amount of legal liability in case something does go wrong - without any legal defence, as it is gross neglect. Passwords should never ever be stored in the database.|||thank you for your comment. Where should i store passwords? any tutorial or books?|||::Where should i store passwords?

You should never ever store passwords. Look at how modern operating systems do it - they also never store passwords.|||Thona is correct, case sensitive passwords are a bad design and clear text pw's are equally as bad from a security stand point, so I recommend you read up on MD5.