Quantcast
Channel: [Archived] elcoCAD | Promis.e
Viewing all articles
Browse latest Browse all 3874

Wiki Page: Error on backup - ExecuteSQL error...Syntax error in INSERT INTO RW_Int_ExitPoint

$
0
0
Product(s): Promis.e, Bentley Substation Version(s): through 08.11.12.137 Environment: N\A Area: Project Management Subarea: Backup and Restore Project Error or Warning Message When attempting to [[Backup Project|backup]] a particular project, the following error messages occur or similar are displayed and the project is not backed up. Information System Exception: ExecuteSQL error, insert into RW_Int_ExitPoint (ID, Name, X, Y, Z, Handle, RegionId, PageId, Description) values (123,'X',0,0,0,'',456,,'') Syntax error in INSERT INTO statement. --> System.Data.OleDb.OleDbException: Syntax error in INSERT INTO statement. at MDBProxy.ConnectionManager.ExecuteSQL(Int32, nConnectionID, String strSQL) at MDBProxy.LocalTools.ExecuteSQL(Int32, nConnectionID, String strSQL) --- End of inner exception stack trace --- at MDBProxy.LocalTools.ExecuteSQL(Int32, nConnectionID, String strSQL) at ECT.ECAD.DAL.BackupData.BackupMSSQLProject(Int32 projectId, String connectString, String path) Explanation The "Syntax error in INSERT INTO statement" portion of the messages indicate the problem is occurring as the software is trying to insert data from the SQL project database into the database in the backup file. The problem could be that the data violates some constraint, causing the insertion to fail. In the example messages above, there is no value present to be inserted into the PageId column of the RW_Int_ExitPoint table, which violates a constraint of the database. The RW_Int_ExitPoint table is related to exit points of regions used by the [[Run Shortest Distance]] tool. The above example message indicates that there is an exit point in the project not associated with any page, which should not be the case. How to Avoid Option 1 - Copy the project This is known to have worked for one user. Use [[Project Manager]] to copy the project. Back up the copy. Option 2 - Copy the pages into a new project Open [[Project Manager]]. Create a new project based on the same project options as the problem project. Select all the pages in the problem project. Right-click the selection and choose Copy . Specify the new project as the destination project and set remaining options. Generally in this situation, choose Keep Existing and Maintain / Complete where applicable. Click OK. Back up the new project. Option 3 - Remove the problem exit point from the database. Executing the following script will remove exit points not associated with any page for the project with an ID value of 9999. Modify the following script to replace "promise" with the true name of the project database and replace "9999" with the true project id value. The project id can be found on the first line in the ect.fid file, which can viewed using Notepad, and is not the same as the project name. Execute the script using SQL Server Management Studio. This may need to be done by a database administrator. USE promise DELETE FROM RW_Int_ExitPoint WHERE PageId is null AND ProjectId=9999; Back up the project. Original Author: Matt_P

Viewing all articles
Browse latest Browse all 3874

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>