can't print from remote desktop on Windows Server 2003 R2 - printing

We have a c# document designer project. We can print documents with this program for most of the customers.
But we faced a problem for the customers which has Windows Server 2003 R2 OS.
I connect to customer pc via remote desktop connection,
Once I try to print from program it doesn't give any errors but it doesn't print any page either!
But when I send test page from the printer it sends the document without problem.
We did similar problem for Windows server 2008 r2 ,
and it was about group policy settings and the problem is solved,
I wonder if it is similar to that problem.

Related

Soap-server responds with error 12030 after requests over HTTPS

My Delphi 10.4 application uses a HTTPRIO-component to communicates with SOAP REST Server over HTTPS.
It is installed on more then 100 PC's, and it works fine almost everywhere.
However, I now have 2 clients that get the following error:
"Error sending data: (12030). De verbinding met de server is niet normaal beƫindigd"
(--> The connection to the server did not end normally )
The user has a Windows 7 Home Premium machine (I have Windows 10 Pro).
Firewall was disabled.
If I copy the complete application-dirctory with all the dll's to my machine everything works fine.
Where should I start looking for a solution?
Which properties of the HTTPRIO-component could have an effect on this behaviour? Or which dll's?
I checked the article Peter Wolf suggested but without succes. (The register-settings should be OK). All the registers are present with the right values, but the windows update could not be installed. Also downloading the stand-alone update KB3140245 fails. It juist says "failed".
any hints are welcome!
kind regards,
Dirk Janssens

TFS246017: Team Foundation Server could not connect to the database

While attempting Branch operation from within VS I get the error message TFS246017: Team Foundation Server could not connect to the database. Verify that the instance is specified correctly, that the server that is hosting the database is operational, and that network problems are not blocking communication with the server. (The error message box looks like the one in this question).
I logged on to the TFS virtual machine. In event viewer I see a warnning with with the same message as above + Process Name: w3wp, User: domain\MyUser. The IIS TFS site is started.
I opened the TFS console on the TFS machine using both domain\MyUser and domain\tfssetup (this is the user running the Visual Studio Team Foundation Background Job agent service), the console opens successfully. Both users appear in the Administration Console Users list. I did reapply account for both users. I also did update password for domain\MyUser. It shows a connection string with Datasource and Initial Catalog. I logged in to the DB machine, opened SQLSERVER users: the tfssetup user is there with sysadmin and owner of relevant instances. I also added the domain\MyUser and added admin privileges (but the error persists).
I also installed SSMS on TFS machine & was able to connect to DB server using both domain\MyUser and domain\tfssetup and view tables.
This error did not happen in the past. This error didn't happen when branching a different location in the source control ($/Project1/Main vs $/Project2/Main) beforehand. The Source Control Explorer appears to show OK (so TFS is working). Using Visual Studio 2013. TFS 2017. AFAIK Virtual Machines were not moved, IP address were not changed. Using vSphere it seems there is enough disk space for both TFS and DB machines. The error appears after ~4 seconds.
What else can be tried?
Looking in the TFS SQLSERVER log there was a "SERVER ASSERTION" error and this was the cause for the TFS generic error.
In my case the error was very similiar to the one here. CHECKDB and updating to the latest service pack didn't help. What helped was changing the recovery mode to full as recommended in that thread.

Citrix printing - 2 of many thin client workstations cannot print

We have a application deployed in a Citrix environment. Many workstations can print to the Citrix print server fine via our application, but 2 cannot (this is limited to our application ie MS Word document prints fine). Of the many workstations, 2 with issues are on the same host as other workstations without issues. There are no printing issues with our application on other workstations. The application is published from the same host. Not having a Citrix background not sure how to go about troubleshooting this.
Check that Citrix host (on which users have issues) have the same policies applied comparing to others. In Citrix XenApp 6.0 and higher run AppCenter console and inspect policies and WorkerGroups they applied on.
Secondly, check Citrix host Windows Event Log for printing errors or printer creation errors.
And lastly check print server for received print jobs and their status.

Team Foundation Server 2012 broken web access - Error TF400893

I have installed TFS 2012 Express on my computer but I can't get TFS web access portal to work. If I try to view a page with work items I get error:
TF400893: Team Foundation Server services are not available.
This is most likely caused by a network error.
Please check your connection and try again.
It's weird because other parts of the TFS web portal works (e.g. source) so I don't think it's network error. If I connect to the TFS server from Visual Studio everything is working, so I suppose TFS service is running.
I tried to reinstall TFS, but it didn't help :-(
Any ideas what can be wrong?
Try an other browser. I have used Opera and got the error. Using IE should work.
Try changing the account from Applicaiton Tier on TFS Administration Console to your current domain and user info. The default value is NT AUTHORITY.
You should check for any firewalls or other IPS devices between the browser and the application tier for SQL injection attack rules. WIQL being sent from the browser in the AJAX request looks far too much like regular SQL so gets canned by such rules.
As we were experiencing this issue where I work, I decided to take a network packet capture of the browser traffic on a machine experiencing the problem. This yielded a whole bunch of TCP retransmits on the packet containing the plain-text WIQL. Upon presenting this evidence to the company's network team, they located the offending IPS rule which was triggering on these packets, disabled it for packets targeting the TFS Application tier and the problem was solved.
I just got the same error while adding a comment to a work item which included a SQL Statement to drop some tables.
After changing my language to not include explicit T-SQL "DROP TABLE" syntax, I was able to add the comment. My guess is something trying to prevent SQL injection.

SQL Server 2008 OLE DB CONNECTION FAILS FROM OUTSIDE

I have a working SQL Server 2008 R2 Express installed on a Windows 2008 server on a cloud machine. All type of connections (ado.net, nhibernate etc.) from several client applications works fine except the OLEDB one. SQL Native Client also works fine.
When I tried to connect from the server locally and as a data source write the instance name, everything was OK. But from outside, I had the problem or also if I write wan ip or dns I had the problem also from local.
-- works perfect from everywhere
Provider=SQLNCLI10;Data Source=mntek.no-ip.org;User ID=xxx;Password=xxx;
-- does not work from anywhere
Provider=SQLOLEDB.1;Data Source=mntek.no-ip.org;User ID=xxx;Password=xxx;
-- works only from local
Provider=SQLOLEDB.1;Data Source=flz001\sqlexpress;User ID=xxx;Password=xxx;
Error: [DBNETLIB][ConnectionOpen (Invalid Instance()).Invalid
connection.
-- works perfect with ado.net
Data Source=mntek.no-ip.org;User ID=xxx;Password=xxx
Some other client applications (not mine) was written with oledb connection so I need them to connect the db with oledb provider.
Any ideas?
Regards,
Mert
It has been a while since this was asked, but I am currently working through an issue related to OLE DB and SQL Server that sounds possibly related.
I found that, even though the server was using the default port (1433), I still had to explicitly specify it in the UDL connection string like this:
Provider=SQLOLEDB.1;User ID=USER;Data Source=IP,1433
I've asked why that might be necessary here:
Why might SQL Server 2008 OLE DB UDL require port 1433 explicitly specified?
Maybe try that and see if it helps.

Resources