|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
If you can't
login and post questions or you are having trouble viewing forum posts:
Click Here
|
Callback
Support |
|
If you live in USA, UK, Canada, Australia or New
Zealand, you can leave us details on your question and request us to call you back and discuss
them with you personally (charges apply). |
|
Click Here
|
Buy Support
Incidents |
|
If you can't find your answer
in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us
private or confidential information: |
|
Click Here
|
|
| SQL Server 2005 Standard Edition Known Issues |
| Author |
Message |
| Ian |
| |
| Group | : Members |
| Posts | : 19 |
| Joined | : 2006-05-03 |
|
| Profile |
|
| Posted : 2006-05-10 01:55:55 |
Are there any known issues with SQL Server 2005? We are using the DCOM setup and have had it working fine but now that we have moved everything to the production server we cannot get it to work. We can successfully run TestDCOM.php and the SQL Script that is provided with no problems. VBDemo works and we have also run the automated security scripts that are provided.
When we attempt to submit a query such as SELECT * FROM OPENQUERY(QODBC, 'SELECT ListID, Name FROM Customer') we receive the following error:
Msg 109, Level 20, State 0, Line 0 A transport-level error has occurred when receiving results from the server. (provider: Shared Memory Provider, error: 0 - The pipe has been ended.)
Any suggestions?
Thanks -- Ian
|
|
|
|
| Tom |
 |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-05-10 09:47:07 |
| As you are using QODBC v6.00.00.138, you need to update to v6.00.00.155, see: How can I get the latest version of QODBC?
After you have updated QODBC, check that "Disallow adhoc accesses" is unchecked to allow OPENQUERY to function in the Link Server setup. Next, check that "Run 2.1 ODBC Compatibility" is checked in the QODBC Setup Screen Advanced Tab Page.
Try running this:
SELECT * FROM OPENQUERY(QODBC, 'SELECT * FROM Host')
to see if any data is returned as it only returns a single row. |
|
|
|
| Ian |
| |
| Group | : Members |
| Posts | : 19 |
| Joined | : 2006-05-03 |
|
| Profile |
|
| Posted : 2006-05-12 06:16:09 |
I have done all of these steps and it is still not working - I am receiving the same error I described before. In SQL Server 2005 there is no option in the Linked Server setup screen for "Disallow adhoc accesses". On my development machine it worked fine without having to set an option like that. I am not sure if that helps but I am still searching for a solution.
Cheers - Ian |
|
|
|
| Tom |
| |
| Group | : Administrator |
| Posts | : 5510 |
| Joined | : 2006-02-17 |
|
| Profile |
|
| Posted : 2006-06-28 13:01:17 |
|
|
|
|