Jump to content

harrylt

New Members
  • Posts

    4
  • Joined

  • Last visited

    Never

Everything posted by harrylt

  1. Hi, We have finally fixed this issue on our server, we tried everything under the sun. The only way we could fix this was to disable the TCP/IP protocol in the sql server settings. We have an msde version on our development box so we could not choose named pipes as the default which i believe you can in the full version. Basically i think SP2 has to use named pipes for connection otherwise it will be very temperamental. You can set these options in the configuration utitlity that comes with sql server. Let me know if this works for the rest of you. Thanks Harry
  2. Hi, We have finally fixed this issue on our server, we tried everything under the sun. The only way we could fix this was to disable the TCP/IP protocol in the sql server settings. We have an msde version on our development box so we could not choose named pipes as the default which i believe you can in the full version. Basically i think SP2 has to use named pipes for connection otherwise it will be very temperamental. You can set these options in the configuration utitlity that comes with sql server. Let me know if this works for the rest of you. Thanks Harry
  3. are you using win 2003 service pack 2? if so then this problem is also affecting me and i can't find a fix anywhere! sp1 worked fine
  4. I have been looking for the answer to this question for weeks now and can't find anything. everything worked fine with win 2003 sp1 but as soon as sp2 was installed it cannot connect. it is fine if the scripts are on another machine or the db is on another but just not when they are both on this machine. very frustrating. someone must know the reason? Thanks
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.