I am trying to migrate a Sitecore 8.0 installation to Sitecore 9.0, and the documentation in the Sitecore Developer portal suggests using the Sitecore Express Migration Tool as the most painless way to do this. However, when I run the application I get an immediate error:
An unexpected error has occured. Please restart the tool and try again. For more information, see the log files.
I checked the log files and I only see this:
[ 1] 11:40:43.421 INFO [WizardCore] Moving to the next step. Current step key: ''.
[ 1] 11:40:43.510 ERROR Unable to perform wizard step transition. Source: <no>, Target: basic_parameters_step.
System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
at System.Reflection.RuntimeAssembly.nLoadFile(String path, Evidence evidence)
at System.Reflection.Assembly.LoadFile(String path)
at Sitecore.ExpressMigration.Core.Plugin.PluginRepository.LoadPlugins() in C:\BA\e849cf469cb4cf58\src\Sitecore.ExpressMigration.Core\Plugin\PluginRepository.cs:line 44
at System.Lazy`1.CreateValue()
at System.Lazy`1.LazyInitValue()
at Sitecore.ExpressMigration.Pipelines.WizardSteps.CreateBasicParameters.AddModuleVersionSelectors.Process(CreateBasicParametersArgs args) in C:\BA\e849cf469cb4cf58\src\Sitecore.ExpressMigration\Pipelines\WizardSteps\CreateBasicParameters\30_AddModuleVersionSelectors.cs:line 54
at Sitecore.ExpressMigration.Core.Pipelines.PipelinesService.Pipeline.Run[T](T args) in C:\BA\e849cf469cb4cf58\src\Sitecore.ExpressMigration.Core\Pipelines\PipelinesService\Pipeline.cs:line 54
at Sitecore.ExpressMigration.Wizard.Steps.Start.BasicParameters.BasicParametersStep.CreateRootDataRequest(Migration migration) in C:\BA\e849cf469cb4cf58\src\Sitecore.ExpressMigration\Wizard\Steps\Start\BasicParameters\BasicParametersStep.cs:line 119
at Sitecore.ExpressMigration.Wizard.Steps.Start.BasicParameters.BasicParametersStep.<OnBeforeStepEnterAsync>d__29.MoveNext() in C:\BA\e849cf469cb4cf58\src\Sitecore.ExpressMigration\Wizard\Steps\Start\BasicParameters\BasicParametersStep.cs:line 84
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Sitecore.ExpressMigration.Wizard.Core.WizardCore.<PerformStepTransitionAsync>d__51.MoveNext() in C:\BA\e849cf469cb4cf58\src\Sitecore.ExpressMigration\Wizard\Core\WizardCore.cs:line 220
[ 1] 11:41:06.247 INFO [WizardCore] Moved to the next step. Current step key: ''.
This is default, without any configuration changes; the system paths referenced do not exist on my system (C:\BA\e849cf469cb4cf58) and I'm not sure how to specify where my actual Sitecore project folder is. I've been looking through the migration document on the Developer portal, but everything documented is written assuming starting the application worked.
What can I do to get past this error? Is there some configuration changes I need to make?
Open Sitecore.ExpressMigration.exe.config
Add the following line <loadFromRemoteSources enabled="true" /> to the <runtime> section
Related
I pulled the latest code from https://github.com/aspnet/MusicStore/tree/dev
Without making any changes to the code. I built the application for
dnx version : 1.0.0-rc2-16308 coreclr x64
The application builds successfully , however when I try to run the application,
I get the below error.
System.NullReferenceException: Object reference not set to an instance of an object.
at Xunit.Runner.Dnx.Program.GetAvailableRunnerReporters()
at Xunit.Runner.Dnx.Program.Run(String[] args)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Dnx.Runtime.Common.EntryPointExecutor.Execute(Assembly assembly, String[] args, IServiceProvider serviceProvider)
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
Please Note , The same code base worked successfully couple of days back.
We're in the process of migrating from dnx to dotnet. The migration happens on the dev branch so all the code there might not compile or fail at runtime. This is most likely one of those cases.
From the callstack I assume you're trying to run the tests. In the dotnet world, we run tests a little different and we haven't got yet to MusicStore with the conversion.
Sorry for the inconvenience.
RC2 is not stable. Downgrade to RC1
https://github.com/aspnet/MusicStore/releases
I have created a simple ASP.NET 5 project based on the ASP.NET 5 beta 8 Visual Studio template.
I have published the project using this command
dnu publish <path to project.json> --out <path to publish folder> --configuration Release --runtime dnx-coreclr-win-x64.1.0.0-beta8 --wwwroot-out "wwwroot" --no-source
After I run the web.cmd on nano server I received this error:
.\web.cmd : System.DllNotFoundException: Unable to load DLL 'kernel32': The specified module could not be found. (Exception from HRESULT:
0x8007007E)
+ CategoryInfo : NotSpecified: (System.DllNotFo...LT: 0x8007007E):String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
at Microsoft.AspNet.Server.Kestrel.Networking.PlatformApis.WindowsApis.LoadLibrary(String dllToLoad)
at Micros
oft.AspNet.Server.Kestrel.Networking.Libuv.Load(String dllToLoad)
at Microsoft.AspNet.Server.Kestrel.ServerFactory.Start(IFeatureCollection serverFeatures, Func`2 application)
at Microsoft.AspNet.Hosting.Internal.HostingEngine.Start()
at Microsoft.AspNet.Hosting.Program.Main(String[] args)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Dnx.Runtime.Common.EntryPointExecutor.Execute(Assembly assembly, String[] args, IServiceProvider serviceProvider)
at Microsoft.Dnx.ApplicationHost.Program.ExecuteMain(DefaultHost host, String applicationName, String[] args)
at Microsoft.Dnx.ApplicationHost.Program.Main(String[] args)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.Dnx.Runtime.Common.EntryPointExecutor.Execute(Assembly assembly, String[] args, IServiceProvider serviceProvider)
at Microsoft.Dnx.Host.Bootstrapper.RunAsync(List`1 args, IRuntimeEnvironment env, String appBase, FrameworkName targetFramework)
at Microsoft.Dnx.Host.RuntimeBootstrapper.ExecuteAsync(String[] args, BootstrapperContext bootstrapperContext)
at Microsoft.Dnx.Host.RuntimeBootstrapper.Execute(String[] args, BootstrapperContext bootstrapperContext)
The same command doesn't throw this error when running on Windows 10. The application works fine on Windows 10.
Nano Server does not have kernel32.dll and advapi32.dll so code that is not linked against default libs won't work. You need to either link your code against onecore.lib or install reverse forwarders.
Reverse forwarders redirect calls to kernel32.dll/advapi32.dll APIs to the counterparts available on Nano Server.
On some OneCore systems (e.g. Win10 IoT Core on Raspberry Pi 2), reverse forwarders are installed by default. This is not the case in case of the Nano Server, since the goal is to make it as small as possible. Hence the need to install reverse forwarders manually if you need them.
To relate this to Asp.Net 5 - both Http Platform Handler and Kestrel (or to be more specific libuv) are linked against default libs. Therefore, to run Asp.Net 5 on Nano, you need forwarders, unless you use WebListener (which should work fine without forwarders).
Hypothesis
You mention that this application is working fine on Windows. How are you running it on Windows? There's a good chance you are using dnx451 and not dnxcore50 (CoreCLR) as your target platform.
This is a problem because you are publishing for CoreCLR. (--runtime dnx-coreclr-win-x64.1.0.0-beta8), and there's a good chance when you are running locally, it is using the full .NET framework.
Does It Work with CoreCLR on Windows 10?
Here's what I'd do: Try to run the web app in the Developer Command Prompt for Visual Studio 2015 using dnx.
Switch to the CoreCLR version of .NET using dnvm:
dnvm use 1.0.0-beta-8 -r coreclr
Restore packages
dnu restore
Run
dnx web
If this fails, we know what is the issue. If this succeeds, there's a chance that Nano doesn't provide the native Windows APIs your code is trying to execute. If that is the case, you have to identify the code that is causing this and use something else.
How to target only CoreCLR in Visual Studio
You can remove the dnx451 target from your project.json so that Visual Studio is forced to use the dnxcore50 (CoreCLR) version. Ideally we want to be running the exact same version / environment we are publishing to.
I am using Unity for in WCF service to load component.
I am referring below mention article.
https://msdn.microsoft.com/en-us/library/vstudio/hh323725(v=vs.100).aspx
Service is working fine when i build service in visual studio with build option option any CPU.
As one third party component required 64 bit specific build. So i selected 64 bit build option.
I have downloaded Unity code and build for 64 bit but it is also not working.
I am getting below mention exception.
Could not load file or assembly 'Common.Unity' or one of its dependencies. An attempt was made to load a program with an incorrect format.
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.
Exception Details: System.BadImageFormatException: Could not load file or assembly 'Common.Unity' or one of its dependencies. An attempt was made to load a program with an incorrect format.
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.
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Common.Unity' could not be loaded.
As this is not issue of Unity.
It is issue of IISExprees of VS2012 which is support on 32 bit.
Can't get IIS Express 8 beta to run website as 64-bit process
https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3254745-allow-for-iis-express-64-bit-to-run-from-visual-st
I am working on a custom module for Dot Net Nuke and am currently just setting up my environment. I have it pretty much completed however every time I try to export and use the default templates provided by Chris Hammond I also get an error with the module.
It always comes back with :
"
Error: EmployerPortalManager is currently unavailable. DotNetNuke.Services.Exceptions.ModuleLoadException: Unable to find the requested .Net Framework Data Provider. It may not be installed. ---> System.ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed. at System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName) at PetaPoco.Database.CommonConstruct() at PetaPoco.Database..ctor(String connectionStringName) at DotNetNuke.Data.DataContext.Instance() at UBA.Modules.EmployerPortalManager.Components.ItemController.GetItems(Int32 moduleId) in c:\websites\vmotest02\DesktopModules\EmployerPortalManager\Components\ItemController.cs:line 46 at UBA.Modules.EmployerPortalManager.View.Page_Load(Object sender, EventArgs e) in c:\websites\vmotest02\DesktopModules\EmployerPortalManager\View.ascx.cs:line 45 --- End of inner exception stack trace ---
"
Any ideas on how to go about solving this problem? I am using DNN 07.02.02 (303) and VS 2012 with the 2.5 templates in C#.
Any help is appreciated.
So I installed RavendDB on a Win2003 server using these instructions:
http://old.ravendb.net/documentation/docs-deployment-iis
And i get the following error when I try to browse to the site. Any ideas?
Version of log file is not compatible with Jet version
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.
Exception Details: Microsoft.Isam.Esent.Interop.EsentBadLogVersionException: Version of log file is not compatible with Jet version
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.
Stack Trace:
[EsentBadLogVersionException: Version of log file is not compatible with Jet version]
Microsoft.Isam.Esent.Interop.Api.Check(Int32 err) in C:\Work\ravendb\SharedLibs\Sources\managedesent-61618\EsentInterop\Api.cs:2739
Microsoft.Isam.Esent.Interop.Api.JetInit(JET_INSTANCE& instance) in C:\Work\ravendb\SharedLibs\Sources\managedesent-61618\EsentInterop\Api.cs:131
Raven.Storage.Esent.TransactionalStorage.Initialize(IUuidGenerator uuidGenerator) in c:\Builds\raven\Raven.Storage.Esent\TransactionalStorage.cs:207
[InvalidOperationException: Could not open transactional storage: C:\Inetpub\wwwroot\RavenDB\Data\Data]
Raven.Storage.Esent.TransactionalStorage.Initialize(IUuidGenerator uuidGenerator) in c:\Builds\raven\Raven.Storage.Esent\TransactionalStorage.cs:220
Raven.Database.DocumentDatabase..ctor(InMemoryRavenConfiguration configuration) in c:\Builds\raven\Raven.Database\DocumentDatabase.cs:151
Raven.Web.ForwardToRavenRespondersFactory.Init() in c:\Builds\raven\Raven.Web\ForwardToRavenRespondersFactory.cs:62
Raven.Web.RavenDbStartupAndShutdownModule.<Init>b__0(Object sender, EventArgs args) in c:\Builds\raven\Raven.Web\BootStrapper.cs:12
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +213
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +76
The RavenDB datastore uses Esent under the hood. As a result it's not portable across OS versions. I.e. if you create a store on one version of an OS, it won't necessarily work on another just by copying the files across.
You can use the RavenDB smuggler tool to import/export the data. Or do it manually.