We have a small business and just bought Server 2016 Essentials to run Sage 300. When trying to install Sage 300, it says : "Unsupported Environment - Sage 300 does not support installing on a DC". That's a problem because Essentials Server must be a domain controller. But then says that some features won't work (features we won't use) and gives me the option to proceed anyway. I proceed, but the it doesn't run : "the server the unable to process the request due to an internal error". So, my question is: Can Sage run on Server 2016 Essentials? If not, can I upgrade Essentials to Standard and NOT use/install a domain? Right now we only use the server as a file share. This is a small office and we just wanted a file server to run Sage.
The bottom line is that it is possible to run Sage 300 on Server 2016 Essentials.
I was able to click by the "unsupported environment" error and it installed just fine. The Sage website has conflicting information on whether it will run or not but we are running it successfully.
The 2nd error was caused by a bug in our version of Sage, in which a service was not starting correctly (it needs to be manually restarted as a work-around).
Once I did that, everything ran perfectly.
Related
I'm having trouble with setting up ACORE API's and then having them work on a website.
Background:
Azerothcore running 3.3.5 on a debian standalone server, this has the Database, Core files and runs both the world and auth server basically a standard setup that is shown in the how-to wiki.
I also have a standalone web server, on the same subnet, but it's a separate server running linux and normal web server stuff, this has a wordpress installation with azerothcore plugin for user signup etc.
I'm trying to add the player map (https://github.com/azerothcore/playermap) and the ACORE-API set of functions (server status, arenastats, BG que and wow statistics) (https://github.com/azerothcore/acore-api)
Problem:
I understand the acore-api must be run in a container (docker or whatever) on the server, which I have done and it binds to port 3000, I can then go to the local ip:3000 and it brings up this error. (all db's etc are connecting and soap is working)
error 404 when navigating to IP:3000
I do get a few errors when running NPM install seen here: I'm not sure if they would be causing any issues or not.
screenshot of NPM errors on install
But further that, when I put say 'serverstatus' on the webserver (separate server) and configure the config.ts file I can't seem to get anything to display.
I'm not sure what I'm doing wrong but is the same scenario for all of the different functions for the acore-api
How are these meant to be installed and function? I feel I'm missing a vital step.
Likewise, with PLAYERMAP I have edited the comm_conf.php and set the realmd_id, but when loading the page, I do get the map, but the uptime is missing and no players are shown?
Could someone assist if possible?
Seems like an issue with NodeJS version. Update your NodeJS to latest LTS version 16.13.0 (https://nodejs.org)
I am trying to install Teradata connection in a virtual machine of Windows Server 2012.
I tried multiple times but I still got the timed out error: No response received when attempting to connect the Teradata error.
I tried connecting through SQL assistant and python teradata module. Below is what I have tried based on resolutions found on web search and none of them works
1. Close the firewall
2. Change the odbcLibPath (in Python)
3. Reinstall .NET framework
4. Extend the time awaiting for response
5. Seeking resolutions around odbc.ini and odbcinst.ini but for Windows specifically, I can not find any resolution.
I have also not be able to find much difference between the configuration on the virtual machine and that on my local desktop which works well.
I felt I have run out of possible solutions at the moment. Appreciate any help in this.
I've followed the instructions at the link below to "Build and simulate a Cordova iOS app in the cloud". https://taco.visualstudio.com/en-us/docs/build_ios_cloud/
After completing the instructions I'm able to build and get the iOS simulator working, however, I'm unable to attach a debugger.
The message displayed in remotebuild is:
GET /cordova/build/5655/debug 500 10.865 ms - 28
In Visual Studio I see the following in the Debug window:
Starting launch process C:\Program Files (x86)\nodejs\node.exe "(redacted)\node_modules\vs-tac\emulator.js" --platform ios --action launch --path "(redacted)\buildInfo.json" --serverUrl https://(redacted):3000/cordova --certificateName (redacted) --language en-US --loglevel info --cliVersion 5.4.1 --npmInstallDir "(redacted)" --deployTarget "iPhone 5"
Timed out connecting debugger to remote Apache Cordova app. See Output window for JavaScript console output.
------ Cordova tools 5.4.1 already installed.
Requesting emulate on iOS Simulator for buildNumber 5655 on server https://(redacted):3000/cordova...
Emulated - Successfully sent to ios Simulator
------ Cordova tools 5.4.1 already installed.
Requesting debug on remote iOS device for buildNumber 5655 on server https://(redacted):3000/cordova...
Failed to Debug iOS remote for build (redacted)\buildInfo.json to https://(redacted):3000/cordova :
iPhone 5
My local development machine is using Visual Studio 2015 and Cordova 5.4.1. I have Node v0.12.2 installed locally and v0.12.9 installed on the MacInCloud. Following the instructions in the link above, I am NOT an admin on the Mac machine.
I've also already tried the instructions suggested in this SO answer: Visual Studio Debugger failing to connect to remote Apache Cordova app in iOS simulator
All the suggestions and the links provided by others were helpful but ultimately my assessment of the problem was not being admin/root on the Mac. The Visual Studio Cordova docs linked in my original question would suggest that you can do all that you need on a Mac without having admin/root access but in my experience that is just not the case.
To the credit of the MacInCloud group, they were very helpful in making changes that I requested to permissions and for reinstalling packages such as brew, ios-webkit-debug-proxy, remotebuild, etc... but after a while that back-and-forth kind of approach to fixing the issue proved painful. When I switched from a Managed MacInCloud server to a Dedicated one, everything worked almost immediately.
Looking back I think the initial execution of remotebuild, which executes brew -- without being admin on the box -- caused the whole process to go south. I was warned when I ran remotebuild for the first time that it would install some brew components that might need root access. That should have been a warning sign to me that not being admin on the box was going to be an issue...
Even though I was able to get a Dedicated MacInCloud server working, the lesson I learned about having control over the Mac prompted me to just buy a Mac Mini. That was a little more difficult to setup because I was now doing everything myself, but ultimately I think it will pay off in the end.
For anyone else struggling with similar issues here is a brain dump of some things I learned along the way:
You don't necessarily need to get Visual Studio talking to the Mac to debug Cordova applications. You can use Safari Web Inspector from the Mac. https://blog.nraboy.com/2015/10/debugging-your-apache-cordova-ios-app-with-safari/. Even though I finally got VS working, I actually prefer this because it is more like Chrome's debugger which I prefer to Visual Studio's.
The ios-webkit-debug-proxy NPM package mentioned in other comments and links is basically a proxy which Visual Studio uses to debug the simulator in exactly the same way Safari does as mentioned above. For this proxy to work you must also be allowed to connect to the Mac over ports 9221-9322. https://github.com/google/ios-webkit-debug-proxy. Prior to learning that I thought I only needed port 3000 open for the remotebuild proxy...
The package necessary for launching the iOS simulator from remotebuild is ios-sim and it will occasionally timeout when launching the simulator and cause the debugger not to attach. This is a known limitation. https://github.com/phonegap/ios-sim and https://blogs.msdn.microsoft.com/visualstudio/2014/11/13/tools-for-apache-cordova-update-ios-debugging-windows-8-1-support/ (see comments).
If you should feel the need to install/uninstall brew it is very easy to do. Just run the install script and if already installed it will give you instructions on how to uninstall. http://brew.sh/ and https://github.com/Homebrew/homebrew/blob/master/share/doc/homebrew/Troubleshooting.md#troubleshooting. To uninstall or reinstall a NPM package is equally easy and Google is your friend.
Read and re-read both of these links for setting up a Mac: https://taco.visualstudio.com/en-us/docs/ios-guide/ and https://taco.visualstudio.com/en-us/docs/build_ios_cloud/. Getting the RemoteBuild.config right is crucial for getting secure connections to work -- especially if you want to access your Mac Mini at home from across the internet.
If you are remoting to a Mac I highly recommend iRAPP or some other VNC alternative. My experience has been that VNC is painfully slow and having a bad connection when you're troubleshooting issues just leads to more aggravation. http://www.coderebel.com/products/irapp/
As mentioned above, the MacInCloud guys were great when I asked for support, but if you do need root access for more than six months the cost of a Mac Mini is less than a Dedicated server plan.
Cheers
Since it is the call to /cordova/[...]/debug that is failing it looks like you might not have ios_webkit_debug_proxy installed. You could try making sure that homebrew is installed (from http://brew.sh) and running brew install ios-webkit-debug-proxy. Afterwards you should be able to run ios_webkit_debug_proxy without an error.
If that runs successfully then you should be able to quit out of ios_webkit_debug_proxy and debugging should work via remotebuild.
I'm attempting to create a custom WordPress theme using MS WebMatrix and am encountering the following error when trying to install the WP app:
Error 2738: Could not access VBScript runtime for custom action
This occurs when the download attempts to install Web Deploy 3.5. I'm currently running Windows 7 64-bit OS.
The research that I've done indicates this is error stems from "VBScript being not properly configured to run on the PC."
The solutions I've encountered and tried - to no avail - are:
Run MS FixIT
Re-registering the VBScript dll via cmd prompt - c:\windows\syswow64\regsvr32 vbscript.dll
Run the System File Checker tool sfc /scannow
[Note: I do not have, nor have I had McAfee installed - I've seen reports that in some instances the McAfee installation can cause the wrong vbscript .dll to be registered]
Outside of doing a factory wipe - which I'd like to reserve as a last resort or completely scrap using WebMatrix entirely - I've run out of potential solutions searching this specific problem.
Has anyone had success with this issue outside of the solutions posted here already? Any help would be appreciated.
So, I discovered a solution to this issue that hasn't been covered well online, so I'm posting it here.
A steadfast solution to resolving this error if running Windows 7 64-bit OS:
Open your registry editor
Start -> Search -> Type "regedit"
In the editor, click on:
HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\Wow6432Node\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
Check the value for (Default)
If it's anything other than C:\Windows\SysWOW64\vbscript.dll that's where your issue is originating
Make sure you have the correct permissions to edit the value for (default)
Right Click on InprocServer32 -> Permissions -> Give yourself "Full Control"
Now edit (Default) and set it to C:\Windows\SysWOW64\vbscript.dll
Reboot
This should fix any issues that might have been encountered during the execution of custom VBScript during Web Deploy download.
Our web application used the old Crystal Reports XI Rel 2 activeX to render the reports called from classic ASP. We would like now to have it run alongside the new Crystal Reports 13 run time to render reports called from ASP.NET.
We installed the exe found in http://scn.sap.com/docs/DOC-7824 (support pack 3). On our dev machines (windows XP) everything went alright, and we were able to design and render reports in both technologies. We tried to deploy it today to a client's server (Windows Server 2008 64 bit) and it obviously didn't work.
If we first try to open the new report then the old one, they both fail, but with completely generic and therefore useless error messages ones like "Error while creating report". the new one is OK, but the old one fails with message "Invalid TLV record".
Inversely, if, after restarting iis, we first try to open an old report (CR XI R2 from classic ASP), it shows correctly, but the new one (CR 13) gives this error:
Retrieving the COM class factory for component with CLSID
{F734A321-8381-4FFD-A614-139E8906DC83} failed due to the following
error: 80000003 One or more arguments are invalid (Exception from
HRESULT: 0x80000003).
We tried to google this error; the only meaningful result was this thread but it didn't help us.
Thank you
EDIT: ok, the first error was simply that the .rpt files were being left out of the deployed folder. So it really boils down to an incompatibility of the CR runtimes, maybe?
EDIT 2: Yes, it is definitely it. We moved the new report in another virtual directory running under another application pool and now they both work, regardless of what is instantiated first. So is there any way we can gradually migrate our existing records, ie have a period where both run times coexist and are used by the same virtual directory?
I had this problem. As I had just installed CR 13 without a reboot, I thought I'd try a reboot of the server. After the reboot, the problem went away.
I have the same error - reboot didn´t help.
Installed SAP Crystal Reports runtime 13.0.0.99 on Win7 but got several errors registering components during installation - think that is the cause of the problem.
Downloaded and installed CR Runtime 13.0.21.2533 (32bit)
from
https://wiki.scn.sap.com/wiki/display/BOBJ/Crystal+Reports%2C+Developer+for+Visual+Studio+Downloads
http://downloads.businessobjects.com/akdlm/crnetruntime/clickonce/CRRuntime_32bit_13_0_21.msi
That installed without errors but didn´t work either :-(