At CodeProject we spend an awful lot of time playing with room heaters, or as others like to call them, "servers". Over the years we've seen it all, some of it smoking, most of it usually working just nicely until something happens.
What that something is can be hard to find so we've created a quiet place for those battle scarred and frustrated to get a little help.
I have installed 64 bit SVN Subversion both on server and client machine. Now, the problem is how should I access the server? I read a lot, but there are no clear cut mentioning what should be done for accessing the Repo Browser URL.
What I have done is,
1. Installed 64 bit Tortoise SVN version both in server (eg: 22.214.171.124) and client machine (eg: 126.96.36.199)
2. Created new folders in E drive of server, E:\svn\NewRepository.
3. Then, open command prompt, and run the command
svnadmin create --fs-type fsfs NewRepository
This ran successfully and created some configuration files in E drive.
4. I have created manually folders like branch, trunk and tag in E:\svn\NewRepository folder.
Now, how will I access this folders from my client machine(188.8.131.52)? should i start with http:// or svn://. Please help.
Try installing VisualSVN. This will allow you to access your SVN repos via the browser.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
So as not to be seen as self-promoting with a URL, please note that the domain names used here are obviously faked. I'm really just after some logical explanation of the situation described below.
My main company website, sample.com is hosted. I was checking the error logs and found quite a few where the referrer was listed as someothername.com. Out of curiosity, I pasted the referrer (someothername.com) into a browser and was greeted with my company's homepage! I ran a ping on someothername.com and it shows my dedicated IP address. I also ran a ping on my sample.com and it also shows my dedicated IP address. WTF? How can another domain name point to my dedicated IP address? Is it possible that somebody screwed up a DSN record with their registrar? I just did a lookup on the someothername.com and see that they changed their records more than a few months back, but then, it seems like they might have noticed it by now.
Now, it just so happens that for the past few months, certain web resources at my hosted site have been acting flaky...static xml files become unavailable, then a few seconds later, it's fine...images failing to load with the same behavior, a quick refresh and they now show up. It doesn't seem to me like the first thing would have anything to do with these problems, but the timing does seem weird.
Having multiple domain names resolving to the same IP address is perfectly reasonable. The server typically uses the "host" header to determine which site hosted on that address to route the request to, usually with a fall-back site for unrecognised hosts.
However, if the other site isn't associated with your company, and you're not using shared hosting, it sounds like someone's made a mistake with their DNS records. You could try running a "whois" query on the other domain to see if you can contact the owners to let them know.
Having a second domain pointing to your IP address wouldn't cause any technical problems. If you're worried about your company's site appearing for requests to the other domain, you could add a dummy site to your server with the specific host header, which would serve up a static HTML page notifying visitors of the mistake.
Richard, Thanks for the quick answer! I looked through the account information for my web host and it does not mention 'shared' anywhere. I think the issue lies with an incorrect DNS record and looking at my web stats (hits almost doubled) it all started back in August...yep, it has been at least half a year since I checked web stats or error logs!
I suppose I should be a nice guy and at least inform my web host...maybe it's something they have to sort out, or at the very least they can tell the owner of the other domain about the problem. Thanks again!
I currently have a .NET 4.0 website successfully running on Windows Server 2008. It utilises SQL Compact 4.0 which resides in the App_Data folder. The database dlls reside in the bin folder.
I am moving to a new web host company and I want to test this on Windows 2012, ultimately with a view to moving to .NET 4.5 and, later, SQL Server.
My starting point was to move across all of my website folders, including a test database and SQLCE dlls and test the site.
Unfortunately I get the following error message when loading the home page for the first time. "Unable to find the requested .Net Framework Data Provider. It may not be installed. "
The first part of the trace states:
[ArgumentException: Unable to find the requested .Net Framework Data Provider. It may not be installed.]
System.Data.Common.DbProviderFactories.GetFactory(String providerInvariantName) +1480919
System.Data.EntityClient.EntityConnection.GetFactory(String providerString) +26
I am still learning .NET and server environment so please be kind. I have researched for answers this morning but it seems to raise more questions than answers for me.
Given my setup and the errors shown is there a best place to look/check first?
That suggests that you do not have SQLCE installed on the new server, even though you have copied the DLLs. Some products are required to have the installation process run in order to set up links and registration information.
o A demonstration of 3 laptop based multi-hop wireless network. If laptop 2 is turned off, the source will NOT be able to communicate with laptop 3. As soon as laptop 2 is turned on again, laptop 1 will be able communicate with laptop 3 again.
with out any internet connection.
Last Visit: 31-Dec-99 19:00 Last Update: 5-Mar-15 12:05