locked
VB Application Error on SQL Server 2005. RRS feed

  • Question

  •  


    Hello

    I have a VB6 application in one system and SQL Server 2000 on other system.
    Application running fine and perfect

    but I moved Database from SQL Server2000 to SQL Server 2005(detatch/attach).

    Now problem is that after  reboot the Application server every first
    I am getting Error #-2147221504 (after every rebbot) for Application server.


    Please guide me any body faced the same problem.


    SNIVAS
    Tuesday, October 20, 2009 11:30 AM

Answers

  • The error that you are probably getting is "SQLSERVER doesn't exist or access denied.", which is likely caused by a connection string that is not valid for your SQL Server 2005 server.

    -- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
    Proactive Performance Solutions, Inc.
    "Performance is our middle name."

    Please! Remember to Vote all helpful replies as Helpful
    Thursday, October 22, 2009 3:02 AM
  • Check your Windows Application Event Log and see if there's any record about this connection problem and of course check your Connection String as RBarryYoung suggested.

    Also check your System Event Log.
    Ekrem Önsoy - MCDBA, MCITP:DBA & DBD, MCSD.Net, SQL Server MVP
    Thursday, October 22, 2009 8:56 AM
    Answerer

All replies

  • I think there's really a low possibility that someone would reply this question because probably there's noone around who experienced this problem and keep that unsigned number in his\her mind.

    Ekrem Önsoy - MCDBA, MCITP:DBA & DBD, MCSD.Net, SQL Server MVP
    Tuesday, October 20, 2009 1:20 PM
    Answerer
  • Thanks Ekrem Önsoy


    I Guess this Due connection like connection time out?

    but this was happing in Prod env only...can please provide me some information how similate connection time out.
    my making changes in system or NIC .



    SNIVAS
    Wednesday, October 21, 2009 7:01 AM
  • The error that you are probably getting is "SQLSERVER doesn't exist or access denied.", which is likely caused by a connection string that is not valid for your SQL Server 2005 server.

    -- RBarryYoung, (302)375-0451 blog: MovingSQL.com, Twitter: @RBarryYoung
    Proactive Performance Solutions, Inc.
    "Performance is our middle name."

    Please! Remember to Vote all helpful replies as Helpful
    Thursday, October 22, 2009 3:02 AM
  • Check your Windows Application Event Log and see if there's any record about this connection problem and of course check your Connection String as RBarryYoung suggested.

    Also check your System Event Log.
    Ekrem Önsoy - MCDBA, MCITP:DBA & DBD, MCSD.Net, SQL Server MVP
    Thursday, October 22, 2009 8:56 AM
    Answerer