Writing to a text file(log file) on remote server in c# - winforms

My intention is create a log file on a remote server from a standalone app(Winforms). Also, will require to edit/read it at times from the application.
Please provide your expert advice and insights.
Thanks in advance.

Related

Sending generated XML file via SFTP

I've generated an XML file using tsql and I'm wondering if there's any way to send it to a remote server via SFTP. Is there any way to do it without external software? What is the best approach to solve this problem?
Any tips will be greatly appreciated
edit:
I forgot to mention that I need a new copy of the file on the server everyday, so...
I need to generate a new file everyday and then replace the old file on the remote server.
I've tried setting up a JOB that runs a SSIS package and it partly does the job, but the standard package doesn't support SFTP. :(
Managed to solve it using WinSCP & command line task in SSIS as suggested by user
Panagiotis Kanavos

DB2 and MQ integration

I'm trying to integrate DB2 and IBM MQ together. My goal is to transfer chosen information from database on one system to database on other system through MQ. I know that there is this Q replication function, but I wanted to use single MQ commands available in DB2. I'm using DB2 Advanced Enterprise Server version 11.1 and MQ version 9 on Windows 7 OS.
I went through the DB2 documentation on IBM knowledge base and found information about MQListener command (db2mqlsn), enable_MQFunctionscommand and so on. Problem is, that I can't see those commands in my DB2 installation folder at all. The db2mqlsn utility is supposed to be located in the DB2PATH\sqllib\bin directory, but for me, it is not. I tried to search the word "mq" through the whole SQLLIB directory with windows search but it didn't found nothing much. There's a screenshot with search results.
Can someone please help me with this?
Thank you very much in advance for any help.
Martist

Filezilla/Wildfly server deployment error (Possible database dependencies)

This is my first time on here. I am having an issue deploying a java application I made on myEclipse. I am using Filezilla to host my Wildfly 9.0.2 test server. I exported my project to a .war file and upon dragging it into the test server I am met with a deployment.failed. Upon viewing the file in Notepad it declares "Services with missing/unavailable dependencies". one such error can be seen below:
[ "jboss.naming.context.java.module.myproject.myproject.env.common.jdbc.database_connection is missing [jboss.naming.context.java.database.connection] "
There are five of these similar errors and all point to a diffferent database connection of some type that I am not using within my project. I understand the issue but I do not know where these dependencies are declared and how I can go about removing them.
Any help will be greatly appreciated.
Kind Regards,
Paul
Creating the WAR file will use the project's deployment assembly (assuming you're using MyEclipse 2013 or later). Right click on the project and select Properties. Then go to the MyEclipse/Deployment Assembly page. This will have all of the files that are added to the deployment (or to the WAR file).
However, the message seems to suggest that a project is using a database connection which can't be found when running on the server. A first thought was that you're using the inbuilt Derby database but don't have that running when you run on Wildfly.But you say that you're not using a database. Also, I'm not familiar with how Filezilla can host a J2EE server - I thought Filezilla was an FTP client and server solution. Perhaps you could give more details, if this answer doesn't help.

SQL Server error when opening the exe that uses the database

I'm not a programmer or anything, I bought a software a couple of years ago and I formatted the computer, but when I called the software company that made the software for me, all their phone numbers aren't working, I think they went out of business or something.
I have the exe and everything, and a SQL Server database .mdf and .ldf, I attach the database to SQL Server through Management Studio, after I install it, but when I open the exe file I get a SQL Server error I will attach a picture of the error in the question, the software was fine before, but I don't know what I'm doing wrong should I do something else beside just attaching the database, forgive me, I'm not very knowledgeable when it comes to programming stuff, can anyone please help me ...
Thank you so much
this is the error message snapshot
This is the content of my config file
and also there is a text file named 1 i don't know if that's relevant or not.
This is the content of that text file
(Data Source=.\SA;AttachDbFilename=C:\Users\Samar\Documents\DB_Center.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True)
In the same folder as the application, look for a .config file (likely to have the same name as the executable).
In this config file should be settings, one of which might be the pointer to a database (called a connection string), which you will want to change to point to your database you just attached.
The error message would indicate that the instance of SQL Server the application is looking for cannot be found...

Sharepoint Server: Step by step guide to moving data to sql server

I have a sharepoint server used for multiple clients which I installed on my internal server with default settings. Now I want to move this to a website host instead.
I need to transfer all this data from the integrated SP server to a SQL server, but I can't find a step by step guide to achieve this. I don't even know where the data is currently stored (I assume in the local filesystem where sharepoint is current running) how to export and then reimport and then tie this to the new Sharpoint site once it's on the new hosting environment.
Does anyone have a step by step guide on how to achieve this? I can't seem to find a solution that works by using google.
Thanks in advance
Stu
Ok, here's a starting point:
Ask your hosting provider what format(s) they support.
And then work from there...
More helpfully, take a look at using the Backup-SPSite cmdlet rather than thinking at the SQL level. You can back up a single site/web and then use Restore-SPSite to put it somewhere else.

Resources