Single Database - Known Issues

Owned by Andrew Paydon
Last updated: Sept 03, 2018 by James Overell

The following, apart from the bug list, are known issues with the Single Database solution.

Passwords

Due to new encryption routines, the following characters cannot be used in passwords

  • {
  • }
  • >
  • <

Contained Logins

  • Logins are not 100% contained as yet
    • zSynergetic_{database name}_ServerLogin must currently exist
    • At present is used to send emails through the MSDB database

Multi-tenants

  • All logins are required to exist in the SynergeticShared database, eg for one tenant
    • zSynergetic_E0000
    • zSynergetic_E0000_Live_ArrivalDeparture_dbo
    • zSynergetic_E0000_Live_CommunityPortal_dbo
    • zSynergetic_E0000_Live_CoreAPI_dbo
    • zSynergetic_E0000_Live_crystal_dbo
    • zSynergetic_E0000_Live_crystal_finance
    • zSynergetic_E0000_Live_CrystalReportPortal_dbo
    • zSynergetic_E0000_Live_CrystalReportPortal_finance
    • zSynergetic_E0000_Live_main_dbo
    • zSynergetic_E0000_Live_main_finance
    • zSynergetic_E0000_Live_ServiceSuite_dbo
    • zSynergetic_E0000_Live_StudyPeriod_dbo
    • zSynergetic_E0000_Live_SynAPI_dbo
    • zSynergetic_E0000_Live_UserFormSimple_dbo
    • zSynergetic_E0000_Live_WebService_dbo

Crystal Reports

Crystal Reports has a known issue where database objects have the same name but exist in different schemas.

When run, regardless of which database it has been verified against, the first instance of the database object will be referenced which may not be correct.

An example of this is the INVCS.RPT which references finance.pvCommunityAddresses, however that same object also exists in the dbo schema.

To fix this we have created a new object (finance.pvCommunityAddressesFinance) and changed the reference from finance.pvCommunityAddresses to the new object – this resolves this particular problem.

A known list of affected reports are listed below:

viewreportDSY reference

pvCommunityAddresses


  • invcs.rpt
  • purord1.rpt
  • rcpt3.rpt
  • rcpt4.rpt

Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.

pvCommunityAddresses


gljnlsub2.rpt

gljnlsub3.rpt

payprl2.rpt

rcpt5.rpt

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

vCommunityAddresses

ComID.rpt
ENQACTINFOPACK.rpt
FUTACTAPPREC.rpt
GLDEPEXS.rpt
NCEAStudentResults.rpt
payPOE.rpt
STFHOMCONTLST.rpt
stucontl.rpt
stucontlCLASS.rpt
stucontlha.rpt
stuenrls.rpt
stureenr.rpt
STUTQA.rpt
stutrf.rpt
stutrfN.rpt

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

crspSynergeticViewFieldsSYSVIEWC.rpt

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Linked Servers and Synonyms

Where the Synergetic legacy databases were being used for access from a linked server, this is no longer possible.

An error message may be generated similar to:

Cannot process the object ""SynergyOne"."dbo"."Community"". The OLE DB provider "SQLNCLI11" for linked server "LinkedServerName" indicates that either the object has no columns or the current user does not have permissions on that object.

Linked servers attempting to access references from the synonym database appear to be unable to do so.

The only workaround is to change any linked server references to use the single database directly.