I'm trying to set up transactional replication between two instances of SQL Server 2014. The publisher is a named instance running SQL Server 2014 Standard Edition. The subscriber is an instance of SQL Server 2014 Web Edition running in another data center.
Setting up the publishing side seemed to work okay; Replication Monitor lists the publisher and the publication is listed as OK. A snapshot has been generated; the snapshot agent's status is Completed and I can see files have been created.
Because the publisher's DNS name is different from its machine name and instance name, I created an alias on the subscriber side (as mentioned here). The machine/instance name is (fictionalized) SERVER01\MSSS2014, while the DNS name by which it is reachable is server01.something.com using a non-standard port (11433).
I've setup FTP synchronization on the publisher's side without specifying an alternate path, which has resulted in a new snapshot being created in (replication root)\ftp. The settings configured are verified to point to a directory containing a sub-directory named SERVER01$MSSS2014_TESTDATABASE_TEST (again, fictionalized).
When I try and create a subscription on the subscriber side, the wizard gives no errors. The only non-standard action is that on the step 'Distribution Agent Security', I select 'Run under the SQL Server Agent service account'. Next, next, next, and finally I get a screen saying that all went well:
On the publisher side I can see a subscription has been created, but its status is Uninitialized subscription. On the subscriber side, I can also see the subscription under Replication\Local Subscriptions. Its status, however, is Not available. Replication Monitor on the subscriber side stays empty. What's more, when I expand SQL Server Agent\Jobs, the only job there is syspolicy_purge_history. I believe enabling replication should create a slew of jobs there which do the actual replication. Since there are no jobs, I can't configure any logging.
SQL Server's log has no current events, neither does SQL Server Agent's log. The subscriber's nor the publisher's windows event logs contain any events related to SQL Server. How can I troubleshoot this issue?