Cannot Create Full-Text Catalog

I had a perfectly good FT catalog, but I was trying to repopulate it after
making changes to the noiseeng file. I restarted the Full-Text search
engine.
When I tried to run a full-text query against the table, I got this error
"no such interface supported". In the message there was a recommendation to
create a new catalog.
I decided to delete the existing catalog, but now cannot create a new one.
I get the following full message:
TITLE: Microsoft SQL Server Management Studio
Cannot execute changes.
Create failed for FullTextCatalog 'FTCDoctors'. (Microsoft.SqlServer.Smo)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+FullTextCatalog&LinkId=20476[/url]
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
Execution of a full-text operation failed. 'No such interface supported'
(Microsoft SQL Server, Error: 7689)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .3054&EvtSrc=MSSQLServer&EvtID=7689&LinkId=20476[/url]
The links are dead links now. Figures.
Can anyone help me?
Thanks, Ross
Unable to find a cure, I uninstalled the Full-Text engine, rebooted,
reinstalled Full-Text, rebooted and was able to rebuild the catalog and
index. But I'd sure like to know what happened and what this error really
means.
Ross
"Ross Culver" <rculver@.warrenalloy.com> wrote in message
news:eOCFu7brHHA.4180@.TK2MSFTNGP04.phx.gbl...
>I had a perfectly good FT catalog, but I was trying to repopulate it after
> making changes to the noiseeng file. I restarted the Full-Text search
> engine.
> When I tried to run a full-text query against the table, I got this error
> "no such interface supported". In the message there was a recommendation
> to
> create a new catalog.
> I decided to delete the existing catalog, but now cannot create a new one.
> I get the following full message:
> TITLE: Microsoft SQL Server Management Studio
> Cannot execute changes.
> Create failed for FullTextCatalog 'FTCDoctors'. (Microsoft.SqlServer.Smo)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+FullTextCatalog&LinkId=20476[/url]
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> Execution of a full-text operation failed. 'No such interface supported'
> (Microsoft SQL Server, Error: 7689)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .3054&EvtSrc=MSSQLServer&EvtID=7689&LinkId=20476[/url]
> The links are dead links now. Figures.
> Can anyone help me?
> Thanks, Ross
>
>

Cannot connect to SQL until after service is restarted

A new database and application was installed on my SQL Server. Recently
users cannot connect to the database. I cannot even connect with Enterprise
Manager or Query Analyzer. Some users were getting an error message telling
them there was not enough memory.
I am getting the following message in the logs:
WARNING: Failed to commit contiguous memory of Size 65536.
I've configured the SQL Server system to allocated up a minimum of 512MB and
a maxium of 2GB of memory.
Are there any thoughts on how to resolve this problem? Thanks for your
attention.
Tech Details:
SQL Server 2000 Standard
OS: Windows Server 2003 (Small Business Server 2003)
2 Processors (P4 Xeon 3.06Ghz)
4GB memory
Application (Zoll Data Systems?)
Can you post the output from sp_configure? Preferably also attach as a text document to preserve
formatting.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jonathan" <Jonathan@.discussions.microsoft.com> wrote in message
news:15715A15-D833-4C89-B8E8-6B8D12B7C18F@.microsoft.com...
>A new database and application was installed on my SQL Server. Recently
> users cannot connect to the database. I cannot even connect with Enterprise
> Manager or Query Analyzer. Some users were getting an error message telling
> them there was not enough memory.
> I am getting the following message in the logs:
> WARNING: Failed to commit contiguous memory of Size 65536.
> I've configured the SQL Server system to allocated up a minimum of 512MB and
> a maxium of 2GB of memory.
> Are there any thoughts on how to resolve this problem? Thanks for your
> attention.
> Tech Details:
> SQL Server 2000 Standard
> OS: Windows Server 2003 (Small Business Server 2003)
> 2 Processors (P4 Xeon 3.06Ghz)
> 4GB memory
> Application (Zoll Data Systems?)

Cannot connect to SQL until after service is restarted

A new database and application was installed on my SQL Server. Recently
users cannot connect to the database. I cannot even connect with Enterprise
Manager or Query Analyzer. Some users were getting an error message telling
them there was not enough memory.
I am getting the following message in the logs:
WARNING: Failed to commit contiguous memory of Size 65536.
I've configured the SQL Server system to allocated up a minimum of 512MB and
a maxium of 2GB of memory.
Are there any thoughts on how to resolve this problem? Thanks for your
attention.
Tech Details:
SQL Server 2000 Standard
OS: Windows Server 2003 (Small Business Server 2003)
2 Processors (P4 Xeon 3.06Ghz)
4GB memory
Application (Zoll Data Systems?)Can you post the output from sp_configure? Preferably also attach as a text
document to preserve
formatting.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jonathan" <Jonathan@.discussions.microsoft.com> wrote in message
news:15715A15-D833-4C89-B8E8-6B8D12B7C18F@.microsoft.com...
>A new database and application was installed on my SQL Server. Recently
> users cannot connect to the database. I cannot even connect with Enterpri
se
> Manager or Query Analyzer. Some users were getting an error message telli
ng
> them there was not enough memory.
> I am getting the following message in the logs:
> WARNING: Failed to commit contiguous memory of Size 65536.
> I've configured the SQL Server system to allocated up a minimum of 512MB a
nd
> a maxium of 2GB of memory.
> Are there any thoughts on how to resolve this problem? Thanks for your
> attention.
> Tech Details:
> SQL Server 2000 Standard
> OS: Windows Server 2003 (Small Business Server 2003)
> 2 Processors (P4 Xeon 3.06Ghz)
> 4GB memory
> Application (Zoll Data Systems?)

Cannot connect to SQL until after service is restarted

A new database and application was installed on my SQL Server. Recently
users cannot connect to the database. I cannot even connect with Enterprise
Manager or Query Analyzer. Some users were getting an error message telling
them there was not enough memory.
I am getting the following message in the logs:
WARNING: Failed to commit contiguous memory of Size 65536.
I've configured the SQL Server system to allocated up a minimum of 512MB and
a maxium of 2GB of memory.
Are there any thoughts on how to resolve this problem? Thanks for your
attention.
Tech Details:
SQL Server 2000 Standard
OS: Windows Server 2003 (Small Business Server 2003)
2 Processors (P4 Xeon 3.06Ghz)
4GB memory
Application (Zoll Data Systems?)Can you post the output from sp_configure? Preferably also attach as a text document to preserve
formatting.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
http://www.sqlug.se/
"Jonathan" <Jonathan@.discussions.microsoft.com> wrote in message
news:15715A15-D833-4C89-B8E8-6B8D12B7C18F@.microsoft.com...
>A new database and application was installed on my SQL Server. Recently
> users cannot connect to the database. I cannot even connect with Enterprise
> Manager or Query Analyzer. Some users were getting an error message telling
> them there was not enough memory.
> I am getting the following message in the logs:
> WARNING: Failed to commit contiguous memory of Size 65536.
> I've configured the SQL Server system to allocated up a minimum of 512MB and
> a maxium of 2GB of memory.
> Are there any thoughts on how to resolve this problem? Thanks for your
> attention.
> Tech Details:
> SQL Server 2000 Standard
> OS: Windows Server 2003 (Small Business Server 2003)
> 2 Processors (P4 Xeon 3.06Ghz)
> 4GB memory
> Application (Zoll Data Systems?)

Cannot connect to SQL server after setting user connections to 1

I have a problem connecting to SQL Server 2005. After I set "user
connections" to 1 and restarted sql service, I cannot connect to server
anymore. Do you have maybe any suggestion how to set "user connection" back
to 0? It's a SQL Server 2005 Standard with SP1 in two node cluster.
Thanks!
BogdanDisconnect the network to make sure nobody can log in and then set SQL Agent
to manual start to make sure it doesn't grab your only connection. Also
look for any other services that might be grabbing the connection. Stop and
start the SQL service and see if you can get in. Good luck.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Bogdan" <Bogdan@.discussions.microsoft.com> wrote in message
news:2418A056-42A7-43CB-984B-E60A84BB124C@.microsoft.com...
>I have a problem connecting to SQL Server 2005. After I set "user
> connections" to 1 and restarted sql service, I cannot connect to server
> anymore. Do you have maybe any suggestion how to set "user connection"
> back
> to 0? It's a SQL Server 2005 Standard with SP1 in two node cluster.
> Thanks!
> Bogdan|||Note - this assumes you are running SQL Server 2000. If you are running SQL
Server 2005 you can use the administration connection to get in.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:ev2PsHaZGHA.1200@.TK2MSFTNGP03.phx.gbl...
> Disconnect the network to make sure nobody can log in and then set SQL
> Agent to manual start to make sure it doesn't grab your only connection.
> Also look for any other services that might be grabbing the connection.
> Stop and start the SQL service and see if you can get in. Good luck.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Bogdan" <Bogdan@.discussions.microsoft.com> wrote in message
> news:2418A056-42A7-43CB-984B-E60A84BB124C@.microsoft.com...
>

Cannot connect to RS instance after Change IP of server!

Dear All,

We had changed the IP address of our SQL Database server(include the Report Server).

After we finished this, we restarted the server, but now, we cannot connect to the Report instance, database instance have no problem.

How to fix it?

Thank you.

Jeffers

Your connection string is likely stored in the installation folder in the file

<YourProjectName>.exe.config

You can open this file from the installation folder of client computer and modify the IP address manually

<connectionStrings>
<add name="MyTestApplication.My.MySettings.cnnConnection" connectionString="Data Source=123.456.789.234;Initial Catalog=TestDatabase;Integrated Security=True" providerName="System.Data.SqlClient" />
</connectionStrings>

Otherwise if you can open the VS project, open the app.config file and change the IP as above, then recompile and package up a new version to install on client computers.

Yet another way to change the connection string is open project properties(double click on My Project), goto "Settings" tab, change the value of the connection string from there.

Hope this helps.

Kiavash