We have a backup application that uses the Windows API BackupRead. It works correctly on Windows Server 2003, 2008, 2008 R2. It does not work on Storage Server 2008 R2. It always fails with error 50 - The request is not supported. The documentation for BackupRead gives no indication that it will not work with Storage Server 2008 R2.
Anyone else have any experience using this API on Storage Server 2008 R2? Did you need to make any changes to your use of the API in order for it to work?
Known problem between Windows 2008 and non-2008 volumes. Hot fix resolves it.
Related
I have a problem when i try to connect my SQL server 2008 express edition to visual studio 2010 and i was try to create web service.
When i am try to install server it show error message like it is not suit for windows 8 operating system.
but i can't connect my SQL server to windows 8 system.
i am using windows 64 bit operating system.
please fix my problem and please suggest correct structure query language version for windows 8.
Thanks advance.....
I've installed the server on a windows 7 64bits PC, the download from MS was for SQL Server 2008 R2 Express x64 with management tools. Firewall is open port 1433 for SQL Server and Management Studio (just in case). All SQL Server services have been configured (including named pipes and TCP/IP and point to the correct port).
From the configuration tool I cannot start SQL Server agent.
When I try and start Management Studio the login fails (windows auth and SQL Server auth)
All the solutions that I could find to a problem similar to mine involves starting Management Studio and enabling remote connection.
If I could this either programmatically (c#.net / ado.net) or modify a key in the registry I would be a happy camper
Thanks in advance
Paul
We have been running a Visual FoxPro (version 9) application on a Server under Microsoft Windows Server 2003 Operating system for a number of years now. We are now trying to migrate it to a different Server running under Microsoft Windows Server 2003 R2 and the application crashes. The problem occurs when it is trying to create HTML files from the FoxPro reports it has just created. To do this is uses the system variable _ReportOutput and aborts with the message “ox is not an object”. The application resides on the Network in a directory accessible to both Servers. Since hitting this problem I have changed the program to use the Htmllistener class within _ReportListener and get the same problem (works on one not on the other (R2)). Wait windows have been inserted to gain additional information but they only show that the object has not been created returning a data type of .Logical. It appears to me the problem is with the R2 version of the operating system, has anybody any ideas.
Have you installed ReportOutput.APP in the same folder as the application?
We just moved one of our .Net applications from a Windows 2003 Server to a virtual Windows Server 2008 R2 (64Bit, VMWare).
This application is a simple console application running on .Net Framework 4.0, 32Bit, that runs different jobs to select, modify and save business data to a database. For the database we use SQL 2008 R2.
Since we run the application on the Windows Server 2008 R2 we recognized, that the execution of Select-Statements with LINQ to SQL are slower than on the Windows Server 2003 we used before. We checked it with a simple LINQ Query, and that tooks about 500 milliseconds longer on Win 2008.
We use the System.Data.Linq.DataContext and get Objects from the Database with the Method GetTable<>().
To compare the duration we took the time from creating the datacontext until the mapping from the DB-Objects back to the .Net-Objects in the application.
See the code:
System.Data.IDbConnection testConnection;
System.Data.Linq.Mapping.MappingSource testMappingSource;
...
...
using (System.Data.Linq.DataContext dc = new System.Data.Linq.DataContext(testConnection, testMappingSource))
{
dc.DeferredLoadingEnabled = false;
return = (from dbObject in dc.GetTable<TestTable>()
select dbObject).FirstOrDefault();
}
On the Windows 2008 R2 Server, the .Net Framework 4.0 is installed, and in the server features the .Net Framework 3.5.1 Features are enabled.
The application was installed on three different stages (Dev, Test, Production) on three Windows 2003 Server. Now it runs on three virtual Windows 2008 R2 Server. We have the same Problem on all three Windows 2008 R2 Server. And we even tested it on a physical Windows 2008 R2 Server; same Problem there.
Has anyone an idea what causes this difference? And what may be a solution to resolve this problem?
Thanks a lot in advance!
Greets
Tom
Our database server is a SQL 2008 server.
My colleagues all have XP service 2 installed with Sql 2008 Management studio and they have absolutely no performance issues.
I however am running Vista x64 (Ultimate) and when I open the 2008 Management studio it's impossibly slow. It takes almost 25 seconds to just connect to the database, so when I run certain portions of our code against the database I more often than not get timeouts.
Everything else on this machine is running like a dream! Is there an issue with SQL2008 on Vista x64 communicating with SQL2008 on a Windows 2003 Server?
Thanks
Nevermind, I have my problem while asking the questions.
Vista has a TCP/IP auto tuning feature. By following this tutorial: http://www.vistax64.com/tutorials/72308-auto-tuning-tcp-ip-receive-level.html I disabled it and now everything runs like a dream!