Plus Community - for users of ACCPAC & Adagio accounting software

Welcome to the PlusCommunity forums! PlusCommunity is a gathering place for companies running Simply Accounting, ACCPAC Plus, Sage Accpac ERP (ACCPAC Advantage/ACCPAC for Windows), and Adagio Accounting.
New visitors, please click here!

Page 1 of 1 1
Topic Options
#53050 - 05/05/17 04:26 AM Web Screens Error Sage 300 2017 (PU2)
dan-zill
Member


Registered: 05/05/17
Posts: 2
Loc: Sri Lanka
Hi,

Sage 300 2017 (PU2) installed on Windows Server 2012 R2, gives an error when opening the webscreens. It's not directing to the log in screens even.

"Could not load file or assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' or one of its dependencies. The system cannot find the file specified."

Please let me know where to look at for a resolution.

Installed as local administrator. IIS is correctly working on the machine. Applied product update 2. Double checked and re-run the portal database.

Thank you,
Danushka

FUll Error as follows;

Server Error in '/Sage300' Application.

Could not load file or assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Stack Trace:

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1590.0

http://Localhost/Sage300
Page 1 of 1
Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' or one of its dependencies. The system cannot find the file specified.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' could not be loaded.
[FileNotFoundException: Could not load file or assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' or one of its dependencies. The system cannot find the file specified.] Sage.CA.SBS.ERP.Sage300.Web.MvcApplication.Application_Start() +0
[HttpException (0x80004005): Could not load file or assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' or one of its dependencies. The system cannot find the file specified.] System.Web.HttpApplicationFactory.EnsureAppStartCalledForIntegratedMode(HttpContext context, HttpApplication app) +9982013 System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +118 System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172 System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +336 System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +296
[HttpException (0x80004005): Could not load file or assembly 'ACCPAC.Advantage.Types, Version=6.4.0.0, Culture=neutral, PublicKeyToken=4d7048ecf2312a7c' or one of its dependencies. The system cannot find the file specified.] System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +9963380 System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +101 System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +254


Top
#53051 - 05/05/17 07:23 AM Re: Web Screens Error Sage 300 2017 (PU2) [Re: dan-zill]
Jay Converse Administrator
Member


Registered: 07/31/00
Posts: 7555
Loc: Location, Location
Call Sage tech support.
_________________________
Jay Converse
Sage 300 Whisperer

Top
#53052 - 05/05/17 08:33 PM Re: Web Screens Error Sage 300 2017 (PU2) [Re: Jay Converse]
dan-zill
Member


Registered: 05/05/17
Posts: 2
Loc: Sri Lanka
Thank you Jay.
Top
#53177 - 08/20/17 10:31 PM Re: Web Screens Error Sage 300 2017 (PU2) [Re: dan-zill]
anthonyyager
Member


Registered: 08/20/17
Posts: 1
Loc: Canberra, Australia
Danushka,

What was the outcome, how did you fix this issue?

Anthony

Top
#53178 - 08/25/17 02:57 PM Re: Web Screens Error Sage 300 2017 (PU2) [Re: anthonyyager]
AWA
Member


Registered: 02/07/08
Posts: 263
Loc: Johannesburg, South Africa
Also would like to know.
Have same problem
No solution from Sage other than downgrading to Server 2012R2.

Anybody have problems with Sage 300 V2018 on MS-Server 2016 and web screens?

Thinking of skipping 2017 and go directly to 2018.

Top
#53179 - 08/25/17 03:02 PM Re: Web Screens Error Sage 300 2017 (PU2) [Re: AWA]
Jay Converse Administrator
Member


Registered: 07/31/00
Posts: 7555
Loc: Location, Location
Don't bother, Sage Web screens are a waste of time.
_________________________
Jay Converse
Sage 300 Whisperer

Top
#53184 - 08/26/17 12:09 PM Re: Web Screens Error Sage 300 2017 (PU2) [Re: Jay Converse]
AWA
Member


Registered: 02/07/08
Posts: 263
Loc: Johannesburg, South Africa
Well we can't expect them to be anything like Odoo, but we still have to try because clients expect them to work.

I believe a few are using them.

Top
Page 1 of 1 1


Moderator:  Jay Converse 
Hop to: