ACIS Defaulting to Named Pipes

Ascent Capture Internet Server

ACIS Defaulting to Named Pipes

Postby RobertMinneman » Thu Dec 14, 2006 10:28 am

For what are probably very interesting reasons, the ACIS servers when installed seem to be defaulting to using the named pipes protocol.

I'd like to change this to a TCP/IP sockets protocol to be more compliant with my company's network standards, and perhaps, get a bit better performance (I have some stations that are taking upwards of a minute to open a 3 page batch in the validation module).

How would I go about changing my ACIS servers over to TCP/IP sockets connections, and would I need to do anything at the workstations to accomodate this?
Posts: 86
Joined: Wed Nov 01, 2006 2:17 pm

Postby » Thu Dec 14, 2006 10:48 am

Hi Robert,

just run svrnetcn on the ACIS servers. Disable named pipes and save and close. Open ACConfig.xml and change the network protocol from DBNMPNTW to DBNETLIB. Save. Stop the ACIS Service. Resart the MSDE instance for AC. Start the ACIS Service.

Best regards,
Posts: 43
Joined: Wed Aug 10, 2005 3:36 am

Re: ACIS Defaulting to Named Pipes

Postby Johan1974 » Thu Feb 04, 2010 12:37 pm


Just being curious , could this still be working for a KC8 and KTM4 environment. In this case the KCNS server is in one country and the remote site is in another country. I have some trouble where with downloading the batchclasses. It just stops responding and the synchronisation hangs .
Posts: 244
Joined: Wed Sep 13, 2006 10:21 pm

Return to Network Server General Discussion

Who is online

Users browsing this forum: No registered users and 1 guest