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 a
domain. Any ideas on getting by this ?
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.
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,
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.
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
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
Hi,
We have the followoing:
-A "master domain" AD, a "sub domain" AD, a trust relationship between the two (sub trust master)
-A sql server 2005 on a win server 2003 in "sub domain" AD
-A linked server to "sub domain" AD
-A linked server login using a "sub domain" admin acccount
-A view to this linked server
-A grant on masterDomain/Domain Users to the database
-A grant on subDomain/Domain Users to the database
-We want all connections done through "Windows Authentication" not "Database Authentication".
Queries on the view work fine using "sub domain" user accounts.
Queries on the view fail using "master domain" user accounts (including master domain admin accounts)
"Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation."
All connections are done through "Windows Authentication" not "Database Authentication".
Can we establish cross domain connectivity with "Windows Authentication" ?
Below are details of the implementation:
SELECT TOP (100) PERCENT *
FROM OPENQUERY(ADSI,
'SELECT displayname, givenName, sn, cn (etc...)
FROM ''LDAP://OU=PEOPLE,DC=subDomain,DC=com''
WHERE objectCategory = ''Person'' AND objectClass = ''user'' ')
EXEC sp_addlinkedsrvlogin @rmtsrvname ='ADSI', @useself='false',
@rmtuser='subDomainAdminAccnt', @rmtpassword='sunDomainAdminAccntPassword';
In SQL Server Mngt Studio in Server Objects/Linked Servers/Providers/ ADSI properties security tab I have:
"connections will: <be made using this security context> Remote login:'subDomainAdminAccnt' With password: 'subDomainAdminAccntPassword'
Error:
Msg 7399, Level 16, State 1, Line 1
The OLE DB provider "ADsDSOObject" for linked server "ADSI" reported an error. The provider indicates that the user did not have the permission to perform the operation.
Msg 7320, Level 16, State 2, Line 1
Cannot execute the query "SELECT displayname, givenName, sn, cn
FROM 'LDAP://OU=PEOPLE,DC=subDomain,DC=com'
WHERE
objectCategory = 'Person'
AND objectClass = 'user'
" against OLE DB provider "ADsDSOObject" for linked server "ADSI".
We're running a simple network with a Windows XP Pro machine runningSQL Server. I have a VB application that runs fine on machines withinthe workgroup. There are several computers outside the workgroup butphysically reside on the network that generate OLEDB errors. I knowwith certainty it is establishing a connection to SQL Server. Theerror occurs on a SELECT statement. The user has read and writepermission to the database. I even tried giving the user Admin rightsjust as a test and it still generated the error. Is this a result ofthe cnmputer not being a member of the Workgroup? Thanks.Damon
View 4 Replies View RelatedHow to establish connection string for sql server on non-domain network?
View 2 Replies View RelatedHI All,
After i installed SQL Server 2005 workgroups edition to my Laptop, P4 and 1 Giga memory. I had a problem.
my problem is: when i start my laptop need 4 minutes to start the windows xp pro edition.
then I format my laptop and install the windows again, and every thing works fine, but I installed the SQL again and i had same problem with windows startup, there is nothing related to SQL in ;msconfig utilities.
do you have any tip about this problem ?
Thank You
Hello -- Please excuse my extreme newbieness -- trying to get up to speed fast on SQL Server Express for work. I've been able to set up the software, create a database, and access it with no problems on my local computer, but I need to make the database available to other computers in my workgroup. I followed instructions -- enabled TCP/IP and Named Pipes and turned on SQL Server Browser, and I was actually able to manipulate one system database (the "master" database) from another computer but not any other databases, not even the other system databases. I can connect to any of the databases with the SQLCMD commands, but if I try to do any SELECT commands (other than in "master") I get an error: "SELECT permission denied on object '[MyTable]', database '[MyDatabase]', schema 'dbo'". I was only able to get into "master" after adding "guest" as a user, but adding this user to the other databases has no effect. One interesting thing: When I used the sp_table_privileges command on each database, all but "master" showed all privileges being granted to and from "dbo", but "master" didn't show anything being granted to or from anybody. Does anyone know what could be going on here? Am I missing something obvious? Thanks for any and all help!
View 1 Replies View RelatedGood day,
We have developed an application using VS 2005 and SQL Server 2005 Developer Edition.
Currently, our client is asking if they could buy the SQL Server 2005 Workgroup Edition.
Is it ok? I'm afraid that the SP we made using CLR and any other functionality might not work.
We are suggesting our client to use the SQL Server 2005 Standard Edition instead. But for them to save money, can they use the Workgroup Edition instead?
I would really appreciate your help.
Thanks and more power,
Arthur
I am putting up a website this month, its pretty complex in terms of the data being stored. We expect to have 1000 users in our first month and grow exponentially from there. In addition, users will be uploading content to the site (mostly jepgs and PDFs).
We currently have a dedicated server and need to decide whether to go with Microsoft SQL Server Workgroup or Standard. Any advice on this?
If we went with workgroup, what is the threshold for the number of users before we would have to switch to standard? Also...are there any huge limitations that would make our site fail if we went with workgroup?
thanks,
sb
I am trying to install the SQL Sever 2005 Workgroup Edition software that came with our Small Business Server 2003 R2 system. I would like to install to the d: drive because space on the c: drive is limited. Can I do that? If so, how?
View 1 Replies View RelatedCan any one tell me what I should do with following error :
I'm working with sql server 2005 workgroup and I installed SP2.
When I make a maintenance plan voor backup the databases (full) then at the end I got the following error !
save maintenance plan failed
One or more arguments are invalid.
I red this problem already on forums but I didn't get it resolved.
When I use sql server 2005 developer It worked fine !
Geert
i have SQL Server 2005 Workgroup Edition
how to connect to it from vb.net 2005 because i try but no use
thanks in advance.
Hi
I've recently gone through installing and setting up merge replication on Server 2005 Standard. All working.
I am now setting up a different box with SQL 2005 Workgroup with SP2. When I go to the Replication tab in Management Studio there is only Local Subscriptions - No Local Publications.
I've re-run the installation but I can't see how Publications is not getting installed orwhy it is missing.
Any ideas much appreciated.
Thanks
Alistair
Hi All,
A client of mine was using SQL Express and soon realised this doesn't meet his needs performance or database size wise. He also realised that SQL Server 2005 Workgroup came free with his R2 version of SBS.
So in essence, I have been trying to find the Microsoft recommended way to upgrade from Express to Workgroup. I have not been able to find a step-by-step guide and to add to my confusion, when I run the work-group installer it tells me to run the installer with a switch which I have gone ahead and done but when selecting components it has all of them defaulted to blanked out.
Surely the process for an in-place upgrade should not be so technical as I am finding it ? To my mind, the natural progression would be to upgrade express to a better capable version of 2005 and should be as easy as pie.
Anyway, I am basically looking for a step-by-step guide on how to upgrade to get it done right the first time as opposed to upgrading and than realised some remenants of Express are still larking about causing trouble.
Regards,
QS
I have a root domain and child domain.
After using ADMT to migrate the domain user or group into the root domain, when I use enterprise manager to try and change the permissions allocated to that domain user/group, i get the 'Error 15401 NT user or Group not found'.
This is a correct error as the user is now in the root domain, however sql (in sysxlogins) still thinks its in the child domain.
Is there a simpler way, other than collecting the users permissions, deleting the user from SQL then adding back in with the correct domainusername format, then adding the permissions back?
I tried renaming the 'name' in sysxlogins (not recommended) and while that worked, whenever I tried to add the migrated user to another database, the login name was missing and would not resolve.
I believe it is something to do with the SID not matching.
Any ideas on how to fix this ?
we recently migrated from our in-house domain to the Enterprise domain. Everything went smooth except for the fact that I can no longer accept my dBs using my SA or my domain admin account. There is only 1 account I can get into the management studio with but it has no admin privileges, so I can't make any password changes or add accounts. I don't have a test environment so kind of hesitant to experiment with our production system.
View 6 Replies View RelatedDoes SQL Server 2005 Workgroup Edition have a limit to the number of user logins I can make?
View 1 Replies View RelatedI made an analysis services project but I can't deploy it because it can't find the server
I search for the analysis service in the Service Control Manager but I can't find it.
Is it possible to download and install it with this version of sql server (workgroup) ?
Hi,
I am new to SQL Server and I am trying to install SQL Server 2005 Express or Stnadard Edition on a computer runing XP pro on a XP's workgroup network using a router. Can I access the the database from another computer running XP pro on the same network? If I can, what setting do I need when installing SQL 2005 in order to do this?
Any help is appricated.
We have only a small busines and haven't got too much experience with servers and now have a proliant server coming in with SBS 2003 R2 Premium with the 4 GB max memory that SBS 2003 can handle according to the specs.
We weren't planning on using the SQL 2005 worlgroup edition up till now, but now we might. According to the specs of SQL server 2005 workgroup edition however, it has a max RAM of 3GB!
Is this going to be a problem and should we keep using our previous DB, or can we migrate toward SQL server with the 4 GB of RAM?
I have an SBS 2003 server that is running SQL 2000 standard edition which was recently upgraded to Small Business Server 2003 R2.
I have installed SQL 2005 workgroup edition on the SBS 2003 R2 server which acts both as an AD server and Exchange server. I installed SQL 2005 for the purpose of using SQL 2005 for my sharepoint services on the Small Business Server R2.
Now I have SQL 2000 and SQL 2005 workgroup edition installed, but I'm unsure whether I can uninstall the SQL 2000 and how to know whether the sharepoint instance is running in SQL 2005 or SQL 2000?
Additionally, I have some MSDE's running for WSUS and Server Reporting which are installed by the Small Business Server installation.
Which tools should I use to become familiar with identifying the databases and which version of the database engine is used for which database regardless of whether it is a SQL instance or a MSDE instance.
How can I identify which SQL versions are not in use and whether I can uninstall if not needed.
Thanks!!
In MSDE sql server 2000 dtsrun was available to execute the dts packages but now with sql server 2005 express edition integration service is not part of express/workgroup edition and the dtsexec run time is also not available.
View 6 Replies View RelatedI've heard that the Standard version supports the use of CommandNotification and that the Express version does not. What about the Workgroup edition?
The reason I'm asking is because there is a substantial monthly difference in cost between the two versions if I were to have my site hosted. I've been developing with MS SQL 2005 Express so obviously I have not tested this caching feature. Are command notifications reliable? On paper, it sounds impressive and extremely efficient especially if a site is to have heavy traffic and you can't afford the overhead of heavy database processing that is useless if the data is unchanged.
Does the Workgroup edition support automatic change notifications? Have automatic notifications been proven reliable and vastly more efficient than crude polling methods?
Thanks in advance.