Anyone knows how to solve the compatilbility problem of the server?
sql server and toolset in Windows 8.1
Débuté par
Kallimachus
, oct. 21 2013 03:07
#1
Posté 21 octobre 2013 - 03:07
#2
Posté 23 octobre 2013 - 11:52
If it is the same warning you get with Windows 8.0 then there are is a thread kicking about (sorry I'm on my phone so I don't have the link but I found it with a quick Google search). The advice boiled down to selecting the "continue without online help" option both time it appears. There were also a couple of other issue I encountered which might of been due to Windows 8 and/or the fact I bought DAO on Steam: I had to create a BioWare subfolder for the uninstall file (again there is a three on this) and I had to give the account running the SQL Server service access to my backups folder so I could restore the database I copied across from my main computer (only relevant if you use backup/restore).
If this is a new Windows 8.1 specific issue then I'm afraid I haven't seen anything about it. If you describe it maybe someone can help.
If this is a new Windows 8.1 specific issue then I'm afraid I haven't seen anything about it. If you describe it maybe someone can help.
#3
Posté 23 octobre 2013 - 12:52
yea, just ignore warning and go on with install, it should work (in my case it does on x64 win8.1 pro), unfortunately i didn't go with thorough test, but importing modules work, i was also able to install needed python for lightmapper, it seems everything is ok (except if you transferred database from old machine and didn't give same comp/user name for new machine, then you could have problems if you try to continue work on some existing project(s) - you cannot check in / check out resources assigned to "older you").. but maybe someone have solution for that also..
#4
Posté 19 novembre 2013 - 08:16
just couple of notes (for win8.1 users)..
if you installed sql 2005, it is possible that when stopping sql service (some crash, or manually to backup database) something changes in system config, and toolset cannot connect to default database anymore.. you can try to go with configure toolset utility, but in my case i lost 2 hours on futile attempts.. i could connect without problems on remote server in vpn, but without luck on local database..
so what you can do?
- stop default sql service and back-up your database(s) - bw_dragonage_content.mdf/ldf file - put on some secure place / folder /.....
- uninstall sql2005 and choose yes to uninstall default instance (BWDATOOLSET)
- install sql2012 express (i used 32bit version with advanced services - it have sql management studio, i guess it should work same with 64bit version, but toolset is 32bit so i tried with 32bit version)...
- when installing, name your sql2012 instance again as BWDATOOLSET..
- for security i choosed mixed mode, put myself as database admin, but also configured password for sql server admin ("sa")..
- copy your backed up database into data folder of sql2012 (for 32-bit sql it is under C:\\Program Files (x86)\\Microsoft SQL Server\\MSSQL11.BWDATOOLSET\\MSSQL\\DATA)..
- open sql server management studio and right click on databases - choose "attach"..
- on file open dialog choose your database from sql server data folder (again in my case C:\\Program Files (x86)\\Microsoft SQL Server\\MSSQL11.BWDATOOLSET\\MSSQL\\DATA)
- and it should work..
but this kills toolset capability to connect to remote database (if any need), i guess it does have something with sql2012 and sql native client.. well, somewhere you get, somewhere you lose..
EDIT: you can connect to remote server.. when configuring connection with configuretoolset utility, you have to choose sql native client and choose to "allow to save password" checkbox..
if you installed sql 2005, it is possible that when stopping sql service (some crash, or manually to backup database) something changes in system config, and toolset cannot connect to default database anymore.. you can try to go with configure toolset utility, but in my case i lost 2 hours on futile attempts.. i could connect without problems on remote server in vpn, but without luck on local database..
so what you can do?
- stop default sql service and back-up your database(s) - bw_dragonage_content.mdf/ldf file - put on some secure place / folder /.....
- uninstall sql2005 and choose yes to uninstall default instance (BWDATOOLSET)
- install sql2012 express (i used 32bit version with advanced services - it have sql management studio, i guess it should work same with 64bit version, but toolset is 32bit so i tried with 32bit version)...
- when installing, name your sql2012 instance again as BWDATOOLSET..
- for security i choosed mixed mode, put myself as database admin, but also configured password for sql server admin ("sa")..
- copy your backed up database into data folder of sql2012 (for 32-bit sql it is under C:\\Program Files (x86)\\Microsoft SQL Server\\MSSQL11.BWDATOOLSET\\MSSQL\\DATA)..
- open sql server management studio and right click on databases - choose "attach"..
- on file open dialog choose your database from sql server data folder (again in my case C:\\Program Files (x86)\\Microsoft SQL Server\\MSSQL11.BWDATOOLSET\\MSSQL\\DATA)
- and it should work..
but this kills toolset capability to connect to remote database (if any need), i guess it does have something with sql2012 and sql native client.. well, somewhere you get, somewhere you lose..
EDIT: you can connect to remote server.. when configuring connection with configuretoolset utility, you have to choose sql native client and choose to "allow to save password" checkbox..
Modifié par dr.drummie, 19 novembre 2013 - 07:52 .





Retour en haut






