EPiServer Commerce Version: 9.14 (build 1)
After recently deploying Commerce Manager to a client's environment, we're seeing strange errors when attempting to access the Commerce Manager Administrative pages.
Please note that, apart from some configured database connection strings, the entire set of Commerce Manager installation files are the same as those that I have running locally on my development machine, where the Commerce Manager Admin pages are working correctly.
Can anyone helpme to understand what may be causing this error, and where the Apps/Views data is ultimately sourced from?
I would suggest to check your Apps folder - it's likely that some files are missing or corrupted. You can simply packages\EPiServer.CommerceManager.<version>\tools, then extract EPiServer.CommerceManager.zip there to overwrite files in Apps folder.
Thanks for your reply, however, I don't think I quite understand. Are you saying that there's a file called "EPiServer.CommerceManager.zip" located within the "packages\EPiServer.CommerceManager.<version>\tools" folder? I've looked, and I can't see one there. Can you tell me where to find the "EPiServer.CommerceManager.zip" file?
Also, I'm confident that the entire set of files within the "Apps" folder structure that exist on the client's server (where the error is happening) are the same set of files that exist within my own installtion on my local development machine (where the error does NOT occur).
Do you have any other ideas, or can you help with identifying exactly where this issue may be originating from? (i.e. is it likely to be xml configuration, database configuration etc.)
When you install EPiServer.CommerceManager nuget package on a site (this is to become a Commerce Manager), EPiServer.CommerceManager.<version> should be restored in the packages folder of your solution. EPiServer.CommerceManager.zip should be there.
I don't think this is a xml or database configuration. Your Commerce Manager site appears to be running (you can open the site directly to be sure) - it just looks like the Apps folder is not "right" to me. I would suggest you to double check (using some tools such as Beyond Compare to compare two Apps folder) to make sure Apps folder in the client's server is correct.
Unfortuantely, I definitely don't have any .zip files within the packages\EPiServer.Commerce.9.14.1 folder.
Here's the complete file/folder structure of the packages\EPiServer.Commerce.9.14.1 folder:
| EPiServer.Commerce.9.14.1.nupkg| readme.txt| +---content| \---net45| web.config.install.xdt| \---tools | Copy-DB.psm1 | Copy-EcfConfigsIfNotExist.psm1 | EPiServer.Commerce.config | EPiServer.Commerce.mdf | Get-Config.psm1 | Get-ConfigPath.psm1 | Get-ConnectionConfigPath.psm1 | Get-EPiServerCommerceConnectionString.psm1 | Get-PackagesToolPath.psm1 | Install.ps1 | Set-CommerceManagerSearchIndexBasePath.psm1 | Set-NameSpace.psm1 | +---Configs | baf.config | baf.data.manager.config | baf.data.metaobject.config | baf.library.folders.config | ecf.app.config | ecf.asset.config | ecf.catalog.config | ecf.customer.config | ecf.customization.config | ecf.marketing.config | ecf.order.config | ecf.security.config | ecf.ssl.config | Mediachase.Search.config | \---Infrastructure InitializationModule.cs
No, it EPiServer.CommerceManager package
Sorry, my mistake.
I believe I have now got to the bottom of this issue and you're exactly right, it was a problem with differences in the files within the Apps folder. I was unable to perform a proper folder compare (with Beyond Compare) against the client's server's folder due to restriction in access the server, however, after some manual digging, I discovered that some of the filenames - mostly those config files that begin with an unorthodox filename character - were being mangled (possibly by either NuGet or our TeamCity instalation that packages up the folder for deployment - I've yet to get to the bottom of the exact cause).
Looking at the screenshot below, you can see the problem:
Once I replaced the "Apps" folder with one that did not have the config files' names mangled/encoded, the Commerce Manager interface started working again!
Many thanks for your help!
For anyone else running into this problem, it looks like it is a Nuget bug with version pre-4.6.
Thanks, Craig, for your detailed investigation!