Windows Service Printing Behaviour - windows-services

Alright, I was tasked to develop a Windows Service that listens to a directory for files that are dropped in it, read them, delete them and print out a report.
I installed the service on my work laptop (Win 7 x86) and a test machine (XP x86) under a User account at first. It would do everything as it should except the print the report. No errors, nothing. Then I made it run under Local System and it produced a "No printers found" exception.
Converting the app to a Console Application and running on these machines gave the desired result. OK, so now I was assuming that there are security "stuff" involved.
Then I installed the service on a Server 2008 x64 machine (under Local System) and it just worked. Can anybody explain to me why this is happening? Why does the service allow printing from Server OS but not from a Desktop OS or am I missing something very obvious?

I'm guessing that the printers are installed locally on the server but installed as network printers on the desktop. Local System only have access to local printers.

Related

RDP printer redirection doesn't work from Windows computer, but works from Mac

I have 1 Mac and 1 Windows.
From the Mac, using Microsoft RDP, I connect to a Windows Server 2019 and I can see my local printer (redirected) in the Windows server. I can print without any problem.
From the Windows, using RDP, I connect do the same Windows server and I don't see my local printer.
Notes:
I configured both RDP to enable local resources (printer)
I didn't install the printer driver in the server. Since I can use it from the Mac, I conclude that I don't need to install it in the server.
Any idea why I can't see the local printer from the Windows computer and how to fix it?
Thanks!

Firebird database connection by FireDAC after Windows 10 update

I have some delphi applications with connection to Firebird database by FireDAC technology. It works fine, but after Windows 10 update 1803, cannot connect to database when I call application stored in network path (example: \comp1\share\myapp.exe or Q:\myapp.exe, Q: is mapped server path). Error status is 335544721 with illegal parameter.
The same build of application stored on local path works fine. Can anybody help Me?
I've got the same problem!! The reason is the Firebird version 1.5.x (maybe 2.5 too?). Windows Update 1803 blocks the communication between client and server. The only solution is to migrate to Firebird 3.0.x (or to uninstall the update - not a really good option).
I had the same problem with my delphi application I developed a couple years ago, after an update to windows 10 in one of my machines it suddenly drops the connection to the firebird server (2.50 in superserver mode) installed on a windows 7 host, while my other hosts (win xp, win 2003, win 7 and 8.1) connects normally, when I ping or telnet to the server adresse from win10 (telnet 192.168.1.X 3050) the connection establishes, I have tried everything like enabling Smbv1 and disabling v2 and v3, run it under a VM (win 7) machine inside win10 I was surprised to not being able to connect too, then I realised that it wasn't a network hardware configuration problem, but for unexplained reasons WINDOWS DEFENDER, I just disabled it and then my app was able to connect.
And don't rely on firebird's returned error messages they don't discribe the real issue, and can mislead you.
I forgot to mention that I did enabled some services before disabling win defender, wich were disabled after windows update 1803:
Set both Function Discovery Services to Automatic and Start Them
SSDP Discovery set to automatic.
UPnP Device Host set to automatic.

The Ifxoledbc provider is not registered on the local machine

I have installed the "informix" client SDK in my 64bit windows 7.in the C# net , while i am trying to debug the datalayer project thru the unit test something retrieve the information from the database.But i am getting the this one error " The Ifxoledbc provider is not registered on the local machine " . and also i have registered the "ifxoledbc.dll" by command prompt. but is not working. And i have tested in the 32 bit machine it is working. only problem in the 64bit machine.

Error attaching debugger to IIS worker process

I have a strange problem in that my MVC Azure application is running/debugging on my desktop but not my laptop. On the laptop I get an error
Error attaching debugger to IIS worker process
However I don't get the problem when running/debugging a simpler/smaller MVC Azure project on the laptop. The only difference between the laptop and desktop is that the laptop is running Windows 8. A prior version of the application did run on the laptop but has suddenly stopped working and I can't trace back why.
Has anyone got any ideas as to what the cause could be.
Can you use TcpView(http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx) to see if there is a port conflict on the machine with the port used by IIS Express

Can't view Rails app on Windows7 via mac local address

My app runs on localhost:3000 on my mac
My mac has its own local address eee.local
Other computers in the office, including other windows machines
can connect to eee.local:3000 and use the the rails app.
However we had once case where one person's windows7 machine
could not connect. I brought a brand new windows7 machine for
IE testing purposes and it doesn't connect either.
I tried turning of the firewall and that doesn't work.
I tried using the ip instead eg. 192.160.0.3:3000 but that doesn't work.
I'm not really sure how else to check, or search for this problem
Anything Im overlooking?
Another thing to try is to install iTunes. Sounds silly at first but installing iTunes gives your Windows machine Bonjour service discovery (enabled by default on Macs and Ubuntu desktops) which would let you resolve .local addresses.
Accessing via the IP really should have worked but if you've already turned off firewalls and the machines are on the same network then enabling Bonjour (by installing iTunes) is worth a shot.
Is the other Windows machine on a different subnet? That could cause the issue.
You need to tell the web server to listen on all interfaces like so:
./script/server 0.0.0.0:3000

Resources