|
| | | StrataFrame User
 
Group: StrataFrame Users
Last Login: Yesterday @ 3:00:39 PM
Posts: 244, Visits: 816 |
| | Well, I thought it was simple. Another error has popped up. The server is telling me that it is refusing connections. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) This doesn't make much sense. It is a 2K server and name pipes are the active protocol and there is no limit set on connections. Also, how could I deploy the database, but not be able to access it? Interesting!
Bill |
| |
| | | StrataFrame User
Group: StrataFrame Users
Last Login: Yesterday @ 3:00:39 PM
Posts: 244, Visits: 816 |
| Solved.  It had to be in the data source string. So, after reviewing it, I realized that the instance name was not represented properly. Wrong: Data Source=SERVER/INSTANCE Right: Data Source=SERVER\\INSTANCE Hey, what's a back slash between friends? Bill |
| |
| | | 
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Yesterday @ 3:24:00 PM
Posts: 3,733, Visits: 3,926 |
| LOL...glad you found your problem  |
| |
| | |
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Yesterday @ 3:24:00 PM
Posts: 3,733, Visits: 3,926 |
| | Yup...you found it. The SecurityDataSourceKey tells the RBS BOs which data source to use. |
| |
| | | StrataFrame VIP
Group: StrataFrame Users
Last Login: Yesterday @ 6:42:41 PM
Posts: 1,058, Visits: 2,581 |
| Here's what I think is happening...the database table is named 'master', not 'Master'. The casing is wrong. This is not something that I am able to fix. What can I do, now?
SQL server doesn't care about casing. So...
Use master
and
Use master
both work. |
| |
| | |
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Yesterday @ 3:24:00 PM
Posts: 3,733, Visits: 3,926 |
| | Actually, the defaults were changed on your server to be case sensitive...this is generally a bad idea. There are certain developers out there that swear by case-sensitive SQL Servers, but it can complicate things, as you have learned. When you install SQL Server, by default, it will assume Case-Insensitive. You can change this through the SQL Server Management Studio, but this is what is happening to you...good eye |
| |
| | | StrataFrame User
Group: StrataFrame Users
Last Login: Yesterday @ 3:00:39 PM
Posts: 244, Visits: 816 |
| | The old SQL Server on which I placed the app data is one of the original RDBMSs in our company. It started at v7 (maybe even 6.5!) and one of the requirements by the software that we bought it for was case-sensitivity. It is often a headache to work around. That is why I got a second SQL Server to do the other heavy lifting. The main app data will have to reside on the old one, unfortunately. |
| |
| | | StrataFrame VIP
Group: StrataFrame Users
Last Login: Yesterday @ 6:42:41 PM
Posts: 1,058, Visits: 2,581 |
| Actually, the defaults were changed on your server to be case sensitive...
Jeesh, I completely forgot about that option. 
There are certain developers out there that swear by case-sensitive SQL Servers, but it can complicate things, as you have learned.
I certainly understand swearing at developers who turn this option on...  |
| |
|
|