I have been asked to move a system running MS SQL 2000 Server from a workgroup to a domain. The SQL server is running in SQL Authentication and the services are running as local system.
Will SQL Server break after the move?
Any advice will help. I thought I remember this being the case, but possibly only with Windows Authentication.
Hi have a small network setup and have MS sql server on workstation.Can access it locally but cannot access it from other work stations.I am assuming it is some sort of logon error, being it is not adomain. Any ideas on getting by this ?
View 2 Replies View Related
Hi folks,
For the past couple of days, I have been trying to get my SQL Server to work with Distributed Views. I am created linked servers, linked server logins, set XACT Abort ON.
I am successful in running a select against the distributed view, but was unable to run an "INSERT"
When I try a simple insert, the query took 3:14 minutes. Then I get an error message like:
Server: Msg 7391, Level 16, State 1, Line 1
The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.
[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]
OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].
I have checked that MSDTC is running and configured under a domain account on both machines - running sQL 2000 and win2K
I have been unsuccessful still after tinkering for several days. I have checked my network configurations and noticed that when I try to ping the other machine by name, I don't get a response. I can only get a response to a ping when I enter the IP address directly.
Could this be a problem? Also, I noticed that for some strange reason, whenever I ping from either machine it is showing an external IP - always the same one no matter which computer name I try to ping. Something like 209.xxx.xxx.xxx instead of the 192.xxx.xxx.xxx that I expect.
Finally, I thought that problem was possibly due to incorrect Active Directory configuration. I tried to remove both machines from the domain by changing them to a workgroup "TEST" instead of the domain.
When I restarted the PC, I am unable to start SQL Server. It shows the Red Stop sign. When I try to start it, it gives an error like: Service could not start because one or more dependencies failed.
When I add the machine back to the domain, SQL server starts working on reboot.
Can anyone help me please.
Thanks.
Hi,
I have a quick question regarding domains and workgroups.
Currently I am working on an issue in the office of a small business. Right now there are 3 client computers that connect to a dell server running windows std. server 2003. The server has sql running on it that takes care of the invoicing system. Two out of the three work stations are able to use the database fine, but there is one that is unable to connect to the database. The only different that I could find is that the two workstations that DO work are currently set to use a workgroup, whereas the one workstation that does NOT work is set to use a domain...... I tried switching that computer to workgroup, but then I was unable to login as the normal user that I had always logged in as before.....
What can I do to solve this dilemma?
Any help would be greatly appreciated!
I apologize if this is the wrong forum for this, and if it is, if someone would point me to the correct one I would appreciate it.
Thanks
-steve
I'm trying to establish connection between two SQL servers, one on a Domain and one on a Workgroup. When I log as the local administrator to the Domain machine, everthing is fine and both machines can register each other (both machines have the same local admin user name & password.) When I log back into the Domain on the Domain machine, I cannot register the Workgroup server but I can register Domain server from the Workgroup server. Putting the Workgroup machine on my Domain won't work because I'm going to be using a firewall. Do I need to set up another domain for the Workgroup machine and configure a trust on the Domain machine? Any suggestions?
View 2 Replies View RelatedMy company has a large-ish website and we are migrating to new
servers. There will be a web server (accessible to the world) backed
by a SQL Server 2005 Standard server (only accessible by the web server and
through VPN/Remote Desktop to administrators and our internal
network). We can either put the database server (which is not in a
cluster) on our domain or leave it in a workgroup. My first thought
is leave it in a workgroup simply for security and reliability (i.e.
if the DC goes down or loses connectivity), but people here are
disagreeing with me.
Should I put the database server (which is not used internally at all)
on the domain or leave it in a workgroup?
My company has a large-ish website and we are migrating to new
servers. There will be a web server (accessible to the world) backed
by a SQL Server 2005 Standard server (only accessible by the web server and
through VPN/Remote Desktop to administrators and our internal
network). We can either put the database server (which is not in a
cluster) on our domain or leave it in a workgroup. My first thought
is leave it in a workgroup simply for security and reliability (i.e.
if the DC goes down or loses connectivity), but people here are
disagreeing with me.
Should I put the database server (which is not used internally at all)
on the domain or leave it in a workgroup?
We have a set of client servers which will include a SQL Server 2000 active/passive cluster attached to a SAN. We have all the equipment here (no attachment to client site) to configure. My worry is since it will have to be setup as a workgroup, and then shipped to client to add to their domain, is this a doable option. has anyone had to do this or tried this? Or would we be better off shipping whole thing to client and setting up cluster there?
View 6 Replies View RelatedIn the following scenario, I am getting the message 'Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection'.
I am running a Windows Server 2003 with development environment and Sql Server Management Studio in a workgroup on a virtual PC.
My SQL Server 2000 is running on a domain server.
On the virtual Pc I have setup my user login and password to be the same as my domain login and password. Why is the Management Studio not using impersonation and allowing me to connect to the SQL server on the domain?
This question is regarding a brand new out-of-the-box SQL Server 2005 Workgroup Edition install. The old SQL Server 2000 server is working properly with regard to the issue we're having:
We are using Windows Authentication, and have created SQL logins for about
40 different groups on our domain. We've given those logins the appropriate
permissions on the databases they're supposed to be able to access.
The SQL Server is not a domain controller, but is a member of the domain, and domain logins do work for Windows-login purposes on this box.
The problem is that when users try to connect to the SQL server, they are denied access. An error 18456 is thrown, and logged in the Application event log
stating "Login failed for user OURDOMAIN heuser" (example values). The
domain user is properly a member of group added as a login to SQL Server, and we've
confirmed that there are not conflicting permissions that would deny those
users access via another route. These same groups are working fine on the SQL Server 2000 box.
This is only a problem for domain-based groups. If we create a local group
on the SQL server machine, through Computer Management -> Local Users and
Groups, then make the same domain users a member of THAT group, and finally then
follow the same process to add that local group to SQL Server Logins and set
the database privileges, it works!!
Our group memberships change frequently, and are used for a lot more than
just SQL server permissions. So, using local groups and maintaining
membership in both places is not really feasible. Any ideas why a local
machine group containing domain user accounts would work fine, but a domain
group containing the same accounts would not?
Thanks in advance.
I have SQL 2000 running on windows 2000 using NT4 authentication all my users authenticate to the NT4 including their access to SQL 2000, we are moving to a new domain using windows 2003 server and Active Direcory.
We will be a an OU in a much larger domain (about 30K users) since we need to be able to be up and running with ability to authenticate and run all our apps including SQL server authentication in the event we loose our connectivity to the rest of the world should a natural disaster hit us.
Here is my dilema, when I see my users in SQL security they all have domainuserdID where the domain is my old domain.
How do I move all my SQL users with their rights to the new Windows2K3 SQL server that will authenticate to a Windows2K3 Active Directory.
I have 300 users and I do not want to have to create each one all over again in SQL, they allready exist in Active Directory I migrated all the users last week but i still have them authenticating to the old domain till I can resolve the SQL issue.
What is an easy and proper way to what I need to do
Thanks
Xavier
Currently running a SQL 2000 server in 2000 domain and want to migrate it to a new 2003 domain of the same name.
How do I go about it and is there any problems with this plan?
Hello,I need to move 6 SQL Servers from existing domain to a new domain.Currently all SQL Server servies are started using the domain accountof old domain.What precautions and steps are necessary for migration from one domainto another. Also note that the name of the servers needs to be changedin the new domain .ThanksSrinivas
View 5 Replies View Related
We have:
A Microsoft cluster, (SQL Failover cluster) with one node as the domain controller. The cluster was built off site and the domain name used is the same as our existing domain where we eventually need to install this cluster.
We need: (At least I think we need:)
To remove node 2 from the "cluster domain", DCPROMO node 1 and eliminate the "cluster domain". We then need to join the cluster (nodes) to the existing domain. We also need to recreate the accounts/groups used during installation.
Questions:
1) What adverse impact will the removal of the "cluster domain" have on the security groups/accounts used in the installation?
2) Will I have to re-install SQL 2005?
3) Is my paranoia real or imagined? (Will Elvis live?) Am I on the right track or totally off base?
Any prior experience with this would be greatly appreciated. In fact, a WAG is appreciated too.
Regards,
Mike
hi
COMPUTER-1
IP ::::: 129.100.100.5
COMPUTER NAME IS ::::: HASH
MEMBER OF DOMAIN
in this computer sqlserver express edition is installed, i want to remove this express becoz in configuration manager it show two SQLSERVER'S are running. when i browse from COMPUTER - 2 for network servers it show server name as HASH/SQLEXPRESS, but not the main SQLSERVER.
COMPUTER -2
IP::::129.100.100.142
COMPUTER NAME::: FEROZ
MEMBER OF WORKGROUP
can anyone help me how to connect these two computers and remove this express edition
iam new to sqlserver configuration
thanks in advance
waiting for eager reply
Please help to connect SQL server 2000 on different domain.
Please correct if I m wrong.
System details as follows
Client
Domain : DomainA
System : System1
IP Address : 10.10.225.19
SQL server 2000 installed
SQL Server
Domain : DomainB
System : System2
IP Address : 10.108.22.19
SQl Server : System2inst2 ( My database is under inst2 instance)
SQL login : TestUser1
Password : Users123
I have Opened firewall port to access 10.108.22.19 from 10.10.225.19
While connecting the SQL server €śSystem2inst2€? from the client machine enterprise manager with the SQL authentication, I am getting error Login failed for user €śTestUser1€?
And I have noticed in the SQL server log the login attempt shows under System2 default instance ( no instance). Actually I want to connect system2inst2.
Please let me know the steps to connect.
Thanks in advance.
Hello,
I'm in the process of moving a SQL Server 2000 to a new server. I have installed the new server added the latest sp. When I try to restore the system databases (Master, msdb) I get the following error
"the database xxxx.bak Cannot be restored because it was created by a different version of the server restore database is terminating abnormally"
I have looked at everything that I know of and both servers seem to be running the same versions of everything.
Can I just export the databases the the new server?
thanks in advance for any help you can give.
Jason
Hello everybody..Is there a way to fix the SQL Server 2000 installation when the Server afterthe server has been disjoined form its old domain and added to a new domainwith a different computer name too?Sounds like a joke, but stuff happens.TIA-arifi
View 3 Replies View Related
Greetings,
I have been tasked with changing our local domian name from .com to .local. I want to make sure I understand the risks to SQL server 2000 when i make this change. We use SQL for Great Plains version 8, here is my simple plan:
1. Dis-join all workstations from .com domain
2. Make a full backup of all databases iin SQL server 2000 -- all databases use the SA account and not NT authentication
3. Dis-join SQL server
4. Change domain name
5. Re-join SQL server box and workstations
6. Launch Great Plains and go home happy!
I am having trouble identifying the risk to my plan and am wondering if:
1. SQL will launch under the new domain
2. Will the backup I made restore under the new domian
3. Will I experience authentication problems even though we use the SA account?
I am not a DB admin and am feeling a little unsure about this task any help on the risks or links to "how to" guides would be appreciated.
Robert
We needed to replace our Motherboard on a server running win 2K Adv.Server with SQL server 2000. After replacing, we could not bringthe system back with the previous OS. So, we have decided tomigrate to Windows 2003 server and install SQL svr on it.On the old server, the SQL DB is residing on a seperate disk.Is there any way one can install SQL on the new server and importthe data from the disk. Many posts talk about how to do detach/attach etc.The case there is they have a running source server. In my case, I don't.any pointers will be appreciatedRegards,Anand
View 1 Replies View RelatedHi,
My server administrator has created a few users as domain user privilege for connecting SQL server from my application. However it faild to connect, and
with Domain Admin privilege, my app is running ok.
I asked admin person to upgrade domain user privilege to connect SQL server,
but he couldn't do this for security reason, and told it should work with domain user.
Is it true for domain user to connect SQL server without any problem?
Do I need to add the user, domain user, into Logins of Security inside SQL server Enterprise Manager?
Or inside users of my database section of SQL server EManager?
Thanks,
dixon
Hi all,Have a situation that my company has never run across before. Clientis running NT4 for the domain server, using terminal services 2000 andrunning an application with a SQL Server backend and they areexperiencing locking problems. Once one person gets locked out theneveryone trying to access that tables is also locked out as a result.It is not specific to a certain User, or module within theapplication. It's not a specific time of the day (like when a backupwould be running) and sometimes it's in the middle of the night whenthere are actually less Users on the system.We have 500 customers using this application. Most are using SQLServer backend, alot of the newer customers are using TerminalServices, and the number of Users is not accessive as compared to ourother customers. THe only difference is that I do not specificallyknow of another client with an NT4 Domain server in the mix.We actually switched to SQL Server as the recommended back end due tolocking issues using SQLBase because SQL Server is row locking andSQLBase is page locking. Since making this change we have stoppedseeing the locking for years until now. Is this a SQLServer issue orissue with the NT Domain server?Anyone have any ideas???ThanksA
View 3 Replies View RelatedSubject problem has me quite vexed.
I am receiving the following error when attempting to access reporting services... to sum things up real nice and tidy-
I get three login prompts - then the access denied response. It is almost as if it is unable to authenticate the user... anyway... here's the actual error response, I'd really appreciate any input/insight/resolution.
Server Error in '/Reports' Application.
Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.UnauthorizedAccessException: Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.
ASP.NET is not authorized to access the requested resource. Consider granting access rights to the resource to the ASP.NET request identity. ASP.NET has a base process identity (typically {MACHINE}ASPNET on IIS 5 or Network Service on IIS 6) that is used if the application is not impersonating. If the application is impersonating via <identity impersonate="true"/>, the identity will be the anonymous user (typically IUSR_MACHINENAME) or the authenticated request user.
To grant ASP.NET access to a file, right-click the file in Explorer, choose "Properties" and select the Security tab. Click "Add" to add the appropriate user or group. Highlight the ASP.NET account, and check the boxes for the desired access.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[UnauthorizedAccessException: Access to the path 'C:Program FilesMicrosoft SQL ServerMSSQL.2Reporting ServicesReportManagerin' is denied.]
System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) +2014163
System.IO.Directory.InternalGetFileDirectoryNames(String path, String userPathOriginal, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption) +1817
System.IO.Directory.GetDirectories(String path, String searchPattern, SearchOption searchOption) +36
Microsoft.ReportingServices.Diagnostics.Localization.GetInstalledCultures() +112
Microsoft.ReportingServices.Diagnostics.Localization..cctor() +66
[TypeInitializationException: The type initializer for 'Microsoft.ReportingServices.Diagnostics.Localization' threw an exception.]
Microsoft.ReportingServices.Diagnostics.Localization.SetCultureFromPriorityList(String[] localeList) +0
Microsoft.ReportingServices.UI.GlobalApp.Application_BeginRequest(Object sender, EventArgs e) +157
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
How to import database in SQL server 2005 from the SQL server 2000 ??
I need to move the SQL Server 2000 Desktop Engine (MSDE) database and all jobs to the SQL Server 2005 Enterprise Edition.
- May I detach and attach the DB in my case?
- Where is the procedure to move the jobs from MSDE to SQL Server
2005?
We have a SQL Server 2000 ent edition sp4 with 3 small databases and one 4 GB database which is REPLICATED
The Server has been bouncing like a yoyo today because of a disk controller problem and I am preparing to move the Instance to a whole new server this afternoon. The new Server will have the same IP and name as the original server.
Any suggestions for the easiest or most seamless way to make this happen? preferably using Backup and Restore since they plan on taking the old server down completely and then building a new server with the same name and IP ... any suggestions would be appreciated.
I will be installing a new, SBS2003 R2 server that comes with SQL 2005 Workgroup Edition. We currently have a SQL 2000 Standard server. Can I installed SQL2000 Standard on SBS2003 R2? The reason for this is that we're not ready to migrate to SQL2005 and we need to continue running SQL2000.
Thanks.
We have 3 MSDE databases (3 seperate servers) which we need to make into one Sql 2000 server (new server). How is this done? Can't find anything clear about this.
Thanks
Is this even possible? I tried to move an existing Sql Server Express .mdf file to SQL Server 2000 by copying the .mdf file to the server's folder and then tried to attach it. I get:
Error 602: Could not find row in sysindexes for database ID 9, object ID 1, index ID1. Run DBCC CHECKTABLE on sysindexes.
I realize that I'm moving back a version in SQL, however the structure of the database is very simple. Does anyone know?
Even if I can just script the thing to SQL 2000 would be helpful, however the .mdf is a file within my ASP.Net site, and does not show up in my Microsoft SQL Server Management Studio Express under the appropriate SERVERNAMESQLEXPRESS either, so I can't figure out how to script it out?
Hi guys,
I have tried to use the sp_help_revlogin script to move logins from a sql 2000 server to a sql 2005 server. It works for users that have a password. But if the password is blank it will fail. Is there a work around for this since I can't change the users passwords?
I have also tried SSIS package but that too doesn't work because of the same reason.
Can anyone help...
I'm trying to run a test from my test environment which is a non-domain Windows 2000 server to access my domain 2003 with SQL2005. I have install 2005 tools to try to access the SQL server.
- I have try following the KB265808 - no success.
- Reading alot of blogs and it seems all are pointing to the same problem. "Remote access" but the settign is enabled.Error Message:
TITLE: Connect to Server
------------------------------
Cannot connect to ardsqldatawh.
------------------------------
ADDITIONAL INFORMATION:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 53)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
Question: Could Windows 2003 security be blocking access? I'm using sa account to access.
Also, sa account does not seems to work for remote access. It is ok when accessing locally.
Any help would be appreciated.
949jc
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
View 1 Replies View Relatedhow can we manage the db transfer when we are upgrading from 2000 to 2005? what is the right way to do that? where can we find something to read about it?
View 1 Replies View Related