SQL Server Merge - Pull replication error - sql

I have a configuration problem to create a Merge/Pull replication between two databases SQLServer 2012.
The machine Publisher is a Windows Server 2008 R2 not in windows domain, this Server is also the Distributor.
The machine Subscriber is a Windows 8 not in windows domain.
I have made the following settings: in the Published Server i created the distributor's folder, "repldata" and I also shared it and suser "everyone full control".
The path's folder is \servername\repldata
see image: www.alessandrosenesi.com/download/distributor.jpg
I created Publisher, see image: www.alessandrosenesi.com/download/Publisher.jpg
I created Subscriber see image: www.alessandrosenesi.com/download/subscriber.jpg
I have done some settings in Distributor, Publisher and Subscriber but I don't get results, I always have access error.
see image: www.alessandrosenesi.com/download/log.jpg
Error messages:
The schema script 'BOOKING_2.sch' could not be propagated to the subscriber. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147201001)
The process could not read file '\\nomemacchina\repldata\unc\nomemacchina$MSSQLSER VER2012_nomereplica\20130930125944\BOOKING_2.sch' due to OS error 5. (Source: MSSQL_REPL, Error number: MSSQL_REPL0)
Access Denied.
(Source: MSSQL_REPL, Error number: MSSQL_REPL5)
Can you tell me where is the problem? I have to do this replication but it looks like to be not possible
Thanks in advance
Alessandro

Replication across two non-trusted domains or workgroups can be done by using Windows Authentication by configuring pass-through authentication.
Create a local Windows account on both the Publisher and Subscriber that has the same username and password. Use this account for the Merge Agent process account and have the connections to the publisher and distributor impersonate the agent process account. Ensure the account has the permissions required in Replication Agent Security Model.
This approach is covered in the section Use Windows Authentication to Set Up Replication Between Two Computers Running SQL Server in Non-Trusted Domains in HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted Domains or Across the Internet.
If you have anymore questions please let me know. I hope this helps.

This permission issue.need check account full rights on file.

Related

BizTalk configuration troubleshooting

I am trying to configure BTS 2016 3.12.774.0 against SQL Server v 17.9.1. They are running on separate servers running Windows server 2016 64 bit OS.
The Enterprise Single Sign On database (SSODB) and the Business Rules Engine DB (BizTalkRuleEngineDB) get created but only to BRE is configured when I go into Biztalk Config.
I have had the servers rebooted but no change.
The Ent SSO Service does not exist in Services
User doing the install is in groups Biztalk Server Admin, Application Users, Server Operators and SSO Admin, Affiliate Admin all at the domain level.
Names of both servers are 13 characters.
Not sure what to look for in the configuration logs. I have searched for the words Error, Fail, Exception but there are none.
A new attempt to configure gave the following error:
Microsoft BizTalk Server Configuration Wizard ------------------------------ Failed to create the SQL database 'SSODB' on SQL Server 'servername10' (with SSO Administrator account 'SSO Administrators'). (SSO) For help, click: go.microsoft.com/fwlink/… ------------------------------ ADDITIONAL INFORMATION: (0xC0002A21) An error occurred while attempting to access the SSO database. (SSO) For help, click: go.microsoft.com/fwlink/… ------------------------------ An error occurred while attempting to access the SSO database. See the event log (on computer 'servername10') for more details. (SSO)
There is no SQL Server v 17.9.1. That version number is one for SSMS.
BizTalk Server 2016 does not support SQL Server 2017. Hardware and Software Requirements for BizTalk Server 2016
Please post the error text, either from the little red X or the error log. There will always be an error. BT Config will never silently fail.

TFS Configuration Error

I am facing a problem that when i try to configure my TFS it show me the following Error Message
Error
TF255049: A connection cannot be made to the server that is running SQL Server. Verify that you have entered the correct name for the server, including the instance name, that the server you are attempting to connect to is online, and that you have the required permissions to connect. If you are attempting to connect to the remote SQL Server instance, then verify that it is configured to allow remote connections, that TCP/IP protocol is both enabled and configured to use port 1433 (default), and that Windows Firewall does not block this port.
Check whether the SQL version is supported by the TFS version: https://www.visualstudio.com/en-us/docs/setup-admin/requirements#sql-server
Check the permission of the account that you use, and make sure it belongs to SysAdmin Server Role.
As #Daniel mentioned in comment, follow the troubleshooting steps provided in the error message, and check this blog to see whether it is helpful: https://elhajj.wordpress.com/2013/02/25/workaround-error-tf255049-punching-a-hole-through-windows-firewall/
I was running an upgrade from TFS 2018 to Azure DevOps 2020.
After the server restart, the Azure DevOps Server Configuration wizard opened.
I was logged in as the local machine administrator and got this error (TF255049: A connection cannot be made to the server that is running SQL Server...) when trying to connect to my SQL Server machine (to chose the configuration database).
I logged in as Network Administrator, started the wizard again and the SQL connection worked.
To restart the Azure DevOps Configuration Wizard again...
Open the Azure DevOps Administration Console and choose Configure Installed Features to open the Server Configuration Wizard...

replication over internet- sql server 2012

I'm having trouble configuring merge replication over untrusted domains.
I have a remote serverA which has a real IP and I configured this server to be his own distributor and publisher and also a ftp-server for the snapshot folder to be shared. I created a windows login which has the sysadmin permission and has users having the db_owner role on both the replicated Database and distribution database and the merge PAL role and the sql-server agent is log on as this windows login and also this login is the job owner for all the jobs that is on the distribution.
And my local serverB is the subscriber server doesn't have a static IP. I configured this server to be the subscriber and to get the snapshot folder from ftp server.
At the distributor, the jobs are running with success, but at the subscriber the job always failing.
When i view the job history, it says job failed. When i view synchronization status it says the process can't connect to the distributor.
When i launched the replication monitor, I found two messages:
Schema script couldn't be propagated to the subscriber
The process couldn't connect to ftpsite using port 2015.
Could someone please help me with this?

SSIS & Business Objects SDK Error: File Repository Server Input is Down

Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.

Database Replication MSSQL 2000 to 2005

I am trying to replicate a database from SQL server 2000 to 2005 they are located on two different servers both running Windows Server 2003 R2. Im am using SERVER1(SQL2000) as the Transactional publisher and distributor and SERVER2(SQL2005) is the subscriber. I can set up the publication and subscription but when I try to syncronize them I get the following error:
SERVER1-TestReplication-TestReplication-IBSCNVII-ReplicationCNVII_2-99956FE2-402A-48D5-B801-2CBADF12BD3E has server access (reason: Could not obtain information about Windows NT group/user '', error code 0x5. [SQLSTATE 42000] (Error 15404)).
Do I need to add my domain user to a certain user group on server? Any ideas?
0x5 means "access denied" and that you're not allowed to query active directory user information. Likely, the sql server service account does not have proper domain privileges to perform look ups in AD. This could be caused by an account password simply being expired and therefore not enabling SQL to validate against AD or some other issue like services running as local system and not a domain account.
I would recommend confirming that both SQL servers are using a valid domain account and not something like local system. Then check that that domain account isn't locked up or expired.
make sure that the service account you are using to execute the replication has the appropriate rights to both your SQL servers
Aye, check your SqlAgent account in services.msc. Make sure it is a user with rights (in the domain and in SQL). If that fixes it, make sure you lookup the minimum rights required before you go into production.