Showing posts with label ent. Show all posts
Showing posts with label ent. Show all posts

Friday, March 23, 2012

Installing SQL Server on XP Pro

I thought SQL Server allowed installation on XP Pro? For some reason I am getting an error. SQL Server Ent. 2000 is telling me that it does not support XP Pro. Is there a work around for this? I don't want to have to rebuild by box just to isntall SQL server!No, the Enterprise Edition is not supported on Windows XP Pro. Itrequires a server version of Windows. But you can install otherversions; seethis page.
Don
sql

Friday, February 24, 2012

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/defaul...b;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...
quote:

>
> 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 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
>

Sunday, February 19, 2012

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.