I use BizTalk Server 2010. Yesterday I deployed a BAM activity and could browse a corresponding view in the BAM portal. Today I've created another activity, but this time I made it non-RTA and hence I can't open a view for that. Every browser gives me an error:
Views cannot be displayed for one or more of the following reasons:
- Office Web Components 2003 are not installed.
- Your Web Browser does not support ActiveX controls.
- Support for ActiveX controls is disabled.
I've installed Office Web Components 2003 previously and ActiveX controls are enabled. Where's the problem?
Reinstalling Office Web Components 2003 fixed the issue
If you are using your BizTalk installation for tutorial purpose and you have BAM Portal and IE
installed on same machine then you may encounter this error.
Do the following step to get rid of it:
Go to IE Tools -> Internet Options -> Security -> trusted sites -> Sites -> add your BAM website(http://localhost).
(You may need to uncheck -- Require server verification (https:) for all sites in the safe zone)
after that if you need, you may check the option.
Related
I am facing issues in deploying to IIS. Spent a lot of time googling around and trying out things, Inspecting/Installing features on control panel, and many more things.
Step1> On Visual Studio
I am publishing my app to a physical path,
Step2> On IIS, I am adding a website where I'm pointing to that path, and completing other fields. I also set port 8080 for this since 80 was used by other ones.
Now on clicking browse under manage application in IIS, I am getting localhost:8080/Error (Its stuck in the page, showing nothing). Adding the screenshot here.
localhost:8080/Error
Honestly reaching out for help
To resolve this error In Control Panel --> Programs --> Programs And Features --> Turn Windows features on or off -> Internet Information Services -> World Wide Web Services -> Common HTTP Features -> Static Content, IIS Management Console, and HTTP Errors.
Also, make sure .NET Extensibility 3.5 and .NET Extensibility 4.5 are checked.
if the issue still exists then open iis. select site and select error pages->select edit feature setting->select detail error message for the local request and custom error pages for remote request.
are you trying to use the asp.net custom error pages?
Our company ships an MVC based product (targeting v4.5) which has stopped working on a customer site for what appear to be environmental issues - a build which worked with no problems once upon a time now gives a 403.14 - The Web server is configured to not list the contents of this directory.
.
What I think is happening...
The user accesses http://server/AppName
Because it's an MVC app, the default route (Reports/Index) should be used.
Instead IIS is looking for a default document...
... and, not finding one, it assumes the user wants to list the contents of the directory...
...which is not enabled so it throws a 403.14.
.
What I've tried so far...
Accessing the route directly.. results in 404 error. So I'm pretty
sure IIS doesn't realise it should use routing.
Use aspnet_regiis to register ASP.Net with IIS. This was done from the Framework64 folder since...
OS is 64 bit - Windows Server 2008 (Standard without Hyper-V)
IIS is 64 bit - though Enable 32-Bit Applications is true
Checked AppPool is targeting v4 of the framework - it is.
Changed AppPool mode to Classic - was pretty sure it should be integrated but was worth ruling it out. It is now back to Integrated
Confirmed RunAllManagedModulesForAllRequests is set to true in the web.config.
Checked permission conditions defined in <system.webServer> section of web.config are met - they are.
Created the simplest of MVC applications and deployed it - same problem.
Running the command shell as Administrator unregistered ASP.Net using aspnet_regiis -ua and re-registered using aspnet_regiis -enable -i. We hit a couple of permission problems - and the Temporary ASP.NET Files directory was missing but once they were address we were back to the same error.
Added a simple default.htm - when present, this is served in response to the http://server/AppName request.
I'm clean out of ideas and all google hits suggest some combination of the above - or enabling directory browsing (which I think is just a symptom rather than the root cause).
Also, not sure if it's relevant but the amount of configurable elements available for the application in IIS seems a bit below what I would have expected...
Have you Checked the user the application pool process is running under? I think Your site needs to run with permissions to execute the .net libraries and I've seen this just change for seemingly no reason (probably related to an overzealous update to the system).
You can try with the Enabling directory browsing .
assuming you are under Windows Server 2012 or Windows Server 2012 R2
On the taskbar, click Server Manager.
In Server Manager, click the Manage menu, and then click Add Roles
and Features.
In the Add Roles and Features wizard, click Next. Select the
installation type and click Next. Select the destination server and
click Next.
On the Server Roles page, expand Web Server (IIS), expand Web
Server, expand Common HTTP Features, and then select Directory
Browsing. Click Next.
On the Select features page, click Next. On the Confirm installation
selections page, click Install. On the Results page, click Close.
if you using the Windows PC try this in your command prompt as follows:
go to C:\Program Files\IIS Express
then press Enter:appcmd set config
/section:system.webServer/directoryBrowse /enabled
Maybe this is your case https://forums.iis.net/t/1157304.aspx
SQL Server Reporting Services creates a folder called Reports by
default if you install it on IIS. If you install SQL 2008 then
Reporting Services doesn't need to use IIS and instead will try to
reserve the URL with the HTTP.Sys service.
I believe this is the cause of the conflict you are seeing. What you
could try is changing the URL that Reporting Services uses via the SQL
Server Configuration Wizard.
Also I found that
Report Manager of SQL Server can use reports path http://<server name>/reports
Configure a Native Mode Report Server for Local Administration (SSRS)
I think the problem is IIS features that are not installed yet. I have met this kind of problem frequently in Windows Pro. Make sure to turn on every feature under Internet Information Service -> World Wide Services because by default IIS is configured to use WebForms. So there might be some features that not installed yet to use MVC, especially ISAPI filters. In my case, that was the solution. I hope it helps.
Something similar i encountered using VS 2017 & ASP.NET MVC.
Was working on the project for long with no problems at all but suddenly the routing started misbehaving & stopped working.
So I changed the Port in Project Properties Page & it started working.
I really don't know what is the relation between a port & MVC routing modules. Someone else can enlighten if at all this helps.
I had the same problem and I just created an application pool out of the Default Web Site in IIS and stoped the default web site. With that difference you will not have the application pool's path
I know it's been a long time since this question but i've had the same problema recently. I've tried every single configuration, just like #amcdermott did, but the only action that solve the problem was reinstalling .NET Framework.
My app was built under .NET Framework 4.5.2. The application server had the version 4.6.1 and 4.5.2 installed. So, i uninstalled all framework versions and installed the one that i needed.
Please, make sure that no other applications use superior versions of .NET Framework if you going to try this solution.
Here are some quote I find on Microsoft official site which I think may help:
For site administrators
This problem occurs because the Web site does not have the Directory Browsing feature enabled, and the default document is not configured. To resolve this problem, use one of the following methods:
Method 1: Enable the Directory Browsing feature in IIS (Recommended)
To resolve this problem, follow these steps:
Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
In IIS Manager, expand server name, expand Web sites, and then click the website that you want to modify.
In the Features view, double-click Directory Browsing.
In the Actions pane, click Enable.
Method 2: Add a default document
To resolve this problem, follow these steps:
Start IIS Manager. To do this, click Start, click Run, type inetmgr.exe, and then click OK.
In IIS Manager, expand server name, expand Web sites, and then click the website that you want to modify.
In the Features view, double-click Default Document.
In the Actions pane, click Enable.
In the File Name box, type the name of the default document, and then click OK.
Method 3: Enable the Directory Browsing feature in IIS Express
Note This method is for the web developers who experience the issue when they use IIS Express.
To do this, follow these steps:
Open a command prompt, and then go to the IIS Express folder on your computer. For example, go to the following folder in a command prompt:
C:\Program Files\IIS Express
Type the following command, and then press Enter:
appcmd set config /section:directoryBrowse /enabled:true
I'm attempting to install a fresh installation of DNN, to evaluate it as well as extend it with custom functionality. The end goal is to gain knowledge on how it behaves prior to receiving a DNN-based product from a third party developer. I've been stumped right from the outset, so am reaching out to the forum for some help.
Problem Statement
I am unable to install DNN at all, because the installation wizard does not load properly, and is missing some controls. It doesn't load most external resources (.css, .js, etc), and inspecting the headers shows those resources are returning 404 errors. Notably, the browser continually (over 1000x) attempts to load dnn_logo.png, each time returning a 404. I would like to know how to install/configure the site source files so that the installation wizard works properly, and I can continue the installation process. I am using the "Installation Package" variant of the software.
Problem Background
I checked the path of dnn_logo.png and it does in fact exist.
I've been using this guide to install the site: http://www.dnnsoftware.com/wiki/page/install_dotnetnuke (the 2nd section, with separate DB).
My installation environment: Win7 x64, IIS 7.5; SQL Server Express, named instance, using windows auth
DNN version: 7.3.1
Installation folder permissions are:
IIS AppPool\DotNetNuke --> modify
NT Authority\Network Service --> modify
SQL Permissions: both users above are set as db_owner for the database
Attempted Resolution Steps
Followed the written tutorial, as well as four installation videos authored by the DNN team
Reinstalled the site three times - first was using outdated v.7.3, 2nd selected the "unblock" option when unzipping the source
Adjusted folder permissions and double checked them; for user DotNetNuke
Added user Network Service with permissions, according to the info in the linked doc
Adjusted web.config and turned off URL rewriting; ended up reverting all changes
Solved
IIS 7.5 (and others) needs to have the ASP.NET server extensions installed, and this will fix the problem. To get you started: you can add these by either going to Turn Windows Features On or Off from the Start Menu of Windows 7, or by using the Microsoft Web Platform Installer from within IIS (if you've downloaded IIS separately).
The solution was in the developer docs located elsewhere on the DNN site, found here: http://www.dnnsoftware.com/wiki/page/development-environment .
I ran into similar issues and thought I would share my solution for others that may need it. It turned out that turning on IIS Management Service solved my issue. To enable this feature go to turn windows features on or off as mentioned above. Select Internet Information Services -> Web Management Tools & check IIS Management Service.
This is my first ASP.NET project so I am a bit of a rookie when it comes to a lot of the configuring of IIS/Visual Studio so bear with me...
I am using Visual Studio 2010 running on Windows Server 2008 SR2. We recently did some updates on the server and now my project no longer loads when I attempt to debug. When I try to debug the default "Welcome" page for IIS 7 loads instead of my project. I am set up to use the development server to debug, not IIS so I don't understand why I get the IIS page. Before the updates the debugger was pulling up my page without any issues.
Any ideas? Thanks in advance!
It looks like IIS is now bound to the port number that Visual Studio Development Web Server was using previously. You can change the port number in the properties of the web site project.
I have found a solution to my issue. I decided to use IIS instead of the Development Server for debugging. After attempting to debug unsuccessfully yet again, I took a look at the identity that was being used in the application pool and I changed to one with more privileges and that seemed to do the trick. Thanks for the suggestions.
I had the same problem but non-of the earlier answers worked.
I am using Windows 7 enterprise 64-bit, IE11, VS2010, Silverlight 5
I have been developing and maintaining a number of Silverlight projects for the past 5 years, and have always been able to debug them within VS2010 using the ASP.NET Development Server. However, on returning from some well deserved holiday, I found that none of my existing Silverlight projects would run in the debugger. In each case there is a Web project set as the start-up project, and in each case on starting the project within VS2010 (with or without debugging) I got the IIS7 web page instead of my application.
I tried creating a new Silverlight web application, and found that this started normally in the ASP.NET Development Server. I checked my source code and found that no changes had been made in my absence.
After a lot of head scratching, etc., the solution was to clear the IE cache. These are the explicit steps I used:
Close all instances of IE and ASP.NET Development Server.
Open Internet Properties from the Control Panel.
Click "Delete" on the General Tab.
In the Delete Browsing History box check the following options:
a) "Preserve Favourites website data"
b) "Temporary Internet files and website data"
c) "Cookies and website data"
Leave the others unchecked
5) Click "Delete" and wait for the command to complete.
6) Close the Internet Properties box.
7) Rebuild ASP.NET project
8) Start (with or without debugging) in VS2010 - it should now load normally.
Hope this works for you.
I want to deploy Microsoft Word 2010 and Microsoft.Office.Interop.Word on Microsoft Windows Server 2008.
The user (just a few) visits an .ASPX page. Data is input there or selected from the database from the aspx page. Once data is collected, I want to invoke the a Word application instance on the SERVER and progematically insert the data into ranges in the Word document. That doc gets saved in a folder on the server and/or downloaded onto the user's local machine.
Can I deploy Microsoft Word and the interop assemblies on Win 2008 Server? If not, is there another solution?
i was facing the same error, after spending 2 days of my life i found this solution.
You need to assign permissions to the Microsoft office 2003 - 2007 object.
Please have a look.
Step 1
Go to the Component Services > Computers > My Computer > and select DCom Config
after this, go to the right pane and find "Microsoft Word 98 - 2003 Document" object
Step 2
Right click on the component and go to the properties and select "Security Tab"
Step 3
Add NETWORK, NETWORKSERVICE, IIS_IUSRS and Administrator users and assign them "Local" and "Remote" Access Permissions
Step 4
Now go to the "Identity tab" and select "This User"
In user and password textboxes type administrator crediantals and press "Apply" and "OK (must to save the changes)"
Step 5
Now restart your machine.
it'll works.
Regards,
Don't use Office on Server. Use Open XML...
See this Link:
Microsoft strongly recommends that developers find alternatives to
Automation of Office if they need to develop server-side solutions.
Because of the limitations to Office's design, changes to Office
configuration are not enough to resolve all issues. Microsoft strongly
recommends a number of alternatives that do not require Office to be
installed server-side, and that can perform most common tasks more
efficiently and more quickly than Automation. Before you involve
Office as a server-side component in your project, consider
alternatives.
Most server-side Automation tasks involve document creation or
editing. Office 2007 supports new Open XML file formats that let
developers create, edit, read, and transform file content on the
server side. These file formats use the System.IO.Package.IO namespace
in the Microsoft .NET 3.x Framework to edit Office files without using
the Office client applications themselves. This is the recommended and
supported method for handling changes to Office files from a service.
The Open XML file formats are a public standard. To obtain a copy of
the specification, visit the following Web site:
ECMA-376 Open XML Standard