Is Enterprise Library 4.1 and server 2008 sp2 compatible? I can't find specifics on this - windows-server-2008

What I thought would be an easy google turned up no results. I'm trying to find out if Enterprise Library 4.1 is compatible with Windows Server 2008 SP2.
The system requirements say its compatible with Server 2008, but there is no mention of the service pack. Does anyone know definitively if these two are compatible?
Thank you for your time.

Typically compatibilities will list the minimum requirements; compatible with "Windows Server 2008" would include it and subsequent service packs (unless explicitly indicated otherwise). Keep in mind EL 4.1 was released almost a year before 2k8 SP2 was.

Does anyone know definitively if these two are compatible?
I guess it would depend on how you define "definitively" and "compatible". ;)
Do you want to know if Enterprise Library will run under Windows 2008 Server SP2? I don't believe that it was formally tested against that version (typically testing will go back two OS releases and SP2 didn't come out until the year after Enterprise Library was released) but it should work on later OS versions. For example, I have used version 4.1 with Windows 7.

Related

Sql Server 2005 Not Compatible with Windows 10

I had SQL Server 2005 working when I upgraded to Windows 10. Now it won't work. I read that it is not compatible with Windows 8, according to Microsoft. Windows 10 is but the matured version of Windows 8, to me. Is there any way I can get SQL Server 2005 to work with Windows 10?
Have you tried to apply / re-apply SP4? I'm not saying it will work but it works in Windows 8. Not sure what you upgraded from.
This may help .. https://www.youtube.com/watch?v=cj859zcWhEM
uninstall inFlow before upgrading to Windows 10 and then re-install (because of compatibility issues with SQL Server 2005). This is pretty easy and can be done from the START menu by searching “Programs and Features” and once open, choosing to uninstall inFlow Inventory.
Not sure which version of SQL you’re using? You can check the version of SQL Server through the START menu by searching “Programs and Features.” In that window, look for “Microsoft SQL Server” and check the version (it will either be 2005 or 2008 R2). If you’re in 2008 R2 or 2012 you’re golden, no extra steps required).
So bottom line: if you’re planning to take advantage of the upgrade from Windows 7 to Windows 10 that’s great, but take a few minutes to double check your SQL Server version (as noted above) before you upgrade. Most of us won’t be affected but if you don’t, the upgrade could break inFlow and that’s no fun at all!

Installing ArangoDB on Windows Server 2008

I'm having difficulty getting Arango 1.4.9 working on my Windows 2008 Standard (SP2) server. It's a fresh install. When I try to start Arango Server I receive this message:
The procedure entry point TryAcquireSRWLockExclusive could not be located in the dynamic link library KERNEL32.dll
I have tried both the 64bit and 32bit versions. I have run the installer as an administrator and vice versa. Any ideas?
TryAcquireSRWLockExclusive is from a newer Windows API. The Windows 2008r2 build uses newer Windows API features such as SRW (Slim/Reader Writer) API to improve performance. These are not available in Windows Server 2008.
I assume that you must recompile for Windows 2008 or ask for a suitable binary in the support forum (https://groups.google.com/forum/#!forum/arangodb).

Windows Embedded CE 6,0 Installation

I need to install the Windows Embedded CE 6.0 package that works with Visual Studio 2005 because I need to upgrade an old driver that runs under CE 6.0. I understand that Microsoft does not support this CE package any longer and, in fact, they no longer provide the installation files for CE 6.0
Where can I get the Windows Embedded CE 6.0 installation files??? They can be in an ISO file or whatever format is available.
I'm not sure if I understood your question right. By package you mean BSP (Board Support Package)?
If you are new to CE, you will need a brief explanation before get started.
The Windows CE 6.0 itself doesn't have exactly installation files. The runtime system is built through a toolkit called Platform Builder. As "input" for platform builder, you select which components your runtime image will have (including drivers) and as "output" is created a binary image of your system. You may transfer your runtime image to the device with a few different methods.
Regarding drivers, they usually are distributed through BSPs. BSPs are built by the device maker so you could check the device manufacturer site for BSPs, but you can give a try first on the supported packages search (http://www.microsoft.com/windowsembedded/en-us/downloads/board-support-packages-for-windows-embedded.aspx).
You can get the Platform Builder Toolkit with a Microsoft Authorized Embedded Distributor or through a MSDN subscription (http://www.microsoft.com/windowsembedded/en-us/evaluate/how-to-buy-windows-embedded-compact-7.aspx). The Platform Builder for CE6 comes with a copy of VS2005.
Windows CE6 is currently at R3 (released in 2009) and it is supported (mainstream support) at least until 2014 (http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-roadmap.aspx).
I strongly recommend you to take a look at least on http://www.microsoft.com/windowsembedded/en-us/develop/windows-embedded-ce-6-for-developers-overview.aspx. I'm not much experienced with CE6 (few months) but my personal experience says that it's a long path to code drivers for CE.

Do I need to install SQL Server 2008 SP1 on the management studio express?

Basic Question -
I have installed SQL Server Express 2008 with integrated SP1. This is the database engine alone.
I realise now that I also need the express studio in order to perform a few tasks. I have installed it, however I know that it was the original installer from before SP1 was released.
I have tried it and it appears to work fine but should I install SP1 / could something unforeseen happen in the future?
Some background! -
I wrote out the question and just realised that people probably don't care, so I just summed it up above!
After reading many different sites and guides, the install order for Visual Studio 2008 really confused me.
I really wanted to install SQL Server Express 2008 with advanced services, however on my other machine I had so many problems with it not being detected with Visual Studio, I just wanted an easy life!
I found the download from Microsoft that had SQL Server Express 2008 with SP1 integrated, however it was only the basic engine without any addons. (At the end of the day, as much as I wouldn't mind reporting services, I doubt I will need to use it any time soon).
I installed this, and after applying the hotfix (for x64 sql) my Visual studio can detect and use it no problem.
Now, I want to use Management Studio Express to write a few SQL scripts. The installer is obviously the original one. It seems to work fine, but I cannot find out any information - do I need to install SP1 for it?
Just install it, if its found something it can update - it will, if not... it won't....
Thanks to the wonder of Windows Installer (and I don't mean "I wonder why it's doing that?"--I mean like "This is wonderful!") it is unlikely that you have caused any big issues by running the older version afterwards.
So, yeah, you can probably just install the SQL 2008 Express Management Tools with no worries. If you want to be sure, afterwards just run the SP1 installer and it will make sure everything's up-to-date.
I always make sure to apply patches to client tools as well as server services. There is no reason to take the chance that your client tools have fallen behind in servicing.

SQL Server 2005 and 2008 on same developer machine?

Has anyone tried installing SQL Server 2008 Developer on a machine that already has 2005 Developer installed?
I am unsure if I should do this, and I need to keep 2005 on this machine for the foreseeable future in order to test our application easily. Since I sometimes need to take backup files of databases and make available for other people in the company I cannot just replace 2005 with 2008 as I suspect (but do not know) that the databases aren't 100% backwards compatible.
What kind of issues would arise? Do I need to install the new version with an instance name, will that work? Can I use a different port number to distinguish them?
I found this entry on technet: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3496209&SiteID=17
It doesn't say more than just yes you can do this and I kinda suspected that this was doable anyway, but I need to know if there are anything I need to know before I start installing.
Anyone?
Yes this is possible. You will have to create a named instance not used by another version of SQL Server as per the previous answer and version 3.5 of .Net installed. Works great!!
Here the list of prerequisites:
.NET Framework 3.5 SP1
Windows Installer 4.5
Windows PowerShell 1.0
If you have Visual Studio 2008 installed you will get a validation error and you cannot install SQL server 2008 until you install Visual Studio 2008 SP1. If you don't have Visual Studio 2008 installed it should not be a problem. So if you do have Visual Studio 2008 wait till August 11th since that is the day that Visual Studio 2008 SP1 will ship
I believe that this is perfectly possible. I am currently running both SQL Server 2000 and SQL Server 2005 on my development server while I transfer applications over.
The only thing you will have to do is create a new instance which isn't already being used by SQL Server 2005.
As with anything new, there will probably be some bugs, however, it should generally "just work".
my experience is after having sql sever 2005 and 2008 on same machine SSIS 2005 does not work properly... specially with script task, data flow and sequence container
You could run just SQL 2008 as the single instance and then attach/create databases with compatability level of 2005? The problem with that is that its a theory. Im not 100% positive that if you create a database on 2008 , with a compatability level of 2005, and then detach it, that a SQL 2005 instance is capable of attaching it.
I think its a good enough chance to try though. But I agree with the previous answers, the multiple instance options will work fine.
Unfortunately, it seems SQL Server 2008 Client Tools requires Visual Studio 2008 SP1, and I'm loath to install a beta of this on my main development machine.
I'll wait until SP1 is RTM before I move on.
Edit: Yes, I do have Visual Studio 2008 on this machine, but I'd like to avoid beta installations of debugger applications. They tend to dig themselves too deep in for my taste.
I have try it with negativ result. The 2k8 installation breaks with a mysterious error-message. The installation-protocol looks fine, but it will not work. After this the 2k5 installation was buggy too.
The 2k8 installation was half-ready, so it´s already in controlpane / software, but uninstallation is not possible.
So my result - don´t do it on a productive server / workstation. If you need both versions, use a virtual machine instead.