MS SQL Server 2008

alsan · Post by **alsan** » Wed Aug 17, 2011 3:43 pm

Hi people

I have a question?

I need to do this:

Aplicacion---->Intermediario---->BD

A Windows application that connects to a database through an intermediary, as I do?

vitamin · Post by **vitamin** » Wed Aug 17, 2011 7:07 pm

alsan wrote:Aplicacion---->Intermediario---->BD

What Wine got to do with it?

alsan · Post by **alsan** » Thu Aug 18, 2011 9:42 am

I need to connect an application made in C # connecting to an MS SQL Server database ... but it claims that need to install the MDAC ... and I have it installed but still gives this error ...

I managed to try to connect from the linux console to connect to the database ... but not in the application ...

JennyT · Post by **JennyT** » Thu Aug 18, 2011 12:44 pm

It would be helpful if you could give a little more information

alsan · Post by **alsan** » Thu Aug 18, 2011 1:34 pm

Ok ... see I have an application made in C # with Visual Studio ... and I have specifically Ubuntu linux computer, which I have to run the application in Wine, which works, but as has database connection to another computer where you have the MS SQL Server 2008, the application does not run perfectly. I get an error that tells me I need to install the MDAC, and of course I did, but the error still there.

Now, I use the FreeTDS vine testing purposes with the connection to the database, and thus fails to connect to the linux console.

lahmbi5678 · Post by **lahmbi5678** » Thu Aug 18, 2011 5:59 pm

First of all, can you connect to the MS SQL Server via tsql (comes with FreeTDS, see also osql)? If that doesn't work, you have some config problem. PLease read the troubleshooting section in the freetds user guide.

Which wine version?
Which winetricks did you use, especially which dotnet versions?
Are you using Windows Mono or .NET?
What is the exact error message regarding failed connection?

If you have got the source code of the application, you might even try to recompile it with the linux version of Mono.

alsan · Post by **alsan** » Fri Aug 19, 2011 9:42 am

Hi thanks for your time ... to lodge a defense your questions ...

lahmbi5678 wrote:First of all, can you connect to the MS SQL Server via tsql (comes with FreeTDS, see also osql)? If that doesn't work, you have some config problem. PLease read the troubleshooting section in the freetds user guide.

Yes, through console ubuntu if I can connect with tsql command

lahmbi5678 wrote: Which wine version?

Wine 1.2.3

lahmbi5678 wrote: Which winetricks did you use, especially which dotnet versions?

dotnet20
others are mcdac and jet40 but not installed because I get an error about not finding the dao360.dll

lahmbi5678 wrote: Are you using Windows Mono or .NET?

Windows

lahmbi5678 wrote: What is the exact error message regarding failed connection?

When I run the application I get the errors that requires MDAC

lahmbi5678 wrote: If you have got the source code of the application, you might even try to recompile it with the linux version of Mono.

good idea

lahmbi5678 · Post by **lahmbi5678** » Fri Aug 19, 2011 11:37 am

You don't have to defend yourself, wine is still a kind of challenge, it is far from being perfect, it can be very complicated and frustrating, and the more information you give, the better.

You should install wine 1.3.26, 1.2.3 is stable, but really old. You should start in a new WINEPREFIX and install the needed winetricks and your application again, the simplest way is to move/rename your old .wine folder, a new .wine folder will automatically be created by wine.

There was another thread with jet40 troubles:
http://forum.winehq.org/viewtopic.php?t ... ght=dao360
Though that might be not really helpful.

winetricks mdac and jet40 should work, if they still fail with an up2date wine, you might report a bug at
http://code.google.com/p/winetricks/issues/list

Are you using Windows Mono or .NET?
Windows

That question was maybe a bit misleading, I wanted to know, if you used winetricks mono to install the Windows version of Mono (.NET substitute).

jjmckenzie · Post by **jjmckenzie** » Fri Aug 19, 2011 11:47 am

On Fri, Aug 19, 2011 at 9:37 AM, lahmbi5678 <[email protected]> wrote:

You don't have to defend yourself, wine is still a kind of challenge, it is far from being perfect, it can be very complicated and
frustrating, and the more information you give, the better.

You should install wine 1.3.26, 1.2.3 is stable, but really old. You should start in a new WINEPREFIX and install the needed
winetricks and your application again, the simplest way is to move/rename your old .wine folder, a new .wine folder will
automatically be created by wine.

If alsan wants to keep the old Wine prefix for some reason:

Code: Select all

cd $HOME
mv .wine{,.backup}

There was another thread with jet40 troubles:
http://forum.winehq.org/viewtopic.php?t ... ght=dao360
Though that might be not really helpful.

winetricks mdac and jet40 should work, if they still fail with an up2date wine, you might report a bug at
http://code.google.com/p/winetricks/issues/list

Are you using Windows Mono or .NET?

Windows
That question was maybe a bit misleading, I wanted to know, if you used winetricks mono to install the Windows version of
Mono (.NET substitute).

There are issues with using Mono vice using .NET, especially with SQL
connections. I would recommend the following:

Create a new Wine Prefix
Install .NET 2.0 using winetricks
Install .NET 3.0 using winetricks
Install mdac2.8 and jet4.0 using winetricks
Install program...

alsan may also need to install the ability to configure DSN
connections. That is discussed in another forum thread.

James