The features of system is;
Microsoft SQL Server Management Studio 10.0.1600.22 ((SQL_PreRelease).080709-1414 )
Microsoft Analysis Services Client Tools 2007.0100.1600.022 ((SQL_PreRelease).080709-1414 )
Microsoft Data Access Components (MDAC) 6.0.6002.18005 (lh_sp2rtm.090410-1830)
Microsoft MSXML 3.0 5.0 6.0
Microsoft Internet Explorer 8.0.6001.19475
Microsoft .NET Framework 2.0.50727.4241
Operating System 6.0.6002
on windows 2008 Server ;
i have connection on sql server. not locally.
there is no problem. by this way; but one or two days later it doesn't allow us to connect.
if i restart server (computer) it connects again.
how can i solve this problem
Related
The current setup of the server is Windows Server 2008 sp1, with SQL Server Reporting Services 2008 r2 installed. The databases are on a separate server which is using SQL Server 2008 r2.
I have a new server with Windows Server 2012 r2, I have installed SSRS 2016 on this server and configured it the same as the original server, restored the encryption keys, and connected to an exact copy of the DB server.
Locally on the new RS server I can access and run the reports using the web interface http://{servername}/reports/. However when I try to access the same url remotely I get redirected to http://{servername}/reports/#/browse, I can see the folders and reports, but when I run a report I get a blank report.
It appears as if ssrs 2016 does not support IE9. The machine I was using to access the server remotely only had IE9 installed. When I used the IE development tools on the server itself to browse to the site using IE9 standards, I had the same problems.
I'm already using Visual Studio 2008 and SQL Server 2008 and now I want to upgrade to SQL Server 2014. But there is an error
This server version is not supported. Only servers up to Microsoft SQL Server 2005 are supported
But connect via coding I got the data but not viewing table data in Server Explorer.
You cannot access correctly the Server Explorer using a lower version SSMS on a newer version of SQL Server (if that is what you mean).
I have an application written in MS ACCESS 2007 using VBA, connecting to an SQL Server at the back end. Both Access and SQL Server are running locally.
My machine runs Access 2010 and MS SQL Server Express 2008 R2 (both 32-bit, on WinXP) with no problem.
I have another machine, Win7 64-bit, running both Access 2010 and SQL Server 2008 (NOT R2) 64-bit.
When I run the Access application on the 64-bit machine, I have a drop down box to select the SQL Server which holds the various databases. When I select the server, after a few seconds I get an error:
Run-time error '-2147024703 (800700c1)':
Automation error %1 is not a valid Win32 application.
When I select the Debug option, the yellow arrow points to:
Set oServer = New SQLDMO.SQLServer
The next line is:
oServer.Connect ServerName, strSQLUser, strSQLPwd
In the watch list, I can see that ServerName, strSQLUser, and strSQLPwd hold the right values to access the SQL Server. I've tested these in sqlcmd and successfully was able to query tables.
Can anyone please help me out on this one? I'm not sure what to do next.
Seems like you've got registered a 32-bit SQLDMO on your system that is being used for connection to the 64-bit instance. Check your registry / file system for SQLDMO.dll versions and register the correct one.
Also check MSDN "Installing SQL-DMO" because SQLDMO was scheduled for remove after SQL Server 2008 R2:
Avoid using this feature in new development work, and plan to modify applications that currently use this feature.
SQL Server Database Management Objects (SQL-DMO) has been removed from SQL Server 2008 R2 Express and the SQL Server 2008 R2 Feature Pack. SQL-DMO also does not support Database Engine features introduced after SQL Server 2000. We recommend that you modify applications that currently use this feature as soon as possible. If you must support SQL-DMO, install the Backward Compatibility Components from the SQL Server 2008 Feature Pack from the Microsoft Download Center. Do not use SQL-DMO in new development work; use SQL Server Management Objects (SMO) instead. You can obtain the SMO documentation by installing SQL Server 2008 R2 Books Online.
Thanks for this.
I looked to find SQLDMO.DLL 64-bit version, but although using the Backwards Comparability package for x64, installing using the MSI did not do the job.
I had to manually extract the files and place the correct version (which is ~2MB larger than the x86 version as an indication to knowing which one is the x64) and then run 'regsvr32 sqldmo.dll ' in the command line (very important: need to run cmd as Administrator for this to succeed).
After the module has been registered, my Access front end run great.
I'm working with
1) Window7 32bit
2) VS 2005
3) language: C#
I made an application that connects to an Access file and deployed the applicatioin with Clickonce on my computer.
I published in release/any cpu mode.
The prerequisites was .Net Framework 2.0.
When I installed the appliction on another computer (Window7 64bit, MS Access Database Engine 2010 32bit), an error occurred.
The error message was Cannot Connect to Database.... System.Data.
My connection string is Provider=Microsoft.ACE.OLEDB.12.0;Data Source=....
64-bit and 32-bit components don't play well together.
I had a similar issue with 64-bit Windows and a 32-bit ODBC driver. You most likely need the 64-bit version of the Access database driver.
I'm writing a .NET app that connects to a remote hosted SQL Server. Researching hosts for when I roll this app out to multiple customers, I find that SQL Server 2008 R2 Web Edition is cheaper (monthly on a hosted dedicated server) than the Workgroup Edition and much cheaper than the Standard edition. Everything says Web Edition is for "website support" and "internet facing" use.
I know I must use Windows Server Standard and not Windows Server Web Edition to support database services, but what about the SQL Server version?
Simply - can a large number of users of a .NET Windows Forms program use a direct connection string to connect to SQL Server 2008 R2 Web Edition on the hosted server without going through a web server / browser?
Yes, it supports remote data connections.
Yes.
From my understanding of Web Edition, it is basically a mid-liner between Express and Standard. It's obviously not free, but it doesn't have the restrictions that Express does yet gives a lot of features (PBM, more than 1 CPU utilization, etc.).