Integraged to Sharepoint mode, credential problems

I think I have Sharepoint and Reporting services correctly installed to use
windows trusted accounts, (using domain Active Directory logins, but not
Kerberos).
While writing my report, I designed the data set to use windows
authentication (instead of a SQL Server authentication).
From the Report Designer,(report runs fine) the deploy repeatedly asks for
Reporting Services login and won't accept any account credentials at all.
I can upload the report using Sharepoint but when I run the report I get
this error message: "An error has occurred during report processing. This
data source is configured to use Windows integrated securi6ty. Windows
integrated security is either disabled for this report server or your report
server is using Trusted account mode."
Thanks for any assistance,
ShirleyIf using the MOSS 2007 (Microsoft Office Sharepoint Server) , check that the
settings in the Reporting Services Managemnet section for security is set to
Windows Integrated and not Trusted.
"ShirleyH" wrote:
> I think I have Sharepoint and Reporting services correctly installed to use
> windows trusted accounts, (using domain Active Directory logins, but not
> Kerberos).
> While writing my report, I designed the data set to use windows
> authentication (instead of a SQL Server authentication).
> From the Report Designer,(report runs fine) the deploy repeatedly asks for
> Reporting Services login and won't accept any account credentials at all.
> I can upload the report using Sharepoint but when I run the report I get
> this error message: "An error has occurred during report processing. This
> data source is configured to use Windows integrated securi6ty. Windows
> integrated security is either disabled for this report server or your report
> server is using Trusted account mode."
> Thanks for any assistance,
> Shirley
>

Installing SQL 2k Ent in AD environment

While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
Directory environemnt, I have noticed two things different from
installing in a non-AD environment.
1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
continue.
2. After the install is completed, I can not connect to the server
using Windows authentication. When I try to register the server in
Ent Mgr using my windows login information, I get the following error:
Cannot Generate SSPI Conext Error
I do not get this if I register the server using the sa account.
Do I have to do something different in the Active Directory before
installing SQL Server 2k?
Thanks
JonI don't know about the 1st question, but for the 2nd use the "HOW TO:
Troubleshoot the "Cannot Generate SSPI Context" Error Message" KB article at
http://support.microsoft.com/default.aspx?scid=kb;en-us;811889.
--
Dejan Sarka, SQL Server MVP
Associate Mentor
Solid Quality Learning
More than just Training
www.SolidQualityLearning.com
"jtw" <jwright@.mailboxspot.com> wrote in message
news:l3qo00dcrgja0l7ih0blnucgs2nural6s1@.4ax.com...
>
> While installing SQL Server 2k Ent Ed on a Win2k Server in an Active
> Directory environemnt, I have noticed two things different from
> installing in a non-AD environment.
> 1. Using the MS SELECT CD, I am prompted to enter CD-KEY. Normally,
> SELECT CDs do not prompt for cd-key. I entered all 1s and was able to
> continue.
> 2. After the install is completed, I can not connect to the server
> using Windows authentication. When I try to register the server in
> Ent Mgr using my windows login information, I get the following error:
> Cannot Generate SSPI Conext Error
> I do not get this if I register the server using the sa account.
>
> Do I have to do something different in the Active Directory before
> installing SQL Server 2k?
>
> Thanks
> Jon
>

Installing SQL 2000 On active/active cluster

I am trying to install SQL 2000 Ent on a Win2k3 cluster.
I have check both local and domain privlages and they are good.
I have performed MS work around so SQL sp2 and below can be installed on win2k3.
And I keep getting the following error during install...

An error occurred while creating virtual server resources for
clustering.Cluster specific registry entries couldn't be written.

Does anybody have any ideas?Check the privilages for the service account and the Account in which you logged in for Installation has folloing privilages .

Part of Local Admin
In Local Policy
1. Act as part of operating system
2. Log on as service
Make sure in the services :Remote registry service is up|||Privlages are good and remote registry service is running !|||Did you manage to resolve this issue? Did you get any USEFULL help from Microsoft support? Please post a few words of wisdom if so.

We have exactly the same problem and I've been struggling with it for a few weeks. Any help/advice is welcome.

I use SQL 2000 EE SP3 install (i.e with SP3 already included in installation) and still get the same error: "cluster-specific registry could not be written". All the simptoms are the same. I can install single-node virtual server, but if I try to install on both-nodes I've got mentioned message. The same happens if I try add second node to successfully installed single-node virtual server.|||My issue ended up being security on the cluster was to tight.
Once I loosened my security policies it started working fine.
Specifically the registry was being locked down by a Windows 2000 DC which does'nt have all the proper setting that Windows 2003 has.
I eventually upgraded the DC to 2003 to help with this matter.

INstalling sp3a on second node

I have a active/passive cluster with W2K Adv. and SQL 2000.
I was having the issue with setting up SQL on the second node. I fixed issue by installing directly onto the second node. But their is no option with the sp3a to install onto the second node locally. The same issue that happened with trying to remote inst
all with the primary node. The install failed because of a timeout issue. Error 121. All of my settings and correct accounts are setup. The person who told me to install directly on the second node to
install SQL stated that this was actually a known problem. What is the fix for the service packs if you cannot install remotely? It looks like sp3a installed correctly because when I ran query analyzer the version that showed up was sp3a. Any comments wou
ld be appreciated.
Thanks,
dcaldwell
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
There is no 'first node' and 'second node' concept in SQL 2000 clustering.
All nodes are equal. The only difference is what node is currently hosting
the instance. Adding and removing nodes is a different process and is well
documented in BOL. It sounds like you built the cluster on a single node or
applied the service pack with one node offline. Normal installation of SQL
Service packs will update all nodes at the same time if it is run from teh
node currently hosting the instance. If you need to reapply a service pack
to update binaries on a newly added or replaced node, you must run the
Service Pack from the 'new' node while hte SQL instance is hosted on an
'old' node. This is documented in the Service Pack readme file.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:%23%23T55iTgEHA.3272@.TK2MSFTNGP11.phx.gbl...
> I have a active/passive cluster with W2K Adv. and SQL 2000.
> I was having the issue with setting up SQL on the second node. I fixed
issue by installing directly onto the second node. But their is no option
with the sp3a to install onto the second node locally. The same issue that
happened with trying to remote install with the primary node. The install
failed because of a timeout issue. Error 121. All of my settings and correct
accounts are setup. The person who told me to install directly on the second
node to
> install SQL stated that this was actually a known problem. What is the fix
for the service packs if you cannot install remotely? It looks like sp3a
installed correctly because when I ran query analyzer the version that
showed up was sp3a. Any comments would be appreciated.
> Thanks,
> dcaldwell
>
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.
|||What do you mean by "I fixed issue by installing directly onto the second
node. "
Did you install a local, non-clustered installation on the second node?
Perhaps now is a time to uninstall that local copy, and reinstall back as a
virtual SQL Server. You can find a clustering installation white paper at:
http://www.microsoft.com/technet/pro.../failclus.mspx
Chris Skorlinski
Microsoft SQL Server Support
Please reply directly to the thread with any updates.
This posting is provided "as is" with no warranties and confers no rights.