1 réponse à ce sujet

[Divino Zarathos]

Ok so, I've correctly installed the Toolset and the database. Toolset can connect to the database and edit savegames so all seems to work fine BUT the resources explorer.
Palette window (the panel on the right that should contain items, merchants, areas, ect...) is totally empty, blank, unfilled. I can't understand why... with SQL Sever Management Studiio I can connect and all the tables seem to be in the right place.

I've also tried to use the restore batch file and the process seems to be successfull achieved without errors but without fixing the problem. It correctly indexed down something like 10500 entries.

The only thing I noticed, in Toolset log file, is that there is an error that doesn't stop to be spammed and it could be related to my problem:

• Fri Nov 27 05:42:01 2009, ERROR, "d:\\DASecuROMBuild\\main\\dev\\tools\\sdk\\include\\toolsoledb.h", 226, "The conversion of a CHAR data type to a DATETIME data type resulted in an out-of-range DATETIME value."
  
  
• Fri Nov 27 05:42:01 2009, ERROR, ".\\dbresref.cpp", 881, "CDBResRef::GetResourceListByType caught an exception: Bad HRESULT: 80040e07"

I'm using SQL Server Express 2005 SP3 running on Windows XP Professional SP3 (fully patched).
It has TCP/IP, shared memory and named pipes enabled; it's settet up to run in Local System (I cannot switch it to Network Service).

The Toolset is configurated in the following way:
Provider=SQLOLEDB.1;
Integrated Security=SSPI;
Persist Security Info=False;
User ID=clientID;
Initial Catalog=bw_dragonage_content;
Data Source=.\\SQLEXPRESS



Can someone help me, please?

Modifié par Divino Zarathos, 27 novembre 2009 - 01:33 .

[BryanDerksen]

I recall that we had a problem with incompatible date formats with a German beta tester, I'm told he managed to work around the problem by changing some locale settings in his OS from the control panel. Unfortunately neither I nor my officemate recall exactly what he did, and a quick search of our email doesn't reveal any details of the solution - though it confirms that "BAD HRESULT: 80040e07" is indeed a symptom of this problem.



Unfortunately MSSQL isn't our program, so when it gets into territory like this we are often reduced to just searching Microsoft's knowledge base and hoping to stumble upon an answer. I'll ask around again tomorrow morning when more people are back in the office and see if anyone has already dug it up.