I installed Domino Server 9.0.1 and lotus Notes. The Enable DAS option is not available at all in the web Engine tab at all.
How can II enable it as 9.0.1 must support it by default! I am using the Enterprise version. Do I need to install some plugin?
UPDATE
I tried to uninstall it and install it again ,this time selecting standalone mode and the option is available if "Load Internet configurations from Server\Internet Sites documents" to disabled as #Knut Herrmann mentioned.
The issue is that I have to use this domino server as additional server and in that mode I am not getting this option
UPDATE 2
I am using Domino server 9.0.1 in additional server mode, that connects to a main server for syncing the data which has a Domino server 8.5.3 . I am not able to get the option under Web Engine tab to enable DAS.
Set field "Load Internet configurations from Server\Internet Sites documents" to disabled on server document's basic tab:
Only if this option is disabled the section "Domino Access Services" on tab "Internet Protocols / Domino Web Engine" is visible.
Related
Installing IBM MobileFirst Studio 7.0 using MFPF_7.0_ELP_UPD_IBM_MF_STUDIO.zip but due to local LAN security we are not able to get dependency from eclipse market place which are required and downloaded directly from download.eclipse.org org. Where can we download necessary requirements and use this as local repository?
You can try this .zip file, but I'm pretty sure it is the same: http://public.dhe.ibm.com/ibmdl/export/pub/software/products/en/MobileFirstPlatform/mobilefirst_studio_plugin_7.0.0.zip
When using the .zip file, you can also attempt the installation with the "Contact all update sites..." checkbox un-checked, before proceeding with the installation in Eclipse.
In general, the MFP Studio installation requires an outside Internet connection.
Find a location with a working connection, install. Make a copy of your Eclipse for future use.
Standard scenario for this setup is to have a central installation (with Internet connection). Then archive that specific installation, and then sneakernet it each of the disconnected workstations. You must do this for each type of workstation (Win/OSX/Linux) to be supported. No its not optimal, but does resolve the problem. Hope this helps.
You can check with your network administrator if they can allow your machine to access to the internet via a proxy server. If this is possible all you need is to configure the network connection in Eclipse to include your proxy server setting. You can see the detail here:
http://help.eclipse.org/luna/index.jsp?topic=%2Forg.eclipse.platform.doc.user%2Freference%2Fref-net-preferences.htm
I am new to Hyper-V and Server Core but I am stumped as to how to install a guest OS from an ISO using only PowerShell.
I have downloaded the Hyper-V Server ISO and installed it on my server. It only installs Server Core and does not give me the option for a full GUI option. I configured its network settings, etc and all looks ok. So Server Core installed properly and Hyper-V feature is enabled. I can use PowerShell to create a VM with VHDX and link my Guest OS ISO to it. When I start the VM there is no console UI to install the OS.
How are you supposed to install a guest OS with no console interface to setup the OS?
Note, there is no option under this configuration to enable the OS GUI as some posts have suggested.
First, please don't confuse "Server Core" with "Hyper-V Server". "Server Core" is an installation mode of Windows. Among other things, it can be converted to GUI mode, which is why people keep telling you to just turn the GUI on. Hyper-V Server looks like Server Core but it is not Server Core.
For your actual problem, you're not going to find a simple out-of-the-box solution. You could work up a complete unattended installation process. You could set up a Windows Deployment Services server and have it install via PXE boot. I think some of the third-party Hyper-V management solutions allow you to connect to the console of a VM from within the local Hyper-V Server.
Hyper-V Server was designed with headless operation in mind. It was expected that you would use it to configure and perform maintenance on the management operating system and, if desired, the virtual machines as containers. The guest operating systems themselves were not really meant to be managed from within Hyper-V Server. What it's expected that you'll do is use a full GUI, whether another copy of Windows Server or a Windows desktop operating system running Remote Server Administration Tools to remotely connect to Hyper-V Server and manage its VMs.
I am trying to search file system using Search.CollatorDSO:
Provider=Search.CollatorDSO;Extended Properties="Application=Windows"
On what Windows OS is this provider available by default? According to this question it is not installed on Web editions of Windows Server.
If it is not installed can it be installed manually?
After much digging, it appears the only way to get the ole db provider: Search.CollatorDSO is to enable the Search service in windows OS itself. Installing Search Server from the download does not install it. (Confusing!)
Note that Windows Search Service, what this thrad is about, is completely distinct from "Search Server."
I want to deploy an MVC 4 web application to a Windows Web Server 2008 based dedicated hosting. I am using SQL Server 2008 R2 Express as my back-end database. What steps will I need to take regarding the following:
Installing SQL Server 2008 R2 Express on the web server and deploying my database.
Managing SQL Express database remotely using SSMS.
Configuring database path in my EF5 generated model
Deploying my application
Managing changes to my application.
Can someone provide me a detailed answer/some good links?
Installing SQL Server 2008 R2 Express on the web server and deploying my database.
This depends on your provider. Most providers, if not all, allow you to install your own licensed SQL Server. If you will be using an Express edition then it is, and should be, 100% allowable by your provider. The only step you need here is to go to download page of SQL Server 2008 R2 and download the appropriate file you need. The files you need on that page are the ones with "ADV" in its name. Choose x64 if you will install a 64-bit OS or choose x86 if you will install a 32-bit OS.
Managing SQL Express database remotely using SSMS.
This depends on the firewall set by your provider. But basically this is how you will allow remote access to your SQL Server:
For Windows 2008 R2
Login to your dedicated server using Remote Desktop. If you don't know how to do this, it's best that you consult with your provider.
Go to Start > All Programs > Microsoft SQL Server 2008 R2 > Configuration Tools -> SQL Server Configuration Manager
On the window that open in step #2, expand SQL Server Configuration Manager (Local) -> SQL Server Network Configuration -> Protocols for SQLExpress
On the right pane, right-click TCP/IP and select Properties.
Select the IP Addresses tab and then scroll to the IP All section.
Set/change the TCP Port value to/from 1433 to 14333 (or any other port) and then click OK.
Right-click TCP/IP again and Enable it
Restart your SQL Server by going to Start -> All Programs -> Administrative Tools -> Services -> SQL Server (SQLEXPRESS) -> Restart. The Restart is on the left pane.
Configuring database path in my EF5 generated model
Unfortunately, I cannot answer this one as I believe you are using the EF designer in creating your model. I never worked with EF that way, but only by code-first. I have to skip this part and let you Google this.
Deploying my application
There is already a good documentation written here so I will not dupliate it here. Basically what you need to do is enable FTP on your dedicated server. Then once that is setup you can go on with bin-deploying your application.
Managing changes to my application.
I assume what you are asking here is that if you have changes to your application, how would you re-deploy it. A bin-deployment will not hurt. Deploying only the files in which you have changes is a good approach. Knowing which files changed can vary depending on the tools you use. In addition, if you don't have any fancy setup that will tell your users you are deploying changes to your site, you might want to take a look at this post. It tells you to put a App_Offline.htm file in your root web directory. That should still work with MVC, after all MVC is still ASP.Net.
I have done some research, based on the problem that my single server gives me when I try to open a document library in windows explorer from the ribbon menu item "Open in Windows Explorer".
The same problem occurs when I try to map sharepoint to a folder in windows explorer too.
The error is:
Your client does not support opening this list with Windows Explorer
From the net, suggestions are:
(Since I'm trying this operation from server itself) enable Desktop Experience
Install the KB907306 update.
Enable IIS webDav service (Some say, it's just for additional functions from the MS Whitepaper)
(Edit) Started webClient service
I've already done them. Nothing changed. Proper machine restart and iis too have done.
Need some serious advice.
Thanks in advance.
Not sure if we are having exactly the same problem BUT I have had similar problem while accessing SP via Windows Explorer in Windows Server 2k8.
What I done to fix it is following:
Install new server feature called Desktop Experience (it comes with WebDAV redirector, which allows you to connect to WebDAV) - Note: Server will need to be restarted.
In Services start WebClient service (go to properties and make sure it starts automatically)
You will now be able to access your sharepoint via entering network path such as \sharepointhost\application\myawesomeapplication\ etc.
Hope that helps.
If you are trying to do this from the server, test it from a server which is not on the SharePoint farm (or better yet, a client machine). Ensure all of your testing is done from machines which are not on the farm.
Do NOT enable the IIS WebDAV service, as SharePoint provides its own WebDAV service and the IIS one overrides it in the pipeline. Enabling this service is a sure path to breaking WebDAV.
If you have SSL enabled, you may be in for a rough time getting it to work. Start by understanding how to use the 'net use' command, and the #SSL suffix.
make sure your webdav is installed as feature
make the following registry fix (http://support.microsoft.com/kb/841215) :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters
Add a new DWORD "BasicAuthLevel" and change this to "2"
Restart your machine (and make sure it is enabled in IIS)
Make sure that WebClient windows service is running in the server. This shall appear in client operating systems like Windows 7, windows 8 however, on the server operating systems like Windows Server 2008, it shall be installed by enabling the server feature "Desktop experience" using Server Manager
This issue nearly killed me. I found that I was using a 64 bit version of my browser and that is'nt supported. I changed over to the 32 bit and it works.