windows-server-2008-r2

Given a Windows Server 2008 R2 system, where the service accounts use a non-English display language, with SQL Server 2008, the following Transact-SQL statement fails: CREATE LOGIN [NT AUTHORITY\NETWORK SERVICE] FROM WINDOWS ... with the following error: Windows NT user or group 'NT AUTHORITY\NETWORK SERVICE' not found. Check the name again. (or the same message in the non-English display language for the service accounts, depending on the context). This same statement succeeds if the service accounts use English as their display language. The reason seems clear: on, e.g., a German system the

I am a mac girl, working on connecting with knife-windows trough Opscode's managed Chef to my Rackspace Windows servers. (I know, it sounds exotic, but these Windows servers are a customer requirment). I tried to Chef for a spin but I am stuck in trying to bootstrap the Windows 2008 Server on Rackspace with the knife-windows command. I am working on OSX, using rvm, ruby 2.1.0 and a local gemset with chef + knife-windows. I was trying to follow the steps from: https://github.com/opscode/knife-windows I have configured the winrm service. I have set up a rule to allow inbound connections in my

We have a project that compiles to a 32-bit COM DLL and to a 64-bit COM DLL (the same one from my earlier question ). When I register both on my Windows 7 machine, both register successfully. When I register both on a Windows Server 2003 machine, both register successfully. But when I try to register the DLLs on a Windows Server 2008 R2 standard SP1 machine, the 64-bit DLL registers successfully, but the 32-bit DLL fails with the message (sic): The module ""%1"" may not compatible with the version of Windows that you're running. Check if the module is compatible with an x86 (32-bit) or x64 (64

In Visual Studio 2012 RC when I try to validate a Web Deploy connection I get this error message: ERROR_DESTINATION_NOT_REACHABLE The required Web Management Service is started on the server and Web Deploy 3.0 RC is installed. Then using Remote Desktop Connection I log on the server and go check IIS logs located at C:\inetpub\logs\LogFiles\W3SVC1 . There I can see my attempts to validate the connection because they contain my IP address: 2012-07-13 20:58:49 185.201.117.17 HEAD /msdeploy.axd site=Default%20Web%20Site 8172 - 189.10.32.194 - 404 0 2 78 It's giving me a 404. After trying to get

I have an SSIS package--two data flow tasks, 8 components each, reading from two flat files, nothing spectacular. If I run it in BIDS, it takes reliably about 60 seconds. I have a sandbox DB server with the package running in a job which also takes reliably 30-60 seconds. On my production server, the same job with the same package takes anywhere from 30 seconds to 12 hours . With logging enabled on the package, it looks like it bogs down--initially at least--in the pre-execute phase of one or the other (or both) data flow tasks. But I can also see the data coming in--slowly, in chunks, so I

We've recently updated a fairly large ASP.NET website (~1500th alexa traffic ranking) to use VS2010 and .NET 4.0 running on Windows Server 2008 R2 Since then, when we deploy new versions of the site we occasionally noticed the same error in this post: ASP.Net cannot create/shadow copy The error message is: Cannot create/shadow copy 'xxxx, Version=4.0.4301.26898, Culture=neutral, PublicKeyToken=null' when that file already exists However, unlike in that post, the error is occurring only in our production environments & only on some servers. After we ship a new version of the code, we recycle

I have a Windows Server 2008 (64-bit) box that I am doing development on. I've installed Visual Studio 2010 and System.Data.SQLite (from sqlite.phxsoftware.com). My problem is that the former is not seeing the latter. That is, when I go to the Server Explorer in Visual Studio and select "Connect to Database" and the "Choose Data Source" window appears, SQLite does not appear under the list of data sources. Anyone know what the deal is with that? Could it be an issue with Windows Server 2008 because in the past I've no issues with VS 2010 + System.Data.Sqlite on a Windows 7 box. Update: System