Reports not working with clean install on MSSQL

Hi,

We’ve done a clean install of SuiteCRM but with an MS-SQL database. When I try to create a report I get a blank screen and the following error in log file:


11/06/13 12:36:56 [1868][1][FATAL] aor_reports for aor_report_aor_fields failed to load

11/06/13 12:36:56 [1868][1][FATAL] Error inserting into table: aor_fields: Query Failed:
INSERT INTO aor_fields (id,name,date_entered,date_modified,modified_user_id,created_by,
deleted,aor_report_id,field_order,module_path,field,display,link,label,function,sort_by,group_by)
VALUES (N'fced09f1-18e3-839b-e2d0-527a3754b11b','',
CONVERT(datetime,N'2013-11-06 12:36:55',120),
CONVERT(datetime,N'2013-11-06 12:36:55',120),
'1','1',0,N'6e9d18c1-5049-b433-669e-527a377549a4',0,N'YToxOntpOjA7czo4OiJBY2NvdW50cyI7fQ==',N'name',
1,0,N'Name','','','0')::: 

[Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near the keyword 'function'.

Can anyone please confirm whether they have been able to run the new SuiteCRM on MS-SQL…and if so, whether they know how to solve this problem.

Thanks
Andrew

Hi agray,

The user in this topic managed to install SuiteCRM 7.0 on his Windows OS with mssql, however this seems to be a bug where the keyword function is already used.

Thank you for highlighting this.

Regards,

Will.

Will,
Thanks for the rapid response.
When I look into the database there is no table so it’s not surprising that the “INSERT INTO aor_fields” failed. The only tables that exist are:
aor_reports
aor_reports_audit
aor_conditions
aor_charts

Do you think this suggests a problem with the installation process?
Regards
Andrew

Hi Andrew,

Please perform a quick repair & rebuild. You will need to scroll to the foot of the page once this has run and Execute the changes. This will create the tables that are missing.

Thanks,

Will.

Will,

I think I’ve discovered what the problem is: there is a field “aor_fields” called “function” which is a shame because whenever MSSQL sees this it treats is as a FUNCTION command. To fix this the field name needs to be wrapped in []

This fails:
INSERT INTO aor_fields (id,name,date_entered,date_modified,modified_user_id,created_by,deleted,aor_report_id,field_order,module_path,field,display,link,label,function,sort_by,group_by)…etc

But this works:
INSERT INTO aor_fields (id,name,date_entered,date_modified,modified_user_id,created_by,deleted,aor_report_id,field_order,module_path,field,display,link,label,[function],sort_by,group_by)…etc

Regards
Andrew

Hi Andrew,

Yes, I may have mentioned in an earlier post that this is a bug as the function keyword is already reserved.

Thank you for highlighting this issue, and for posting your solution.

Regards,

Will.

Will,
Can you give me any idea as to when the next minor-release (7.01?) might become available?
Thanks
Andrew

Hi Andrew,

There is no set release date for a minor upgrade. There will be a roadmap released for 7.1.0, which will detail what is to be included. SuiteCRM 7.1.0 is due for release in January 2014.

Thanks,

Will.

Is there a fix available for this? I guess that the install script needs the square brackets inserted? Has this been done or is there any instruction on which file to edit?

Thanks

J

Hi J,

This will be resolved in the next minor/bug fix release.

Thanks,

Will.

1 Like

Any idea on the possible eta for this? I would rather wait for this than starting dev with the current version but I need to inform product owners on the timing…

I believe that it’s going to be resolved in v.7.1 which is slated for release towards the end of January.
Regards
Andrew

1 Like

Hi J,

There will be a bug fix release soon but there is no exact date set for release.

Thanks,

Will

1 Like

Will is there any possible way you can tell me where / how to make these changes in the meantime? I am experiencing tons of pressure to get this installed from up top.

Hi jucedupp,

If you require a reporter module there are others out there such as KReports and AlineaSol reports.

Thanks,

Will.

Will

I actually just need to be able to install the package on MSSQL so that I can start migrating our current stored procedures and custom modules from MySQL to MSSQL.

Regards

Jacques