MSSQL 2008 64 Bits Connection VB.Net project (VS 2005)

  • Hi.

    I'm having an issue with one new SQL 2008 64 Bits installation.

    an existing app using SQL 2008 32 Bits works fine.

    The setting for both servers/DB are the same the only difference is the version 32 & 64 Bits/

    The apps runs fine using the 32 bits server but when the connection string changes to the 64 Bits server produces the following error, which is not valid since the connection string works ok on 32 bits

    I tired the tow connection strings and works fine on ServerName32Bits when I switch to Servername64 Bits, I got the errors.

    "User ID=user;PWD=password;DATABASE=DBRept;Server=ServerName32Bits;CONNECTTIMEOUT=90;Provider=SQLOLEDB; "

    "Driver=SQLOLEDB;Data Source=ServerName32bits;Initial Catalog=DBRept;User id=user;Password=password;"

    I found some posts about configuration but didn't work either, I can access the DB using the SQL Analyzer with multiple user ID from the machine runing the VB app.

    I used the SA password for the connection strings

    Any Ideas..?

    System.Runtime.InteropServices.COMException was unhandled

    ErrorCode=-2147467259

    Message="Invalid connection string attribute"

    Source="Microsoft OLE DB Provider for SQL Server"

    StackTrace:

    at ADODB.ConnectionClass.Open(String ConnectionString, String UserID, String Password, Int32 Options)

    at TruePrinRept.ModReptDB.DBOpenDBLCN1(String strConnect) in C:\VisualStudio2005\TruePrinRept\TruePrinRept\ModReptDB.vb:line 38

    at TruePrinRept.ModReptDB.FN_Save_A_ReportControl_Table(String passSQL) in C:\VisualStudio2005\TruePrinRept\TruePrinRept\ModReptDB.vb:line 180

    at TruePrinRept.frmMain.SetCertificates() in C:\VisualStudio2005\TruePrinRept\TruePrinRept\frmMain.vb:line 71

    at TruePrinRept.frmMain.SetDatabaseCertificatesToolStripMenuItem_Click(Object sender, EventArgs e) in C:\VisualStudio2005\TruePrinRept\TruePrinRept\frmMain.vb:line 46

    at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

    at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

    at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

    at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

    at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

    at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)

    at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

    at System.Windows.Forms.Control.WndProc(Message& m)

    at System.Windows.Forms.ToolStrip.WndProc(Message& m)

    at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)

    at System.Windows.Forms.Control.ControlNativewindow.WndProc(Message& m)

    at System.Windows.Forms.Nativewindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

    at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

    at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)

    at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

    at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()

    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()

    at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)

    at TruePrinRept.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81

    at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)

    at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

    at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

    at System.Threading.ThreadHelper.ThreadStart()

Viewing 0 posts

You must be logged in to reply to this topic. Login to reply