We are using a Server 2003 domain. I've found the instructions for installing the Active Directory snapin for Server 2012 and earlier: http://technet.microsoft.com/en-us/library/cc732110.aspx. However the DLL it mentions (schmmgmt.dll) isn't present on our 2012 R2 server.
I've found information on 2012 R2 AD Administration Centre, but as our domain is 2003 based I presume none of that is relevant.
Can I run the AD snap-in on this server, or do I have to use an older server?
We're using some third party software which runs as a service on one computer, accessing an IIS resource on second computer. The second computer isn't in the same domain as the first, and there's a firewall directly between them.
Both servers are Windows 2003, running IIS6.
The service fails to do what it wants because it isn't authorised to access the IIS resource (HTTP error 401). The resource cannot be run anonymously (and complains if I set IIS to work like that) and uses windows authentication. The software assumes that both machines are in the same domain.
Without adding the second computer to the same domain as the first (which must be possible, but involves fiddling around with routing), can I make it so that the service can access the resource?
I've tried to find ways of adding the first computer as an authorised user on the second one, but I can't.
I'm using a third party app build on asp.net. It runs on Server 2003/IIS6. I changed the way that app pools are recycled. After this happened the third party application stopped working. Specifically URLs that didn't correspond to files in the third party program directory returned 404 errors.
(I'm not that up to speed on how asp.net works.) What I mean is that if I go to a URL like example.com/thirdparty/page.aspx, when there is a page.aspx file in the third party program directory, the page works. If I go to example.com/thirdparty/stylesheet6.css, when there is no stylesheet6.css file in the program directory, I get a 404 error.
It stopped working after I did this change to the app pools, though I could have changed some other aspect of the IIS configuration by mistake. I've put those app pool settings back how I think they were, but that hasn't fixed it.
The company for this third party software suggests uninstalls and reinstalls and restoring from backup (basically they haven't a clue why it's broken) but I'd like to undo what damage I did because that might be easier.
What sort of changes to IIS configuration could I have done that would break these sort of URLs?
I wanted to physically move the files associated with a database in SQLServer 2005 Express. I backed up the database, detached the database, copied the files to a different drive, and then reattached. When I reattached I changed the filename at the top half of the screen, but didn't notice that the filename used in the bottom half of the screen (for the individual files) had the old filename.
Since then whenever I've started up the server and the SQLServer service I get a message saying that it is recovering, even an hour later.
I would like to detach the database, but I can't do that. I can stop SQLServer and rename the files, but then it just gives an error message about not finding the files.
There are messages in the application log
Process 51:0:0 (0xe94) Worker 0x03A800E8 appears to be non-yielding on Scheduler 0. Thread creation time: 12897060171040. Approx Thread CPU Used: kernel 0 ms, user 0 ms. Process Utilization 0%%. System Idle 98%%. Interval: 1750921 ms.
How do I get rid of my database entry in the management studio so I can either reattach it properly, or restore from backup?