Running SQL Server 2000... I've installed a new instance of this on a new
server (to migrate from server1 to server2).
On server1, i have a group set up (domain/SQLGroup)...
On server2, i have the exact same group set up... unfortunately all the
users in this group doesn't get recognized by my new sql installation. I
get the error above (SQL Error 18456, State '28000')..
I can change permissions for all the users in this group to have "Domain
Admins", but obviously i don't want to do that... by doing this though, all
access works as before...
SP4 is installed on server2, but not on server1...
Does anyone have any suggestions on how to proceed with this?
Re: Error 18456, State 28000 ...Server2 is just windows 2003, and is dedicated to sql server 2000... ... i have a group set up... ... users in this group doesn't get recognized by my new sql installation.... (microsoft.public.sqlserver.security)
Re: transaction log shipping wizard uses wrong computer name? ... I'm still hoping someone can point me to a solution here...It looks like the "jobserver" name is an alias to the machine name that SQL Agent is running on...I presume that the SQL agent picked this up when I first installed SQL2005 on the server before it was joined to the domain. ... I'm configuring log shipping on server1 and backingup/restoring to server2.... (microsoft.public.sqlserver.tools)
Security Question - Totally Stumped ...SERVER2 has joined to the SBS domain (verified by looking at the AD on ... When I log into SERVER2 using the Admin credentials of the domain ... To add to this SERVER2 also has SQL 2005 with Reporting Services. ... (microsoft.public.windows.server.sbs)
Re: Security Question - Totally Stumped ...SERVER2 has joined to the SBS domain (verified by looking at the AD on ... When I log into SERVER2 using the Admin credentials of the domain ... To add to this SERVER2 also has SQL 2005 with Reporting Services. ... (microsoft.public.windows.server.sbs)
New Server Cannot See Out ... We have a network setup in location 2 where we are doing development and also have a server in that location (everything at location 2 is behind the same firewall).... There is a new server in location 2 running Windows 2003 Server and SQL Server 2005. ... The problem is that Server2 cannot see Server1, ... Also, any of the Dev machines can see and connect to Server2 as well, but Server1 cannot. ... (microsoft.public.sqlserver.connect)
