I'm trying to configure MSOffice 2016(x64) on a Windows Server 2012(x64) to run with ABCPdf 9.1.2.5(x64).
At runtime, the application fails because of this message: "Failed to get MS Office installation path."
So far I couldn't find an explicit explanation of why this problem occurs.
The application pool uses the "ApplicationPoolIdentity" (instead of dedicated account) and Office has been installed with an account having Admin privileges.
I also followed recommandation on websupergoo website link here
Machine has been restarted after installation, DCOM config has been made accordingly to instructions given (both for folders and launch/activation);
Is there any way to login as Application Pool user in cmd to run WinWord once ?
Is there any AppData file to copy from one user to another - like for OpenOffice installation ?
For anyone trying this kind of configuration, please be aware that highest compatible version with AbcPDF is Office 2013. Office 2016 is compatible from version 10.
Below, answer from support
The highest version with ABCpdf 9 is Office 2013 - for Office 2016 you
would need to upgrade to ABCpdf 10.
Since office was preinstalled on my laptop, i had to reinstall office 365 through the Office app that was already available.. then abcpdf was able to find my installation path
Related
During my GeneXus installation, there was error in installing Microsoft SQL Server (GeneXus provided installer for 2014 version x86 requiring some WOW64, but my PC is Windows 10 x64).
Anyway, I've tried creating a KB and the GeneXus Trial IDE doesn't auto fill the 'Server Name' field. When I click <Browse for more...> I get an empty list.
Then I've tried putting anything, but the IDE fails to connect to the server.
Then I've tried installing Microsoft SQL Server 2019 for Windows 10, but I didn't install all features, and it didn't change anything.
Anything I could be missing?
Here you have GeneXus 16 Requirements.
I recommend you to install SQL 2017 Express and SQL 2017 Management
Let me know how it goes
Brand new Windows 10 Pro system running 1809. Just installed Access via Office 365 (version 1904). We have a database that was originally created in 1998 and has been updated and working on other Windows 10 systems without a problem. However, when we open it on this new system, we are getting the following error right away:
Compile error. in query expression 'IIf(Hour(Time())<12,"Good Morning",IIf(Hour(Time())>11 And Hour(Time())<18,"Good Afternoon","Good Evening")'
Removing this query does nothing but bring up additional compile errors.
All of the other computers were running Office Pro 2007 at some point - probably when the database was converted from an .MDB to an .accdb file. They are now running the latest version of Access without issue. They all also have an Inactive Application Add-in called "Microsoft Office 2007 Access Database Engine Conflict Resolver" installed and set to Load on Demand. I don't know if this has anything to do with it.
I did install Office 2007 to this computer (Access module only) and that same add-on then appeared in the newer Access. But I have since uninstalled Office 2007 after the issue remained unresolved. (That add-on is now gone.)
My (probably ignorant) guess is that there is old code that isn't being processed correctly and the current batch of computers are handling it via something that was installed during the upgrade process? Our database needs are pretty simple and there are very few users.
Any help in getting this new system into the loop would be appreciated.
Argh. I think the issue was that I installed the 64-bit version of Office 365. All works now under 32-bit. Sorry and thanks.
I have a Win XP Embedded machine (WES2009), that does not have preinstalled "Microsoft Windows Embedded Studio" (MSWES).
I need MSWES as a preposition for development (RTX by IntervalZero).
All I found on MS site related to this product is docs: http://msdn.microsoft.com/en-us/library/ms838630(v=WinEmbedded.5).aspx
Anyone with a clue:
Can I simply install MSWES product on my WES2009 machine ?
Where can I download it simply ? (Preferably without using MS account.)
You don't run Embedded Studio on XP Embedded; you run it on your development host, and use it to create an XP Embedded OS image for your target application.
You need a development license, and ultimately deployment licenses.
You can simply and officialy download the WES2009 here:
http://www.microsoft.com/en-gb/download/details.aspx?id=14947
This should be a trial version, or you apply your bought licence to this.
Here is the antenced of my story
I've got a problem with the VS or IIS. I don't know.
When in the Visual Studio 2010 I try to create website: throw up the follow errormessage:
Unable to create the Wet site'http://www.ecommerce.com'. The Web server does not appear to have FrontPage Server Extensions installe.
I download the Frontpage extension from here: http://www.iis.net/community/default.aspx?tabid=34&g=6&i=1630
Then I read how can it install, but when the article write that:
To extend a Web site using HTML Administration pages on Windows, use the following steps:
Click Start, point to Programs, point to Administrative Tools, and then click Microsoft SharePoint Administrator to open the Server Administration page.
In the list of virtual servers, click Extend next to the virtual server you want to extend.
In the Administrator box, type the user name for the administrator of the virtual server.
Click Submit.
I don't find Microsoft SharePoint Administrator on my Windows 7 Profesionnal 64 bit
or
You can extend a Web site by using the command-line tools, owsadm or owsrmadm. These tools are located in the "%ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\50\bin" folder. To extend a Web site, use the install operation, which takes the following parameters.
I don't find the Web Server Extennsions dir on my Windows 7 Profesionnal 64 bit
I have read another article where write that, Use the Visual Studio DVD go to WCU dir and into the Web Server ... dir, but I don't find...
I download the FPSE and install with my local Administration account.
But the Visaul Studio Always says: The WEb server does not appear to haver FPSE installed.
How can I fix it? Install it?
Bad news (may not be so bad): FPSE for IIS 7 and 7.5 are not supported. Alternative is to use WebDav and here's an article explaining how to migrate FPSE Sites to WebDAV.
Good News (may not be so good due to licensing part): As of December 18, 2010, Ready-to-Run Software Inc. has created Microsoft FrontPage Server Extensions (FPSE) 2002 for IIS 7 and 7.5.
See this announcement from MS: FrontPage 2002 Server Extensions for IIS 7.0 on Windows Server 2008 and Windows Vista
If the FrontPage Server Extensions are installed, this error may occur because the _vti_bin virtual directory is not marked executable. To correct this problem, run the Internet Service Manager, select the Web server having the problem, and use the Check Server Extensions task. Reference: http://msdn.microsoft.com/en-us/library/aa984224%28v=vs.71%29.aspx
I am trying to get the Azure SDK up and running on my dev PC and have been having some issues.
I have installed the SDK, tools for VS and am trying to run the samples. Every time I try to run the samples the Development Storage service starts and then the Developer Fabric tries to start. This is where is stops. The Developer Fabric cannot run any websites for whatever reason.
I have followed their checklist for setting up the system and there is not Event messages. I am running under Vista Home Premium with IIS 7 installed.
If you have any suggestions I would love to hear them.
It turns out my problem is a little deeper than simply Azure not working on my computer.
In order to natively debug IIS apps using windows vista (configured under the project settings) you need to have windows authentication enabled for IIS. This feature cannot be installed let alone enabled under Vista Home Premium under the guise of what home user would want such a feature.
For the average VS 2005 user this is okay there is a hotfix but for me and my fancy VS 2008 SP1 there is no solution.
After becoming supremely frustrated with this issue I posted it as the following Microsoft Connect issue.