Field Mapping

Build - Platform Target:  X86

IIS on a 64 bit system runs by default the 64 bit version of the framework and SQL Server express is a 32 bit application so that is what is causing your problem since it needs the 32 bit framework to operate correctly. There are 2 solutions: 1. Install SQL Server 2005 x64 developer edition instead of the express edition. This version however is not free so you will need to purchase a license witch luckily for us is not as expensive as a standard or enterprise license. Or: 2. Click start > run and type: (maybe need make start.bat, and right click to run as administrator) cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1 That will force your IIS to run in 32 bit emulated mode. then again at run or a command prompt type: %SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i To register the 32 bit framework with IIS. After that you should be able to install the larger version (x64) capable of SQL Server Express 2005 without...

By default, the following schema changes made at a Publisher running SQL Server are replicated to all SQL Server Subscribers: ALTER TABLE ALTER VIEW ALTER PROCEDURE ALTER FUNCTION ALTER TRIGGER If you do not want to replicate schema changes for a publication, disable the replication of schema changes in the Publication Properties - dialog box. For more information about accessing this dialog box, see How to: View and Modify Publication and Article Properties (SQL Server Management Studio) . To disable replication of schema changes On the Subscription Options page of the Publication Properties - dialog box, set the value of the Replicate schema changes property to False. Click OK. To propagate only specific schema changes, set the property to True before a schema change, and then set it to False after the change is made. Conversely, to propagate most schema changes, but not a given change, set the property to False before the schema change, and then set it to True after the change is ...

error message: THE MERGE PROCESS WAS UNABLE TO CREATE A NEW GENERATION AT THE “SUBSCRIBER”. TROUBLESHOOT BY RESTARTING THE SYNCHRONIZATION WITH VERBOSE HISTORY LOGGING AND SPECIFY AN OUT PUT FILE TO WHICH TO WRITE. I tried "update sysmergepublications set [generation_leveling_threshold] = 0" on both Subscriber and Publisher, still it didn't work. Then I tried "select count (*) from dbo.MSmerge_contents" and "select count (*) from dbo.MSmerge_genhistory" on the Subscriber The both query was running indefinely with no results, instanly I realised there is some Locking problem. In desperation I restarted the Subscriber Database Engine and started the Agent. Magic! Replication was successfull.

1. Download and install SelfSSL. By default, the application is installed to :\Program Files\IIS Resources\SelfSSL. Application and documentation shortcuts are copied to :\Documents and Settings\All Users\Start Menu\Programs\IIS Resources\SelfSSL. 2. Run SelfSSL: To run SelfSSL with default values for all parameters, locate the installation directory for the application, and then double-click SelfSSL.exe. or get your own server certificate if already installed. 3. Expand the Local Publications folder, right-click the publication, and then click Configure Web Synchronization. Create a new virtual directory. /websync

http://msdn2.microsoft.com/en-us/library/ms151319.aspx SQL Server 2005 Books Online Implementing Replication over the Internet Replicating data over the Internet allows remote, disconnected users to access data when they need it using a connection to the Internet. Replicate data over the Internet using: A Virtual Private Network (VPN). For more information, see Publishing Data over the Internet Using VPN . The Web synchronization option for merge replication. For more information, see Web Synchronization for Merge Replication . All types of Microsoft SQL Server replication can replicate data over a VPN, but you should consider Web synchronization if you are using merge replication.

Merge Replication windows application http://technet.microsoft.com/en-us/library/ms146869.aspx

1. to add alias with Sql server configuration 2. create subscription using alias instead of IP

http://msdn2.microsoft.com/en-us/library/ms151819.aspx SQL Server Express does not include SQL Server Agent, which is typically used to run replication agents. If you use a pull subscription (in which agents run at the Subscriber), you must synchronize the subscription using Windows Synchronization Manager or RMO. For more information, see the following topics: Windows Synchronization Manager RMO programming: How to: Synchronize a Pull Subscription (RMO Programming) Replication does not support the Run As Normal User (RANU) feature of SQL Server Express. For more information about this feature, see the SQL Server Express documentation.