SQL – Page 4 – Spitfire Client Services

KBA-01204: The server principal “Master60SP” is not able to access the database “sfSol6DocSys”KBA-01204: The server principal “Master60SP” is not able to access the database “sfSol6DocSys”

May 7, 2012| Dorothy McGovern|

Purpose & Scope: When saving in Microsoft Dynamics SL, the following error message appears: System Message 916: The server principal ‘Master60SP‘ is not able to access the database ‘sfSol6DocSys‘ under

KBA-01403: Adding a custom item to the Spitfire Help MenuKBA-01403: Adding a custom item to the Spitfire Help Menu

January 9, 2012| Dorothy McGovern|

Summary: A custom item, URL Link, or document can be added to the Spitfire Help Menu. In the example below a custom user guide is added to the Spitfire Help Menu.

KBA-01487: Keeping site-specific customizations after Spitfire updatesKBA-01487: Keeping site-specific customizations after Spitfire updates

October 12, 2011| Dorothy McGovern|

Question: We have made some backend customizations to our site, which are lost after Spitfire updates. How can we make these customizations reapply automatically after an update? Answer: Backend customizations are

KBA-01430: Replacing Spitfire SQL stored procedures with Custom SQL codeKBA-01430: Replacing Spitfire SQL stored procedures with Custom SQL code

October 6, 2011| Dorothy McGovern|

Question: Can I replace a Spitfire SQL stored procedure with one of my own? Answer: Yes, sometimes. When the datalayer starts, it scans for stored procedure owned by the SQL

KBA-01404: Spitfire Lookup EditorKBA-01404: Spitfire Lookup Editor

October 5, 2011| Dorothy McGovern|

Purpose & Scope: Spitfire offers a Lookup Editor utility for maintaining and creating Lookups for use in sfPMS. This Lookup Editor requires access to your SQL Server and the Spitfire

KBA-01383: Deleting multiple Spitfire documents through SQLKBA-01383: Deleting multiple Spitfire documents through SQL

October 5, 2011| Dorothy McGovern|

Purpose & Scope: How to use SQL to delete multiple Spitfire documents. Procedure: Note:This process is executed in SQL Server and is intended for use by the System Administrator. While

KBA-01325: Can I use Site_Wrapup.sql to overwrite a Spitfire default in a database other than the Spitfire database?KBA-01325: Can I use Site_Wrapup.sql to overwrite a Spitfire default in a database other than the Spitfire database?

October 3, 2011| Dorothy McGovern|

Question: Spitfire has a few default Doc types listed in the left-panel Documents Menu. When I update with the Configuration Tool (ICTool), Spitfire rewrites these entries and overwrites my changes. Can I

KBA-01324: Resolving: Runtime version does not match last published versionKBA-01324: Resolving: Runtime version does not match last published version

October 3, 2011| Dorothy McGovern|

Question: sfPMS displays a page that reads Sorry, SFPMS is not available at this time. How do I correct this? Answer: The message Sorry, SFPMS is not available at this time indicates

KBA-01274: Conversion failed when converting the varchar value “ISNULL(ex_act_amt,0) + ISNULL(ex_com_amt,0)”KBA-01274: Conversion failed when converting the varchar value “ISNULL(ex_act_amt,0) + ISNULL(ex_com_amt,0)”

September 30, 2011| Dorothy McGovern|

Problem: When loading a budget or forecast spreadsheet the following error appears: ‘An error – ‘Conversion failed when converting the varchar value ‘ISNULL(ex_act_amt,0) + ISNULL(ex_com_amt,0) to data type int. occurred

KBA-01268: SQL Server Versions with Service PacksKBA-01268: SQL Server Versions with Service Packs

September 30, 2011| Dorothy McGovern|

Summary: SQL Server Versions This great chart is from http://sqlserverbuilds.blogspot.com/ (excessive advertising notwithstanding) See also https://support.microsoft.com/en-us/kb/321185 You can determine what version SQL Server is running by using this Query: Select @@version, @@MICROSOFTVERSION @@Version

Tag: SQL