Error while transfer SPCOD to Meghdoot postman,Error " Could not find server "eCounterLinkserver" in sys.servers'

Regarding error message "Could not find server 'eCounterLinkServer' in sys.servers....", please do the following and check:



a) Please check whether your office is an ePayment enabled office and eCounter database is present in the Server.

b) The article data for SP-COD is transferred from Speednet Server to Meghdoot Server based on the linked server concept and the prerequisites for creation of linked server are that the Meghdoot server should have the remote connections enabled.

c) To configure SQL Server 2005 to allow remote connections, you must complete the following steps:

i)   Enable remote connections on the instance of SQL Server that you want to connect to from a remote computer.
ii)  Turn on the SQL Server Browser service.
iii) Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.
iv)  To enable remote connections on the instance of SQL Server 2005 and to turn on the SQL Server Browser service, use the SQL Server 2005 Surface Area Configuration tool. The Surface Area Configuration tool is installed when you install SQL Server 2005.

You can view further information at http://support.microsoft.com/kb/914277.
The above example is provided for SQL Server Version 2005. Please follow the same for other Versions also.
You can google for similar information for other versions of SQL Server. For some versions, enabling of the Named Pipes and TCP/IP options under the Surface Area Configuration setting for SQL Server might be required to be done additionally.

d) Details for Meghdoot server are taken from the configuration done under 'Supervisor --> Master --> Environment --> Folder Paths' window. Hence, ensure that this information is correct.

e) Default settings need to be set for linked server to fetch data related to SP-COD articles. As such, please do the following:

In SQL version 2000:

a) Open 'Enterprise Manager' and select 'Linked Servers' option under Security.
b) Right-click on 'Linked Servers' option and select new linked server option (give some name as linked server name).
c) Select 'Other Data Sources' option under General tab.
d) Select provider name as 'Microsoft OLE DB Provider for SQL Server' and click on 'Provider options' button.
e) Set the 'Allow InProcess' property to true, click on OK and exit enterprise manager.

If the above settings are not working in SQL Server Version 2000, then the office concerned may need to upgrade to SQL Server Version 2005 or above.

In SQL Version 2005 or above:

a) Go to Providers option under Server Objects --> Linked Servers in the SQL Server Management Studio
b) Select the entry for 'SQLOLEDB' under Providers, right click and select 'Properties' option
c) Check / Select the entry for 'AllowIn Process' option for the SQLOLEDB properties

Save the above settings.


f) Once the above configurations are done, please do the following and check:

a) Download the attached zip file and unzip it.

b) Run POSPCC_COD_18032015.exl file using Meghdoot ScriptTool.exe after taking full backup of POSPCC database and check the script execution log file.


Attachment Sent: POSPCC_COD_18032015.zip