I've doing a project using the azure servers for a little bit now. After a month my subscription ended, and I had to get a new one, with a new acc (school project, so im too poor to get the normal sub). Now after setting everything up, and trying to connect to my new databasa (which to its address has added 2 at the end), my VS still tried to log me into the old server.
I've already tried to delete the whole project, copying it anew from gitlab, deleting cache from my pc, restarting it, and adding/removing connections in VS, but when the error occurs.
I'm getting the "Login failed for user X", when I'm checking the logs of the error, I see that it still tries to connect to the old server.
Any ideas what could cause it to keep logging to the old server?
I'm using in this part of the program only 1 Connection string, which I have changed to the proper one.
Related
A development server I was using ran low on disk space causing the system to crash. When I checked the replica set cluster it came back 1 node was unreachable. I removed the bad nodes and forced config. I went home for the day the next day I came back, and the status was not good saying unreachable for one of the nodes. I worked on something else and later that day it when I checked rs.status it came back primary and secondary. I then added the 3rd node back that ran out of space. Now I can connect to each node and the data looks ok, but I cannot connect to the replica set group in php/nodejs or stuido3t. When i use the group connect it returns auth invalid but I can use that same auth for each node.
Any ideas what could be going on and how to fix it?
What I needed to do was take down the 3 services making up the replica docker swarm. I redeployed it using my scripts with auth turned on. It I checked the replica status and it returns host unreachable, I checked it a few hours later that day it came back online. I was unable to get the replica set back online with rs.add / remove, but I did get it back up and running by recreating the services.
I have a ClickOnce app in .NET 4.0;
How can i prevent users from copying the whole installation directory from one machine to another?
I don't need a solution that can't be hacked(if there's one), but i need one to stop everyday users from doing this;
I already tried the following:
Store the MAC address when the app is installed, and try to match it every time the app starts - this didn't work because users might use wired or wireless connections;
Match the HDD serial key - it doesn't work for WinXP;
Some extra info that might help:
I'm keeping track of my customers in a DB: when a customer requests the product, i add a new record ; When they run the app for the first time, the app asks for the ProdId, and changes the status so they can't install it again using the same ProdId;
I am scraping a site for data every 50-90 seconds randomly using a C# console application running on .net 4.5. There are couple of values I am posting to the site and based off the returned value I kick off some other process. The problem is after say about a thousand hits or so I get what looks like a DNS error. I am trying to sort out what the source of the problem is first, before trying to fix it. Here below are some of the errors I see in my logs:
The remote name could not be resolved
Unable to connect to the remote server
Unexpected character encountered while parsing value <. Path '',
line 0, position 0.
Unable to read data from the transport connection An existing
connection was forcibly closed by the remote host.
Unable to read data from the transport connection An established
connection was aborted by the software in your host machine.
About 60% of the time I have got the first error. The remaining 40% is divided between the rest of the errors listed above.Are these issues caused by the website I am scraping or by the DNS servers on my end or something else? For all practical purposes the website I am scraping is ok with it as long as I keep the interval between automated hits above 45 seconds which I am doing. The data I am downloading is on an average about 30KB per hit. Please help me understand what could be going wrong and what things I could try to fix this.
I'd say you're running against an automated system designed to protect the site against a DDoS attack http://en.wikipedia.org/wiki/Denial-of-service_attack.
It's seeing that your same IP address is hitting it repeatedly in a short space of time and is simply blocking your resolution of the eventual server.
So, I used the updater in CF Admin to apply the latest patch (14) to CF10. Afterwards, I rebuilt my web server connections. This is a process I've done dozens of times. However, this time around I've lost the ability to get to my CF Administrator....but all my sites are running just fine! I just can't access the Administrator! I've removed/recreated the connectors and restarted IIS/CF 3 times. Same thing.
Everything about this server was running fine up to now. It is Win 2008/IIS7
I'm getting the dreaded IIS HTTP Error 500.0 - Internal Server Error:
Module IsapiModule
Notification ExecuteRequestHandler
Handler ISAPI-dll
Error Code 0x00000000
Requested URL http://thewebsiteimtalkingabout.com:80/jakarta/isapi_redirect.dll
Physical Path D:\My_Web_Sites\config\wsconfig\2\isapi_redirect.dll
Logon Method Anonymous
Logon User Anonymous
I have 2 other identical servers that I have yet to update so they continue to run fine. I've been referencing each of them to see if there were some permissions or other oddball changes. Can't find anything.
Any ideas?
I'm playing around with sample code that makes use of live tiles, and when it tries to create the TileUpdater instance via:
TileUpdateManager.CreateTileUpdaterForApplication()
It immediately crashes with the following message:
The notification platform is unavailable. (Exception from HRESULT: 0x803E0105)
This happens when deploying to both the simulator and the local machine.
EDIT
While digging through event logs, I stumbled across a few of these:
The Windows Notification platform has failed initialization. Notifications will not work until after a restart.
I've restarted a bunch of of times already though.