We have integrated R 3.1.2 with ASP.NET. But after deploying application in IIS 6.0, application is not able to call some of the R packages like RODBC, stats, etc. We are getting following error:
Error: Package or namespace load failed for stats.
The same error we are getting for package RODBC.
IIS 8.5 still same issue. thanks to "Pravin Mane"
right click on My Computer, > properties > Advanced System Setting >
Environment Variables, the see in the System Variables window, there
is a variable named path. Select path, click on edit and add the path
where R packages have been stored.
One correction - enter in the path variable path to bin folder (64 or 32 bit depends on your appool setting.) enter something like this
C:\Program Files\R\R-3.3.2\bin\i386\
IMPORTANT!! Restart the server, just re-starting IIS did not help me and I spent few more hours looking for solution.
Related
I decided to publish the ASP.NET MVC project to test it locally using IIS Manager. Therefore, after opening the necessary windows features, I created a new folder in the C:\inetpub\ directory on IIS Manager:
In the Visual Studio IDE I right clicked on the solution and clicked "Publish..." and specified that the target was "Folder":
When I clicked the Next button, I specified in the next window that the "Target" location was the C.\inetpub\TechnologyArticle directory. Then when I clicked the "Publish..." in the Visual Studio IDE, I encountered an error that I did not receive in Debug mode:
System.AggregateException: One or more errors occurred.
---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
---> (Inner Exception #0) Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
---> Microsoft.WebTools.Shared.Exceptions.WebToolsException: Build failed.
How can I solve this problem? Is the reason why I got this error in Release mode, which I did not receive in Debug mode, due to programming?
This error is not due to programming. The reason for this error is trying to publish the website in the C:\inetpub\ directory, which is made visible and/or created by a service that you have activated by "Turn Windows features on or off" to publish the ASP.NET website locally. The user has no right to modify the C:\inetpub\ directory. Therefore, the current user's right to modify the C:\inetpub\ directory must be declared manually in the Windows 10 operating system.
When the ASP.NET website is published, the project outputs (such as *.dll files, style files, scripts, Views) compiled in Release mode will be extracted to the target directory, so the user must have the right to write to the C:\inetpub directory.
To resolve this issue, follow the steps below:
Open the properties of the C:\inetpub folder (With the folder selected, use the ALT + ENTER shortcut).
Switch to the Security tab and click the Edit button.
Define "Full Control" right for current user and confirm settings by clicking OK button.
You repeat the publish procedure to publish your website.
I'm building an ASP.NET MVC application and when every time I start debugging, it throws an error
Process with an ID (Random number every time) not running
in Visual Studio 2015 Enterprise.
Also in the output window, I see the following lines:
The program '[10144] iisexpress.exe: Program Trace' has exited with code 0 (0x0).
The program '[10144] iisexpress.exe' has exited with code 0 (0x0).
What I tried:
deleting .VS folder in the solution
deleting IISExpress folder in My Documents
changing project URL of the web site
checking out 'Use 64bit version of IIS Express' in Tools > Options > Projects and solutions > Web projects
deleting DEvelopmentServerPort, DevelopmentServerVPath and IISUrl in CSPROJ.
repairing IISExpress from Add/Remove programs.
like most of every solution I could find in StackOverflow and every where in the web.
According to your description, I suggest you could try below solution.
1.Open your project file (csporj): Upload the project and right client the project file.
2.Find DevelopmentServerPort, if it contains and delete it then reload the project.
If this solution doesn't solve your issue, I suggest you could try this solution.
Eidt
If your machine is 64bit, please go to Tools-> options -> projects and solutions:
Could you please tell me this issue is only occured for current MVC application? If you start a new web application, it will work well.
If above solution doesn't solve your issue, I suggest you could try to use process monitor to find how IIS work.
Details about how to use process monitor, you could refer to below steps:
Download Procmon tool from https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
Open Procmon.exe as Administrator.
3.Remove all the filters -> then Apply -> then OK
4.Make sure the telescope icon is shown as below, this indicates the capture is ongoing
5.Then reproduce the issue
Press CTRL + E to stop the trace capture
Press CTRL + S to save the log
Click "All events", Save log as "Native Process Monitor Format (PML)".
9.If this pml doesn't contain the importent data,you could share the pml to me to analysis it.
When i try to start my ASP.NET application from VS (2015 or 2017) it just crash with no error in output window.
The program '[8464] iisexpress.exe' has exited with code 0 (0x0).
But Windows Event log says this:
The Module name ManagedEngineV4.0_32bit path C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\webengine4.dll returned an error from registration. The data is the error.
I have no more ideas about how to fix this.
I've tried to reinstall VS, IIS, even tried to remove .net framework, change IIS settings from 32 to 64bit but no luck so far.
Any chance someone experienced similar error and found the solution? :)
P.S.
Extended error log:
System
Provider
[ Name] IIS Express
EventID 2293
[ Qualifiers] 49152
Level 2
Task 0
Keywords 0x80000000000000
TimeCreated
[ SystemTime] 2017-06-06T20:47:56.693031400Z
EventRecordID 7271
Channel Application
Computer PC
Security
EventData
ManagedEngineV4.0_32bit
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\webengine4.dll
2BEE0CC0
Binary data:
In Words
0000: C00CEE2B
In Bytes
0000: 2B EE 0C C0 +î.À
I know this is an old thread, but this has been killing me today. And since this is pretty much teh top thread on any search for the error, i decided to add this.
taken from here
"Unable to launch the IIS Express Web server" error
Delete folder IISExpress from "My Documents"
Load your project again, it will create IISExpress folder again with updated configuration
Check IISExpress folder has sufficient permissions to read-write the configuration file
Load project again and Run IISExpress. It should work.
I didn't need to check any permissions or anything, just deleting and reloading the project was enough for IIS to behave itself and i could get back to some debugging fun.
Cheers
After couple of days spent trying to solve the problem, i didn't succeed, so here is quick workaround:
Uninstall of IISExpress v10
Install IISExpress v8
And everything works just fine
We encountered this same problem and event viewer error using IIS. For us the problem was we were modifying C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Aspnet.config to apply some garbage collection improvements, and ended up with a typo in the XML.
So not related to IIS Express, but thought I'd mention it for others who find this post when searching for the error message:
The Module name ManagedEngineV4.0_64bit path
C:\windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll
returned an error from registration. The data is the error.
This question is related to my previous question.
I need to publish a C# application (that has been set up in IIS 6.0 and built in VS2010) to a desktop with win7.
I have set up IIS on my desktop well. Now I can install the application on my laptop by accessing the URL
http://myDesktopName.domain.com/MyApp
pointing to a physical location in desktop
e:\myPath\myApp\myAppService.svc
When I publish a new version of the web service, the application should get updated when I open it.
But, it gave me an error:
**the filename,directory name, or volume label syntax is incorrect**
After searching online, I found this error is normally caused by some unacccepted chars in the link. Here is the code that the msi (MS installer) needs to access and get the new version of the application.
System.Diagnostics.Process.Start("msiexec", "/favmuso \"" + myurl + "\"");
here,
myurl is http://myDesktopName.domain.com/MyApp/MyAppSetup.msi
Here, http://myDesktopName/MyApp/ is the virtual directory set in IIS 6.0 on my desktop. I can access and download it from IE in my laptop without any problems.
But, when the application notified me that a new version is available for updating the old one, I clicked the pop-up ballon on the application icon and then I got the error:
Error 123. The filename, directory name, or volume label syntax is incorrect.
If I try to access it from the C# code, I got the same error.
Then, I did a test by running
msiexec **/favmuso** http://myDesktopName.domain.com/MyApp/MyAppSetup.msi /Lv mapp_msi.log
In the log file, i found :
MSI (s) (80:DC) [18:04:33:089]: SECREPAIR: Failed to open the
file:http://myDesktopName.domain.com/mypath/\myAppSdetup (10).msi for computing its hash. Error:123
Error 123. The filename, directory name, or volume label syntax is incorrect.
Why my applcation setup file name was changed to
\myAppSdetup (10).msi
The "/favmuso" options can be found at
https://technet.microsoft.com/en-gb/library/cc759262%28v=ws.10%29.aspx#BKMK_Install
Any help would be appreciated.
thanks
So I noticed that you've asked this question elsewhere, and everyone was focused on the /favmuso piece of it.
I've been recently exeriencing this issue when trying to repair MSIs with a URL source when the original application was installed by SCCM 2012.
The workaround I found was to add a registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer. The value below causes the MSI to skip the problematic portion of the repair and move on.
Name: SecureRepairPolicy
Type: REG_DWORD
Value: 1
To be a bit safer, you look into setting the registry value to 2 and using a whitelist as described in this Microsoft article: https://support.microsoft.com/en-us/kb/2918614. (Ctrl+F "Steps to opt-out the affected programs".)
My co-worker is able to deploy our projects to AWS Elastic beanstalk fine. However I have issues on both my work machine and my home laptop. Both computers have the same error in AWS window pane.
I get a pop up as follows:
Deployment of the website failed due to errors during build of the deployment archive,
check visual studio output window 'Build' and/ or 'Amazon Web Service' panes for more details.
Then in the amazon window pane I get a different error everytime I try to run the deployment.
Example 1:
...package build 'CopyPipelineFiles': error in 'C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets' at (1413,5): Copying file Web.config to obj\AmazonDev\TransformWebConfig\original\Web.config failed. Could not find file 'Web.config'.
Example 2:
...package build 'TransformXml': error in 'C:\Users\Andrew\colony\colony-website\Colony.Web\Colony.Web.csproj' at (840,5): Could not open Transform file: Could not find file 'C:\Users\Andrew\colony\colony-website\Colony.Model\Web.AmazonDev.config'.
Seems to be a different error each time -- I'm not sure how to even begin to look for any issues.
Jim Flangagan's comment is the answer: ReSharper 8.2 is causing this problem. To resolve either disable resharper ( Tools>Options>ReSharper>General>Suspend Now) or upgrade Resharper.