Reporting: SQL Error "Login Failed for user (null)" 1

[Stevehewitt]

Hi Guys,

Getting the following error when I try to access the reporting website:

An error occurred when the report was run. The details are as follows:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Error Number: -2147467259
Source: Microsoft OLE DB Provider for SQL Server
Native Error: 18452


I must be doing something wrong, but can anyone give me a step-by-step guide into how the SQL/Authentication side of things should be setup?

Much appreciated.


Steve.

 

[ncotton]

Have you got IIS's Web Reporting Tools installed?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[ncotton]

If it is, check your global.ada file : c:\Inetput\

http://wwwroot\SMSReporting_xxx

(xxx = sitecode)

There should be a section of Consts and Dims then some session deffinitions.

Check these are correct. Maybe increase the timeout a little, just incase its a big report, it is possible that a slow server could cause it to time out.

if all seems fine.
at the bottom of the sessions sections add these lines.

Session("strConn")= "Provider=SQLOLEDB.1;Network=DBMSSOCN;User ID=" & sUser & ";Password=" & sPassword & ";Initial Catalog=" & sCatalog & ";Data Source=" & sSource

Make sure you backup the original global.asa first!!!!


Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[ncotton]

I forgot to mention.....make sure you have the Reporting Point role set in the Site Systems > SiteServer.

If it is already installed.....Uncheck the "Use this system as a reporting point" > Click OK > Reboot the Site Server > Go back to Site Systems > SiteServer > Re-check the box, this will reinstall the SMSRP.exe (i think its called).

That is also the possible cause.

Have you ever had reporting working on it? If not, is it an upgrade from a SMS2.0?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[Stevehewitt]

Hi Nick,

Thanks for your help.

I'm completely new to SMS, and i'm afraid I've never heard of IIS's Web Reporting Tools - however if I go to

http://server/SMSReporting_site/

then I do get everything else - just the navigation window to the left brings up the error.
If I try to run a report from the admin console then I just get the error and nothing else.

I've added the connection string you posted above - but it hasn't worked either.

Any other ideas appreciated.

Cheers,


Steve.

 

[ncotton]

Go to System Status int he SMS Admin Console. see if there are any errors or warnings.

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[Stevehewitt]

Hi,

Yeah, there's a few - but after reviewing them I can't see anything that would affect reporting / SQL authentication etc.
(Just items such as failed to install client - access denied etc)

This is a new installation on a Win2k3 DC.

Thanks again,


Steve.

 

[ncotton]

I don't know if you skipped over this post, or just didn;t mention checking it, but here it is again.

I forgot to mention.....make sure you have the Reporting Point role set in the Site Systems > SiteServer.

If it is already installed.....Uncheck the "Use this system as a reporting point" > Click OK > Reboot the Site Server > Go back to Site Systems > SiteServer > Re-check the box, this will reinstall the SMSRP.exe (i think its called).

That is also the possible cause.

Have you ever had reporting working on it? If not, is it an upgrade from a SMS2.0?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant

 

[Stevehewitt]

Thanks again Nick.

The reporting role point is setup correctly

We've never has it working as it's a new install (never used the product before) - so it's not an upgrade either...

If it's any help, the SQL server is NOT the local server, it's another server on the same domain.

Cheers,


Steve.

 

[ncotton]

BTW - It's NEIL, not NICK!

Just to make sure, do the steps in the last post to uninstall the reporting point role, and then reinstall it. Never heard of this working with Reporting points, but is a common fix to Managmenet point and SLP problems, so for the 2 minutes it takes, it's worth a go.

Have you made the SMSServerMachine$ a Local Administrator on the SQL Server?

Is the SMSServerMachine$ in the SMSReporting AD Group?

Hope this Helps.

Neil J Cotton
njc Information Systems
Systems Consultant