Writing to Application Log on a remote Windows 7 machine - event-log

I need to write to an application log on a remote Window 7 computer. When my PC was running Windows 7, I could do so using a Write-Entry cmdlet, eventcreate, WriteEvent API, or LogEvent in VBS. Since upgrading my PC to Windows 10 (v1511), this no longer works failing with an error "The procedure number is out of range". I can write to an application log on a remote Window 10 machine, but the problem is with the remote (not firewalled) Window 7 PC. How can this problem be solved?

Related

Unknown issue in PostgreSQL Function

I develop an application using VB6 and ODBC that fetch data from PostgreSQL function.
I used the function "F0006" to get information about item code, name, etc.
So far, my application runs smoothly on the current PC ( Windows 7 SP1 ). Because of the end of the support of Windows 7, we buy a new PC to replace the current that has Windows 10 installed.
We set up the same ODBC connection based on the currently running one and Connection success. But when we try to test our application to fetch the data, it seems can't find the function "F0006" and throw an unknown function message in the New PC ( Windows 10 ).
FYI, PostgreSQL is managed by others, and we don't have Admin DB access to it, and Active Directory is used in our network.
But if we try the same application in the current PC ( Windows 7 ) and other PC that using Windows 10 that has not configured to network AD, the application can get fetch data from the function.
Where could be the source of the problem?
Thanks

Remote Firebird 3 client cannot connect to the DB on my PC

For years I was unable to get my app, on a laptop on my LAN, to connect to the db on my PC.
I was getting the “rejected by” message.
One day I was trying again and viola! It was connected. I do not remember what I had done on my PC (Win 10 Pro, FB 3). Then my PC C drive crashed. After reinstalling all the parts needed I am back to the rejected message. The PC firewall (Win Defender) has a Firebird entry using port 3050. The connection string is “ServerName:c:\FBData\dbname.fdb”.
I am stumped, again. Does anyone have tips on what do to connect?

Flamerobin doesn't connect to Firebird database (msg: -902 isc_attach_database failed)

I'm studying Firebird 2.5 with FlameRobin 0.9, installed on a VM Virtualbox (with O.S. Win7 32bit PRO). The .fdb files are on the same disk of the Firebird machine and the FlameRobin program. The machine is not embedded and run as Superserver.
With FlameRobin I've created more than one.FDB file, created tables, triggers, generators, etc: all works fine.
I use Delphi7 to create executables that utilize the .fdb file.
Yesterday, during a proof, Delphi arise an error of "out of system resource": disconnect .FDB in Flamerobin, close Flamerobin (quit), close the VM; re-open the VM, re-open FlameRobin, re-register the .fdb... error:
IBPP:: SQLException; Context: Database::Connect; Message: SC_ATTACH_DATABASE
failed; SQL message: -902 unsuccessful execution caused by a system error
that precludes successful execution of subsequent statements. Unable to
complete network request to host LocalHost.
On the VM there is no antivirus and Windows firewall is disabled (on the host machine, Avast Internet Security is running).
I've haven't varied any parameters, all is developed as described.
In the .conf file, the Firebird machine can connect to all.
If I use a program compiled with Delphi, to insert or update some record in a Firebird table, all works fine, but FlameRobin doesn't want connect to Fdb.
In FlameRobin, the item "user manager" lists SYSDBA-masterkey and another user added by me 10 days ago.
On Internet, I've not found cases of the kind. Does it depend on Win7? And how? Can someone help me, to continue the work? Thanks for any suggestion that can be useful to understand the problem.

Unable to get password for Instance launched from AMI obtained from an instance after being shutdown from SysprepInstance.ps1 for AWS Windows 2016

I read through how to work with Ec2Launch and SysPrep with AWS Windows 2016. Unlike 2008 R2 or 2012 R2, 2016 does not use the EC2ConfigService, instead it has EC2Launch and bunch of PowerShell scripts which takes care of the EC2ConfigService's job.
I launched a windows instance call it "I1" from the community AMI - Windows_Server-2016-English-Full-Base-2017.03.15
I Scheduled InitializeInstace.ps1, command - powershell.exe -Command "C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\InitializeInstance.ps1 –Schedule"
I ran SysprepInstance.ps1, command - powershell.exe -Command "C:\ProgramData\Amazon\EC2-Windows\Launch\Scripts\SysprepInstance.ps1"
The instance goes from running state to stop state.
I take an AMI of the instance and launch another Instance "I2".
There are two issues I am facing:
Issue 1 - I am not able to RDP into instance I1, I tried the password from the console by decrypting it with my pem file. But that password works fine before I have run this SysprepInstance.ps1, but after running that script I get the error Password incorrect.
Issue 2 - Once my Instance I2 has passed the status checks and is running, when I try to connect to it and retrieve the password from the console, I am not able to retrieve it, it gives me the error:
Please wait at least 4 minutes after launching an instance before trying to retrieve the auto-generated password.
In case of Windows 2008 R2 or 2012 R2, we would change the config.xml file of EC2ConfigService and make EC2SetPassword to enabled, but I'm not understanding what am I supposed to do with Windows 2016 with EC2Launch.
Edit 1: Including the contents of LaunchConfig.json
{
"setComputerName": false,
"setWallpaper": true,
"addDnsSuffixList": true,
"extendBootVolumeSize": true,
"adminPasswordType": "Random",
"adminPassword": ""
}

Connecting to Windows Postgresql takes 10 seconds

I installed Postgresql 9.6 on Windows (x64), using the default installer.
I did this on 2 almost identical machines. On the first machine making a connection to localhost (for example by using psql) is instant, while on the other machine it takes more than 10 seconds.
I even copied the entire directory of the first machine, to make sure there is no difference, but the problem persists. The services are the same, and already running when Windows starts.
What on earth could cause this delay on that one machine?
Any way to identify what's going on?