This topic is locked

Error Occurred - Record was not Edited

10/29/2008 12:02:25 PM
ASPRunnerPro General questions
S
sleighbor author

Hi everyone,
I have created my first app with Asprunner. It is working great to list data but when trying to save an inline edit change I received an error. It seems to me that the error is a permissions error saving to the database. What account(s) need what permissions to make editing possible?
Thank you,

Kevin

Sergey Kornilov admin 10/29/2008

What's the exact error message?
Just in case check this:

http://www.xlinesoft.com/asprunnerpro/docs...ery__errors.htm

S
sleighbor author 10/29/2008

Hi Sergey,
The error I am seeing is an ASPRunner error and is in the web page when trying to save. it says:
Error Occurred - Record was not EDITED. [Microsoft][ODBC SQL Server Driver][SQL Server]The OLE DB provider "SQLNCLI" for linked server "ServerA" does not contain the table "dxdata"."dbo.nt1restore"". The table either does not exist or the current user does not have permissions on that table.
thanks,

Kevin

S
sleighbor author 10/29/2008

Does anyone know what I need to do to fix this?
Thank you,

Kevin

Sergey Kornilov admin 10/29/2008

I believe you trying to edit table that resides on another SQL Server. This could be database permissions issue.
If this is the case I recommend to connect to the linked server directly in ASPRunnerPro.

S
sleighbor author 10/29/2008

How do I do that please?
Thanks,

Kevin

M
myPCdoctor 10/29/2008

Hi Kevin, I agree with admin. It would be a security issue on (assuming) MS SQL, but I believe that DXDATA is a MySQL system Table so I'm not quite sure.
So, depending on the MS SQL version you have the steps to set permissions is different. For example SQL 2K is far different from SQL2K5 or SQL2K8.
However, the general steps would be as follows:

  1. Locate the table in question,
  2. Right Click on the table and select Permissions. With SQL2K5 and SQL2K8, select Properties, then Permissions. Don't mess with Extended Permissions here.
    Also, make sure that the account you are using has the appropriate permissions on the table. Thess have to "Explicitly" set, unlike SQL2K!
    In SQL2K it's pretty easy, follow the permissions dialogs and you'll get there.
    With SQL2K5 and SQL2K8, you need to specifically select each table and GRANT permissions for Select, Update, Insert, Delete etc.
    Hope it helps. If not, send me an email and I'll email a few pages from my SQL Instructor manuals that should help. But I would suggest following the general steps above first, it's both good practice and experience.
    Cheers.

S
sleighbor author 10/30/2008

Hi PcDoctor,
Thanks for trying to help me out with this problem. I am running SQL server 2005. I am using a SQL login and have made it a database owner of the database.
dxdata is the name of the database and nt1restore is the name of the table.
I have checked that I have grant for all the permissions possible but I am still getting this error. I was reading that it might be a file permissions problem but I have granted full control to the ASP and IUSR users to the IIS folder.
Here is the exact error I am getting:
The OLE DB provider "SQLNCLI" for linked server "ServerA" does not contain the table "dxdata"."dbo.nt1restore"". The table either does not exist or the current user does not have permissions on that table.
I really appreciate your help with this.
thank you,

Kevin

Sergey Kornilov admin 10/30/2008

Kevin,
let proceed step by step. According to the error message you use linked server "ServerA".
Is that correct?

S
sleighbor author 10/30/2008

Yes, ServerA is the server name.
Kevin

Sergey Kornilov admin 10/30/2008

Kevin,
this doesn't answer my question.
Do you use linked server "ServerA"?

S
sleighbor author 10/30/2008

sorry, I am not sure what you mean by linked server. I have created an ODBC connection called dxdata to connect to server ServerA. My default database is called dxdata.
Kevin

Sergey Kornilov admin 10/30/2008

Your error message says you use the linked server. Hence the question.
I suggest to create a new project and use recommended way to connect to SQL server - via third connection option (ODBC driver dialog).

S
sleighbor author 10/30/2008

Creating a new project and using the odbc driver dialog seems to have fixed it! I tried creating a new project before so I am going to assume that it was using your odbc driver dialog that corrected the problem.
Thank you very much for your help and patience with this issue!
Kevin