February 16, 2010 at 3:57 am
in both machines (publisher and suscriber) i login with sa account with no problem, i have mixed mode in two machines. im using HAMACHI2 in the process al is correct, i search the publisher and find it, i make the suscription and no problem, but at the end the replication won't work, i just see the login error. but i check many times and its ok, localy its ok. some one can help me with this, i need to do the replication trough internet. thanks
===================================
Login failed for user 'sa'. (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476
------------------------------
Server Name: ALEXPC
Error Number: 18456
Severity: 14
State: 1
Line Number: 65536
------------------------------
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.SqlManagerUI.LogSourceJobHistory.InitializeInternal()
at Microsoft.SqlServer.Management.SqlManagerUI.LogSourceJobHistory.Microsoft.SqlServer.Management.SqlManagerUI.ILogSource.Initialize()
at Microsoft.SqlServer.Management.SqlManagerUI.LogSourceAggregation.Microsoft.SqlServer.Management.SqlManagerUI.ILogSource.Initialize()
at Microsoft.SqlServer.Management.SqlManagerUI.LogAggregator.DelegateAggregationWorkImplementation(ILogSource logSource)
February 16, 2010 at 5:45 am
Can you check the logs on the subscriber sever? this will have the error code and state that will help determine why the login failed.
February 16, 2010 at 6:59 pm
i look this error in the log:
Date16/02/2010 01:00:28 a.m.
LogSQL Server (Current - 16/02/2010 01:01:00 p.m.)
SourceLogon
Message
Error: 18456, Severity: 14, State: 38.
and this error too:
Date16/02/2010 01:00:28 a.m.
LogSQL Server (Current - 16/02/2010 01:01:00 p.m.)
SourceLogon
Message
Login failed for user 'NT AUTHORITY\Servicio de red'. Reason: Failed to open the explicitly specified database. [CLIENT: 5.35.137.29]
February 16, 2010 at 7:07 pm
why don't you use SQL service domain account for both servers. May be SA password on publisher and Subscriber is not same.
EnjoY!
February 16, 2010 at 7:48 pm
Domain account? you mean the MACHINE\User account? could be more especific please. and why i cant with sa account?
February 16, 2010 at 7:57 pm
Machine name and domain name are not the same, Are doing this in your local machine? under which service account your SQL Server is running?
February 16, 2010 at 8:09 pm
it's runing in the LocalSystem account, i think is the same that NT AUTHORITY\System. but it say its LocalSystem
February 16, 2010 at 8:12 pm
Are both servers running under local system account?
February 16, 2010 at 8:28 pm
ok here are the cofigurations:
Suscriptor:
SQL Server Reporting Services = LocalSystem
SQL Server Integration Services = LocalSystem
SQL Server Browser = NT AUTHORITY\LOCAL SERVICE
SQL Server Analysis Services = LocalSystem
SQL Server Agent = LocalSystem
SQL Server = LocalSystem
SQL Full-Text Filter Daemon Launcher = NT AUTHORITY\LOCAL SERVICE
Publisher:
SQL Server Reporting Services = NT AUTHORITY\NETWORKSERVICE
SQL Server Integration Services = NT AUTHORITY\NETWORKSERVICE
SQL Server Browser = NT AUTHORITY\LOCAL SERVICE
SQL Server Analysis Services = LocalSystem
SQL Server Agent = LocalSystem
SQL Server = LocalSystem
SQL Full-Text Filter Daemon Launcher = NT AUTHORITY\LOCAL SERVICE
February 16, 2010 at 8:45 pm
Are these servers in same domain?
EnjoY!
February 16, 2010 at 8:59 pm
well publisher is in an local network in an office, suscriber its on my home, i made the suscription via (VPN) the two servers are in the same NETWORK GROUP
February 16, 2010 at 9:11 pm
phanatico-1156717 (2/16/2010)
well publisher is in an local network in an office, suscriber its on my home, i made the suscription via (VPN) the two servers are in the same NETWORK GROUP
Even though you are in same network, SQL servers has to be in same domain to communicate b\w two. VPN means it just creates a tunnel to your office network, doesn't mean you can set up replication between these two servers, you had mis understood domain vs network both are two different things.
Hope this helps
EnjoY!
February 16, 2010 at 9:20 pm
AND HOW I PUT THEM IN THE SAME DOMAIN, ITS TO DIFICULT? YOU THINK THAT'S THE PROBLEM??
February 16, 2010 at 9:40 pm
Server team has to do that, i guess you won't have permission to that, they can add the servers to domain. Don't you have test environment in your office to do this kind of testing?
EnjoY!
February 16, 2010 at 9:52 pm
Run osql -L in command prompt on either publisher or subscriber machine and see the list of SQL server instances in that domain. You will be able to set up replication only between those listed SQL server instances.
Hope this helps
EnjoY!
Viewing 15 posts - 1 through 14 (of 14 total)
You must be logged in to reply to this topic. Login to reply