2. ASPRunnerPro General questions
  3. [SOLVED]  ASPrunner Error.
This topic is locked
[SOLVED]

 ASPrunner Error.

 		10/30/2008 8:09:54 PM
ASPRunnerPro General questions
W
 Wanda author

All of a sudden we are getting this error. This project has been working fine for logins etc. The only thign we've been playing with is the edit/add properties. This is a straight forward login.
Technical information

Error number 3001

Error description Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another.

URL /aspr/login.asp

SQL query select from [dbo].[Accounts] where [Login_ID]='wanda' and [Password]='test'

Solution

*

I ran SQL queries using the above Login_ID and Password - no problems.
I ran our existing ASPmaker project with the same credentials - no problems.
The columns are defined as follows:
Login_ID: nvarchar(15) -> adVarWchar(15)

Password: nvarchar(10) -> adVarWchar(10)
We created a dummy project with a Login Page and it works just fine.
We've checked every page (i.e. in the gui) from start to finish and nothing has changed at all (other than formatting for add/edit).
Any ideas what is goofy with this project?
Sergey Kornilov admin 10/30/2008

Wanda,
post your application to Demo Account and send the URL to support@xlinesoft.com for investigation.
W
 		Wanda author 10/31/2008

Alas, we nuked it. We tried pretty much everything with no luck.
One thing we did notice however was the if we entered a valid user name and invalid password for that user, we got the "Invalid login...". The reverse was also true.
This leads us to believe that it was something that we did and suspect that the error was actually being caused in another page - not so much as the login page.
We disabled generating a Menu, and then all worked fine. We looked at the menu page, tried resetting it to no avail. As this was a test/dev type project weren't too concerned.
It was just disconcerting that this happened all of a sudden.
Anyway, on to more...
Thanks for the reply. If we run into something like this again, we'll post.