I have created release in Azure Devops, which should be deplyoing my web application to IIS which is on a physical server (Windows Server 2008) but firstly I am getting a warning:
##[Warning 1]
The operating system the agent is running on is "Windows Server" (OS name: 2008, OS version: 7601), which will not be supported by the .NET 6 based v3 agent. Please upgrade the operating system of this host to ensure compatibility with the v3 agent. See https://aka.ms/azdo-pipeline-agent-version
Then I am getting a error:
I have created an Agent on my server, and until today I was not getting this error. How could I fix this?
Windows Server 2008 reached end of life years ago, so no modern tool is going to support it any more.
You might feel lucky that things were running, but that luck finally ran out. You have to upgrade your machine to a supported Windows version.
Related
I have Windows 10 Enterprise Version: 20H2, Experience: Windows Feature Experience Pack 120.2212.4170.0. This upgrade happened last week. I had Oracle 19c server and client installed in my system with a database configured which was working fine before the Windows upgrade. I had all registry entries and the Oracle Windows services were visible under services.msc. I have an application installed which was configured using this same database. Suddenly I am seeing that the Oracle services are not showing under Windows Services, I don't see any registry entries which were there. Please can anyone help if similar issue has been observed and resolved. thanks!
This is regarding Abbyy Setup issue that we are facing on a Azure Cloud Machine which is a Windows Server 2019 VM.
We followed the Admin Guide for Reader 12, the "Manual Runtime Installation Steps" were followed for the setup. The Bin64, Data and Inc folders are copied into a directory which will be later used while registering FREngine.dll on the OS. We have not done the Abbyy SDK installation.
We have VM setup locally which is a Windows Server 2019 VM image. On this setup we are able to Register the FREngine.dll successfully using regsvr32 command. Also we don’t see any issue and is working, w.r.t reading OCR/Barcode values successfully through Abbyy FineReader.
ISSUE
The issue is on the Azure Cloud System [VM Windows Server 2019], where we are able to Register the FREngine.dll successfully using regsvr32 command. However even with the successful Registration of FREngine.dll, when we try to initialize the FREngine, we are getting an exception "Invalid Engine instance" during the call to InitializeEngine( ) with all the Required parameters set.
// Create the abbyy engine instance in outproc process,
// as its recommended by Abbyy for 64-bit process
outProcLoader = new OutprocLoader();
if (outProcLoader != null)
engine = outProcLoader.InitializeEngine(AbbyyEngineUtils._strProjectId,
engLicensePath,
AbbyyEngineUtils._strEngPwd,
"", "", true);
Here we have a license file which is also copied into the location where FREngine.dll is present.
Due to this initial Step failure Abbyy Logs could not be generated from the codebase. However we see a log file that gets generated from Abbyy in the path “C:\ProgramData\ABBYY\SDK\12\FineReader Engine\” at this point of failure which states as follows:
10552 :ABBYY Licensing Service is unavailable: The RPC server is
unavailable.
We also we additionally tried running the Abbyy SDK’s Sample applications on this machine. This also fails with the above error during Abbyy Engine Initialization.
How can this be resolved?
More Info on Licensing Service:
We additionally tried installing the LicensingService and the LicensingSettings.XML had :
ProtocolType="LocalInterprocessCommunication" />
Here Ours is a Standalone Abbyy Installation and hence the Protocol Type used is LocalInterprocessCommunication which is for the local Licensing Service. It is not necessary to specify this protocol type for Standalone installation, as Standalone licenses are always used with the LocalInterprocessCommunication protocol type.
This was an additional Step tried by us. However the actual issue was with the Abbyy Licensing on Azure.
Did you happen to start the abbyy licensing service in the Azure VM ?
(Windows Key + R) Run command --> services.msc
In the Services Dialog, find the Abby...Licensing service.
Right Click -> Properties
You can click on the start and click ok.
Retry your above steps. Also, you could have startup type as Automatic if this works in the services in dialog.
As any other OCR solution some have licensing constraint to run on Azure and AWS , make sure your license is compatible.
as posted here
https://support.abbyy.com/hc/en-us/articles/360016441600-Can-I-run-FineReader-Engine-in-Virtual-Machine-or-Container-
also I would check the OS compatible version.
ABBYY SDK 12 Licensing Service has been tested in the following virtual environments:
Windows Server 2016, Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2
Windows 10, Windows 8.1, Windows 8, Windows 7 SP1
I'm having troubles enabling remote debugging on sharepoint online. I have 2 machines, my local machine (Windows 8.1) and my development server(Windows Server 2008 R2). On my development server I first tried remote debugging using Visual Studio 2012 Update 4, as described here: http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug.
When this didn't work I tried doing exactly the same thing on my local machine, which has Visual Studio 2013 (Ultimate) update 1 and the latest windows azure sdk (2.3). This worked perfectly. Thinking upgrading to visual studio 2013 would solve my problem I've installed 2013 (Premium) on my dev server, next to 2010 and 2012. After installing and updating everything for 2 hours however, I came to the conclusion that I received the same error as on VS 2012.
Googling came up with a few interesting causes for this bug: sitenames longer than 20 characters or sitenames containing hyphens. This is not the case. Then I verified port settings, the dev server has no active firewall but I wanted to exclude any possibilities. And low and behold, both telnetting from my local machine as my dev server to ports 4016 and 4018 of my azurewebsites.net url worked.
Are there any other solutions for this bug? Since debugging locally is not an option (sharepoint provider hosted app for project online) this is very inconvenient.
Thanks,
UPDATE: Deploying the site as a cloud service works, and so does remote debugging them. However, we would like to stay with azure web sites for now..
I know this is a duplicate of Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023; but none of the solutions there or on twitter were of any use.
Check out Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023
I think this has to do with blocked ports 4016 and 4018
I recently resinstalled Windows 7 on my machine and went back to downloading and installing the tools to help me continue developing node.js windows azure web applications. I followed the instructions given on the node.js azure site:
http://www.windowsazure.com/en-us/develop/nodejs/
and using web installer 4.0 it says I have successfully installed these tools:
Windows Azure Powershell
Windows Azure SDK for Node.js - June 2012
Windows Azure SDK for .Net (VS 2012 RC) - June 2012
IIS Recommend Configuration
The problem I am experiencing is that when I run the site using powershell e.g:
start-azureemulator -launch
it goes ahead and runs IIS Express, and after several minutes IIS Express crashes with the following information:
Problem signature:
Problem Event Name: APPCRASH
Application Name: iisexpress.exe
Application Version: 8.0.8298.0
Application Timestamp: 4f620349
Fault Module Name: iiscore.dll
Fault Module Version: 8.0.8298.0
Fault Module Timestamp: 4f63b65c
Exception Code: c0000005
Exception Offset: 00021767
OS Version: 6.1.7601.2.1.0.256.28
Locale ID: 1033
Additional Information 1: f66d
Additional Information 2: f66d807b515d6b2dc6f28f66db769a01
Additional Information 3: 7b2f
Additional Information 4: 7b2f6797d07ebc2c23f2b227e779722e
I am running 2 instances each time, and both of them crash one after the other. Is anyone experiencing something similar and fix this issue ? Is their an upgrade I need to do ? I've run windows update but it says I've got all the latest updates etc.
Can I tell the powershell cmdlet to use IIS 7 instead of IIS Express? I'm guessing its something to do with IIS Express on my machine.
I did some hunting around and found this person here who experienced a similar problem:
https://github.com/tjanczuk/iisnode/issues/149
I've got a cron job running every 1 second, to check if any website totals need to be updated. Could this be causing IIS Express to crash?
Cheers
I believe your problem will be resolved if you install and use iisnode for IIS7 64bit (instead of iisnode for iisexpress) from the link below as I could fix a similar issue in past:
http://go.microsoft.com/?linkid=9784331
need urgent help
i am not able to run the solution in the local environment. I have created the hello world sample and trying to run the application but i am getting error like some prerequisites are missing. Below in the configuration i have.
Installed in VM--
Window server 2008 OS-32 Bit
VS 2010
Installed the Azure SDK
But when i am running the solution i am getting below error ---
Windows Azure Tools: Warning: The Windows Azure development fabric and development storage are running on a 32-bit workstation. In the cloud, Windows Azure Hosted Services run in a 64-bit environment. The use of native code execution or .Net Full Trust features such as P/Invoke may require migration to 64-bit. See http://go.microsoft.com/fwlink/?LinkId=145047 for details.
Windows Azure Tools: Error: Running .NET 4.0 web roles on the Windows Azure Development Fabric requires installing the following QFE: http://support.microsoft.com/kb/958854, or upgrading to SP2 of Windows Vista or Windows Server 2008.
Windows Azure Tools: The system is missing a prerequisite to execute the service. Please see the release notes.
Can any one suggest what i am doing wrong ??
As said, you are using 32-bit environment. Retry on 64-bit Windows Server.
Also make sure the client profile in not set on the .NET Assembly versioning... Choose .NET 4
Did you upgrade to SP2 of Windows Server 2008 as suggested by the warning message ? And the mentioned hotfix for IIS7 & .NET 4.0: http://support.microsoft.com/kb/958854.