Difference between revisions of "Bug: Unable to save a new module"
m (Translate page on Russian) |
m (Expanding and description and workaround based on recent thread) |
||
Line 3: | Line 3: | ||
== Description == | == Description == | ||
− | |||
− | + | <!-- Describe the bug here including as many details as possible. What situations trigger it and what effects it causes are the most important. --> | |
+ | The Toolset user is unable to create a new module and encounter the following messages in their logs: | ||
− | <code>String or binary data would be truncated.</code> | + | * <code>String or binary data would be truncated.</code> |
+ | * <code>CDBModule::Add caught an exception: Bad HRESULT: 80040e57</code> | ||
− | + | Users that have encountered this bug be reproduce it using the following steps: | |
− | + | #Start the Dragon Age Toolset | |
+ | #Select '''File''' > '''Manage Modules''' from the menu bar | ||
+ | #Click the '''New...''' button | ||
+ | #Set the '''Name''' property, for example, to "Test" | ||
+ | #Set the '''UID''' property, for example, to "test" | ||
+ | #Click the '''OK''' button | ||
− | + | == Status == | |
+ | |||
+ | This problem is still being investigated. So far the issue seems to be related to the Windows user profile name, particularly long names or ones with 'special' characters in them. | ||
+ | |||
+ | As of February 2010 BioWare were still trying to determine the longest name possible, and what special characters are problematic, as well as if there is a way to deal with this programmatically. | ||
== Workarounds == | == Workarounds == | ||
+ | |||
<!-- if you know of any ways to work around the bug describe them here. --> | <!-- if you know of any ways to work around the bug describe them here. --> | ||
− | + | The issue has been discussed in the following threads: | |
+ | |||
+ | * [http://social.bioware.com/forum/1/topic/8/index/184494 Unable to save module] | ||
+ | * [http://social.bioware.com/forum/1/topic/8/index/9101779 Unable to save module/duplicate resource] | ||
+ | |||
+ | It appears that this issue is caused by '''CreatedBy''' and '''LastModifiedBy''' fields that exists in various tables, including '''t_Module''' and '''t_ModuleResRef''', to populate the resource history. The data type for both of these fields is a [http://msdn.microsoft.com/en-us/library/ms176089.aspx <code>varchar(32)</code>] which means it can contain a maximum of 32 non-unicode characters. The data stored in these fields is the user's <code><server-name>\<user-name></code>. For most people the <code><server-name></code> will be the name of their computer. | ||
+ | |||
+ | For some users this issue has been resolved by creating a new user account that is shorter or has no "special" characters in it. | ||
+ | |||
+ | It may be possible that this issue can also be resolved by changing the database authentication to '''SQL Server and Windows Authentication mode''', also known as "mixed mode"; creating a SQL Server Authentication login; and configuring the Toolset using the '''ConfigureToolset.exe'''. | ||
{{languages}} | {{languages}} | ||
[[Category:Toolset bugs]] | [[Category:Toolset bugs]] | ||
[[Category:Modules]] | [[Category:Modules]] |
Revision as of 22:05, 14 February 2012
- Version found: 1.0.1008.0
- Status: Open
Description
The Toolset user is unable to create a new module and encounter the following messages in their logs:
-
String or binary data would be truncated.
-
CDBModule::Add caught an exception: Bad HRESULT: 80040e57
Users that have encountered this bug be reproduce it using the following steps:
- Start the Dragon Age Toolset
- Select File > Manage Modules from the menu bar
- Click the New... button
- Set the Name property, for example, to "Test"
- Set the UID property, for example, to "test"
- Click the OK button
Status
This problem is still being investigated. So far the issue seems to be related to the Windows user profile name, particularly long names or ones with 'special' characters in them.
As of February 2010 BioWare were still trying to determine the longest name possible, and what special characters are problematic, as well as if there is a way to deal with this programmatically.
Workarounds
The issue has been discussed in the following threads:
It appears that this issue is caused by CreatedBy and LastModifiedBy fields that exists in various tables, including t_Module and t_ModuleResRef, to populate the resource history. The data type for both of these fields is a varchar(32)
which means it can contain a maximum of 32 non-unicode characters. The data stored in these fields is the user's <server-name>\<user-name>
. For most people the <server-name>
will be the name of their computer.
For some users this issue has been resolved by creating a new user account that is shorter or has no "special" characters in it.
It may be possible that this issue can also be resolved by changing the database authentication to SQL Server and Windows Authentication mode, also known as "mixed mode"; creating a SQL Server Authentication login; and configuring the Toolset using the ConfigureToolset.exe.
Language: | English • русский |
---|