Trying to find out if Windows Server 2012 has the same limitation on Raw Sockets as Windows 7. The MSDN documentation is unclear on this.
I think that is just because it hasn't been updated.
Related
I'd like to install MongoDB Community Edition on my computer, which has the 64-bit Windows 10 Home OS, but the system requirements say I need Windows Server 2008 to do it.
I don't think my computer has Windows Server 2008. Is there any way around this? For example, would it work for small-scale databases, or is it totally incompatible without Windows Server 2008?
If I absolutely can't use MongoDB, is there another non-relational database that would work with my system? (It would have to be free.)
I admit that the download site is a bit confusing.
But you can simply download the MSI and install it on your Windows 10 machine. A Windows Server version is not required for the community edition.
Disclaimer: I have it on a Pro (Windows 7 and 10, without Windows 2008 or any other server) edition, not on a Home edition, but I'm pretty sure that it will work in the local machine context)
We have a classic ASP application we just migrated from Windows 2008 R2 to Windows 2012 R2 Core.
Apparently Core versions of windows don't include cdosys or cdonts and thus our application can no longer send email.
Most of the advice I can find suggests using system.net.mail for sending email which of course is a .NET technology and we're using classic ASP.
We do have .NET on our system but I'm not sure if classic ASP could talk to a .NET page for sending email?
Besides using a 3rd party COM utility like Persits ASPEmail are there any native ways of working around this?
We do NOT want to convert the server core instance to the full version of windows. That's killing an ant with a bazooka. This is only impacting two places in our code and everything else works just fine on core.
Unfortunately, CDONTS was superseded by CDOSYS some time ago. When migrating from Windows Server 2008 to Windows Server 2012 I had this exact same issue, but managed to find a fix.
It involves taking a copy of the cdonts.dll file from the Windows Server 2008 Server and adding it to the Windows Server 2012 server then registering it with the relevant COM subsystem without any need to change code or install a 3rd Party library.
Hopefully the same method will work with Core but I haven't tested it.
Does anybody know how to get export to XLSX support for SQL Server 2008 R2 Reporting Services without upgrading to SQL Server 2012 or using any 3rd party tools?
Apart from developing your own render? Nope. I haven't been able to find ANY information on that by the way.
Apart from going to SQL Server 2012 (a 3rd party renderer may be more cost effective) you could develop your own ASP.Net app while using EPPlus that would link from the report. This stackoverflow post may help start you off with the code.
Hello I have installed management studio 2005(x64) alse I have microsoft sql server 2012 in my pc. But cant connect server due to dont know server name. (if sql server 2008 express were in my pc, default servername would be "./sqlexpress")
How can I connect server in my own pc ? And also I wanted to know;
Should I use another management studio ? can there be a problem use ms2005 with sqlserver 2012 ? Do you recemmond other studio ? (with exp. reason please)
Thank you anyone who just feel to help.
At least one of them must be a named instance. So, open the SQL Server 2012 version of SQL Server Configuration Manager, and see what the services say (and make sure the one you want to connect to is started - you can right-click to do so). Mine are all named instances:
So, if I wanted to connect to the SQL Server 2008 SP3 instance, I would use any of the following to connect:
.\SQL2008SP3
LOCALHOST\SQL2008SP3
(local)\SQL2008SP3
YOURMACHINENAME\SQL2008SP3
127.0.0.1\SQL2008SP3
The exception is if the subtext has (MSSQLSERVER) - this is a default instance rather than a named instance. In that case you would just connect to YOURMACHINENAME or ..
Also, no, you should not use Management Studio 2005 to manage SQL Server 2012 instances. In fact I think the above Configuration Manager won't show your 2012 instance. So before you do anything, you should uninstall the 2005 version of Management Studio, and go get the 2012 SP2 version here:
http://www.microsoft.com/en-us/download/details.aspx?id=43351
Click Download, the file you want is SQLManagementStudio_x64_ENU.exe. The nice thing about this version in 2012 SP1 is that it's the first version of SSMS Express that is actually fully functional and license free. Previously you had to live with limitations like no SQL Server Agent management, well those restrictions are now all gone.
(When you instal the client tools, this should also give you a new version of Configuration Manager, if your previous installation of SQL Server 2012 did not provide that for some reason.)
I have two questions...
Could I create a complete portal for Internet with WSS 3.0 or MOSS is necessary for that?
I wanted to know if it is possible to install WSS 3.0 on Windows Server 2008 R2 or Windows Server 2003 is the only possibility for this version of Sharepoint.
The answer to your first question really depends on your definition of portal and how broad it is. It is possible to have an efficient intranet solution with WSS without full blown SharePoint. Microsoft offers a lot of templates too, for specific site types.
To your second question, yes you can install WSS 3.0 on 2008 R2, but you will need to apply the latest service packs.