Author |
Topic  |
|
TestMagic
Senior Member
   
USA
1568 Posts |
Posted - 20 August 2002 : 12:21:25
|
Hello! I've got my 3.4 forum installed and running well on an Access 2000 db.
Yesterday, I turned on email authentication (I'd received some registrations last week from people using my domain name in their email addresses).
Today, I noticed I hadn't received any new members since turning on the email authentication, so I did a test registration myself. I did not receive the confirmation message. So I logged out, and relogged in under a test name I created in the past and sent myself a test message just to make sure that my email component (ASPmail) was set up correctly. I received the email almost instantly, no problem.
I then did a search of these forums to see if there was any information on problems with email authentication, but I did not find any.
So then I decided to allow the 8 pending members to join. I went to Admin Options and clicked on "Activate Account" and received this message:
Microsoft JET Database Engine error '80004005'
Field 'FORUM_MEMBERS.M_USERNAME' cannot be a zero-length string.
/forum/register.asp, line 185
I'm guessing that since the members haven't confirmed their emails, that the proper data hasn't been written to the db, but I just wanted to post here to let you know.
As always, thanks in advance for all your wonderful help! |
Snitz rocks! · Search 2 |
|
Roland
Advanced Member
    
Netherlands
9335 Posts |
Posted - 20 August 2002 : 12:25:48
|
I've had that happening to me twice now and the reason is that during setup, for some reason several fields in the table FORUM_MEMBERS are set to not allow zero length entries. You'll have to download your database, make the appropriate changes in Microsoft Access and upload the database again. All those problems will be gone then.
There are more than one fields that are "reset" (if you wish to call it that) so make sure you try them all, except the number fields.
|
 |
|
TestMagic
Senior Member
   
USA
1568 Posts |
Posted - 20 August 2002 : 12:33:02
|
Okay, Roland, I'll try that.
Thanks a million! As many have said already, and will certainly say again, you are a true asset to the Snitz community! |
Snitz rocks! · Search 2 |
 |
|
Roland
Advanced Member
    
Netherlands
9335 Posts |
Posted - 20 August 2002 : 12:35:59
|
You're very welcome 
Erin, also change the field country to allow 60 or 70 characters. I believe 50 is not enough for the countries with a longer name. This was reported as a bug for 3.3.x but might've slipped through. |
 |
|
Roland
Advanced Member
    
Netherlands
9335 Posts |
Posted - 20 August 2002 : 14:02:19
|
Watch out! My advise is correct and does fix the problem. However, you can also apply this fix for register.asp and your problem should be solved too.
I was not aware that that fix was for this problem at the time I posted my other replies. My apologies for this. |
 |
|
TestMagic
Senior Member
   
USA
1568 Posts |
Posted - 20 August 2002 : 15:00:46
|
No sweat, Roland. I haven't had a chance to fix it yet anyway. 
Thanks for your vigilance! |
Snitz rocks! · Search 2 |
 |
|
TestMagic
Senior Member
   
USA
1568 Posts |
Posted - 20 August 2002 : 18:30:35
|
Okay, I applied the fix listed here:
http://forum.snitz.com/forum/link.asp?TOPIC_ID=33006
And have received this error message:
Microsoft VBScript runtime error '800a005e'
Invalid use of Null: 'Replace'
/forum/inc_func_common.asp, line 322
I will open the db manually and look to see if I need to make the change you mentioned above:
quote: for some reason several fields in the table FORUM_MEMBERS are set to not allow zero length entries. You'll have to download your database, make the appropriate changes in Microsoft Access and upload the database again.
There are more than one fields that are "reset" (if you wish to call it that) so make sure you try them all, except the number fields.
Of course, I will post back with results!  |
Snitz rocks! · Search 2 |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 20 August 2002 : 18:47:36
|
Erin, your current problem has also been fixed:
http://forum.snitz.com/forum/topic.asp?TOPIC_ID=32988
Also I've already told Roland that the fields set to not allow zero length at my Snitz 3.4 DB are the same, as far as I've been able to find, that did not allow zero length in Snitz 3.3.x. If you have a backup, compare them.
The difference, IMO, is the code that fills in the tables, and that fix I posted fixes the problems I've found so far. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
Edited by - ruirib on 20 August 2002 18:52:21 |
 |
|
TestMagic
Senior Member
   
USA
1568 Posts |
Posted - 20 August 2002 : 19:14:44
|
quote: Originally posted by ruirib
Erin, your current problem has also been fixed:
http://forum.snitz.com/forum/topic.asp?TOPIC_ID=32988
Yes, Rui, that did the trick!
I might go back and compare the two databases just for the heck of it, though, even though everything seems to be working okay now.
Obrigado por tudo, como sempre! |
Snitz rocks! · Search 2 |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
|
Roland
Advanced Member
    
Netherlands
9335 Posts |
Posted - 21 August 2002 : 11:32:59
|
The fields might be set to not allow zero length entries by default. That doesn't mean that setting them to allow zero length to get rid of this bug is wrong  |
 |
|
ruirib
Snitz Forums Admin
    
Portugal
26364 Posts |
Posted - 21 August 2002 : 11:35:38
|
quote: Originally posted by FrutZle
The fields might be set to not allow zero length entries by default. That doesn't mean that setting them to allow zero length to get rid of this bug is wrong 
Of course. What I meant to say is that this is not a 3.4 issue, with the possible exception of the situation I posted a bug fix for. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
 |
|
|
Topic  |
|