Aller au contenu

Photo

Unable to save module


35 réponses à ce sujet

#26
VenetianLunacy

VenetianLunacy
  • Members
  • 55 messages
Hi Allan - I have a suspicion that the problem may be caused by the Windows user profile name (particularly with 'special' characters in the name), rather than the language of the OS itself. For example, if my Windows Vista (US English Language) user name is E. Henry Thripshaw, the toolset fails to create a new module and generates the following errors in the log:



Tue Dec 15 19:52:54 2009, ERROR, "d:\\DASecuROMBuild\\main\\dev\\tools\\sdk\\include\\toolsoledb.h", 226, "String or binary data would be truncated."



Tue Dec 15 19:52:54 2009, ERROR, ".\\dbmodule.cpp", 338, "CDBModule::Add caught an exception: Bad HRESULT: 80040e57"



However, if I create a brand new Windows user name, for example, Allan Smith and attempt to create a new module under this new user, no issues or errors occur. I suspect that this problem may be the result of using characters that are not compliant with SQL, which would suggest why any non-English characters in a user name could also cause the problem.



It is important to note though, if the user name already has any offending characters in it, you cannot simply change the user name to resolve the issue. This is likely because while Windows changes the display name on request, it never changes the actual user name at the command shell.



The issue may be caused by other factors too, but hopefully this should allow you to reproduce the problem. For anyone looking for a workaround, try creating a brand new Windows user name, free of any non-standard characters, spaces seem to be okay.



Cheers.




#27
tarvs

tarvs
  • Members
  • 4 messages

VenetianLunacy wrote...

Hi Allan - I have a suspicion that the problem may be caused by the Windows user profile name (particularly with 'special' characters in the name), rather than the language of the OS itself. For example, if my Windows Vista (US English Language) user name is E. Henry Thripshaw, the toolset fails to create a new module and generates the following errors in the log:

Tue Dec 15 19:52:54 2009, ERROR, "d:\\\\DASecuROMBuild\\\\main\\\\dev\\\\tools\\\\sdk\\\\include\\\\toolsoledb.h", 226, "String or binary data would be truncated."

Tue Dec 15 19:52:54 2009, ERROR, ".\\\\dbmodule.cpp", 338, "CDBModule::Add caught an exception: Bad HRESULT: 80040e57"

However, if I create a brand new Windows user name, for example, Allan Smith and attempt to create a new module under this new user, no issues or errors occur. I suspect that this problem may be the result of using characters that are not compliant with SQL, which would suggest why any non-English characters in a user name could also cause the problem.

It is important to note though, if the user name already has any offending characters in it, you cannot simply change the user name to resolve the issue. This is likely because while Windows changes the display name on request, it never changes the actual user name at the command shell.

The issue may be caused by other factors too, but hopefully this should allow you to reproduce the problem. For anyone looking for a workaround, try creating a brand new Windows user name, free of any non-standard characters, spaces seem to be okay.

Cheers.


This worked for me.  My default user name had an underscore in it.  I created a new user with admin rights and I was able to create a new module.

#28
Fudzie

Fudzie
  • Members
  • 217 messages
That's odd, considering my username is straight up normal letters, with my language being English.



Apologies for not responding sooner, my computer was in the process of being replaced, and steam no longer works on my old one. When I get the toolkit installed and try again, I'll post my results should I experience the problem again (knowing my luck, it should happen again.)

#29
Lejontass

Lejontass
  • Members
  • 14 messages
It worked! Strange though, as I had only capital letters, normal letters and spaces in my user name. Still thanks for the tip, finally! After all this wait! ^^

#30
Allan Smith

Allan Smith
  • BioWare Employees
  • 83 messages
@VenetianLunacy
Thanks for the tip. We had seen other manifestations of the username giving us trouble with SQL, but I had not made the connection to this particular problem. Will post this information on the wiki (if it is not there already)
If this solution does not solve the problem for anybody, please speak up so we can chase down any other causes.

Modifié par Allan Smith, 16 décembre 2009 - 04:03 .


#31
mihlena

mihlena
  • Members
  • 141 messages
Great, it works! Thank you very much for this tip!

#32
Lejontass

Lejontass
  • Members
  • 14 messages
My problem was probably the length of my username, 17 letters in length.

Modifié par Lejontass, 16 décembre 2009 - 06:11 .


#33
jedigazelle

jedigazelle
  • Members
  • 1 messages
I have no speciall characters in my username unless space is conidered special...(special ed maybe)...however i am still receiving the unable to create module...is there no other way around it than to create another username? i really dont want to add yet another user to my computer just for one program

#34
nametab

nametab
  • Members
  • 70 messages
When I first downloaded and installed the toolset I encountered the lightmap problem, to which there was no good solution. It's been like 3 months now, I already have a new PC and I thought everything would go just fine from now on... and now I am "unable to save module". And there is no problem with my username - it is short and doesn't contain any unique characters. Is there any other way around this bug, or is it just destiny that I can't create DA modules?

#35
fedesensiz

fedesensiz
  • Members
  • 2 messages
My computer name had 20 letters, I change it in a shorter one and the toolset finally runs (no problems with other programs)! thnx!

#36
Chairon de Celeste

Chairon de Celeste
  • Members
  • 720 messages
Edit:

Some moronic programmer of 3rd party win content had
decided to change my windows computer name into
some random funky nugdropping.

After changing 'Marv-#31/ff7//79841' back into 'Marvin'
here, saving modules again works like a charm...

Modifié par Chairon de Celeste, 09 avril 2010 - 09:23 .