Colin MacQuillin Posted September 7, 2023 Share Posted September 7, 2023 I have downloaded the full Sage 200 SDK and it has given me files at version 20.0.49.0 However if I download the beta release (I guess prior) it has the version 20.0.50.0. I am looking at Sage.Utils.dll to get this information. Ultimately I have tried both these sets of files and cannot get the sdk to work. I have seen '{"The type initializer for 'Sage.Accounting.Application' threw an exception."} and other errors so must be doing something basic incorrectly. This is version 2023R2 Thanks for your help. Colin Link to comment Share on other sites More sharing options...
Colin MacQuillin Posted September 7, 2023 Author Share Posted September 7, 2023 I have also seen {"Logon failed due to unexpected error.\r\n\r\nPlease check if the Sage200Configuration database is configured and running.\r\n\r\n(Message was: The type initializer for 'Sage.Common.IdentityProvider.AuthenticationProvider' threw an exception.)"} Just for information I have had this running since Sage 2017 year on year no problem. This 2023 R2 is giving me problems. Link to comment Share on other sites More sharing options...
Administrators Ben Smith Posted September 12, 2023 Administrators Share Posted September 12, 2023 Hi Colin, Thanks for your question - I see you've sent in a case to Developer Support so we will deal with the issue via email. For members of the UK Developer Programme that is still the preferred method for support. Regards, Ben Link to comment Share on other sites More sharing options...
Philip Walker Posted October 4, 2023 Share Posted October 4, 2023 Hi Colin Did you activate the SDK, I am having an issue with the 2023 R2 also but related to activation. When I open the SDBX Packager, I am asked to register the software which is something I have never had to do before with the SDK. However, when entering the Serial Number supplied by BP Services I get the following error: Regards Phil Walker 1 Link to comment Share on other sites More sharing options...
Administrators Ben Smith Posted October 10, 2023 Administrators Share Posted October 10, 2023 Hi @Philip Walker, There were some changes made to the licence requirements in 2023 R2. You will need to migrate your licence by completing this form. You will be provided with new details that should be used with the SDK tools. Regards, Ben Link to comment Share on other sites More sharing options...
Nigel Bogle Posted January 31 Share Posted January 31 This reply is for Colin. I had this little issue earlier this year and for me it was caused by not setting the company number when I connected to the application. This scenario was explained in the SDK under the heading 'Connecting to Sage'. I hope this helps. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now