Thursday, March 29, 2012
Cannot remove replication
I have a box running SQL 7 with replication. I restored one of the
replicated database to another SQL 7 with no replication. A developer needed
to test an upgrade of an application (MS Great Plains) using that database.
The application states that the tables are part of a replication. As far as I
know, when you restore a replicated DB to another server (with no
replication), the replication infomation is lost. I have also ran
sp_removedbreplication successfully but we still have the same problem.
Any ideas?
--
--
I saw it work in a cartoon once so I am pretty sure I can do it.The tables in question are still marked for replication.
I think you may need to manually update some of the system tables to remove
the marking for replication on the object.
I don't have my poster here at the office, so i couldn't tell you which
tables specically to look at.
I would guess sysobjects.xtype....
Rick Sawtell
MCT, MCSD, MCDBA
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:260846C9-A09A-415A-8028-715D66021376@.microsoft.com...
> Hi,
> I have a box running SQL 7 with replication. I restored one of the
> replicated database to another SQL 7 with no replication. A developer
needed
> to test an upgrade of an application (MS Great Plains) using that
database.
> The application states that the tables are part of a replication. As far
as I
> know, when you restore a replicated DB to another server (with no
> replication), the replication infomation is lost. I have also ran
> sp_removedbreplication successfully but we still have the same problem.
> Any ideas?
> --
> --
> I saw it work in a cartoon once so I am pretty sure I can do it.|||I don't have a SQL 7.0 box at work anymore, but if it
also exists on SQL 7.0, please try using
sp_MSunmarkreplinfo which takes a tablename as a parameter
HTH,
Paul Ibison (SQL Server MVP)
>> (recommended sql server 2000 replication book:
>> http://www.nwsu.com/0974973602p.html)|||Before updatnig system tables, I would recommend making sure you've dropped
the distributor and publisher. In EM from Tools...Replication...configure
publishing subscribers and distributors. Make sure there are no selections
(uncheck all boxes).
Colleen
"Paul Ibison" wrote:
> I don't have a SQL 7.0 box at work anymore, but if it
> also exists on SQL 7.0, please try using
> sp_MSunmarkreplinfo which takes a tablename as a parameter
> HTH,
> Paul Ibison (SQL Server MVP)
> >> (recommended sql server 2000 replication book:
> >> http://www.nwsu.com/0974973602p.html)
>
>
Cannot remove replication
I have a box running SQL 7 with replication. I restored one of the
replicated database to another SQL 7 with no replication. A developer needed
to test an upgrade of an application (MS Great Plains) using that database.
The application states that the tables are part of a replication. As far as
I
know, when you restore a replicated DB to another server (with no
replication), the replication infomation is lost. I have also ran
sp_removedbreplication successfully but we still have the same problem.
Any ideas?
--
I saw it work in a cartoon once so I am pretty sure I can do it.The tables in question are still marked for replication.
I think you may need to manually update some of the system tables to remove
the marking for replication on the object.
I don't have my poster here at the office, so i couldn't tell you which
tables specically to look at.
I would guess sysobjects.xtype....
Rick Sawtell
MCT, MCSD, MCDBA
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:260846C9-A09A-415A-8028-715D66021376@.microsoft.com...
> Hi,
> I have a box running SQL 7 with replication. I restored one of the
> replicated database to another SQL 7 with no replication. A developer
needed
> to test an upgrade of an application (MS Great Plains) using that
database.
> The application states that the tables are part of a replication. As far
as I
> know, when you restore a replicated DB to another server (with no
> replication), the replication infomation is lost. I have also ran
> sp_removedbreplication successfully but we still have the same problem.
> Any ideas?
> --
> --
> I saw it work in a cartoon once so I am pretty sure I can do it.
Cannot remove replication
also exists on SQL 7.0, please try using
sp_MSunmarkreplinfo which takes a tablename as a parameter
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]Before updatnig system tables, I would recommend making sure you've dropped
the distributor and publisher. In EM from Tools...Replication...configure
publishing subscribers and distributors. Make sure there are no selections
(uncheck all boxes).
Colleen
"Paul Ibison" wrote:
> I don't have a SQL 7.0 box at work anymore, but if it
> also exists on SQL 7.0, please try using
> sp_MSunmarkreplinfo which takes a tablename as a parameter
> HTH,
> Paul Ibison (SQL Server MVP)
>
>
>
Cannot remove replication
also exists on SQL 7.0, please try using
sp_MSunmarkreplinfo which takes a tablename as a parameter
HTH,
Paul Ibison (SQL Server MVP)
[vbcol=seagreen]
Before updatnig system tables, I would recommend making sure you've dropped
the distributor and publisher. In EM from Tools...Replication...configure
publishing subscribers and distributors. Make sure there are no selections
(uncheck all boxes).
Colleen
"Paul Ibison" wrote:
> I don't have a SQL 7.0 box at work anymore, but if it
> also exists on SQL 7.0, please try using
> sp_MSunmarkreplinfo which takes a tablename as a parameter
> HTH,
> Paul Ibison (SQL Server MVP)
>
>
sql
Tuesday, March 27, 2012
Cannot remove replication
I have a box running SQL 7 with replication. I restored one of the
replicated database to another SQL 7 with no replication. A developer needed
to test an upgrade of an application (MS Great Plains) using that database.
The application states that the tables are part of a replication. As far as I
know, when you restore a replicated DB to another server (with no
replication), the replication infomation is lost. I have also ran
sp_removedbreplication successfully but we still have the same problem.
Any ideas?
--
I saw it work in a cartoon once so I am pretty sure I can do it.
The tables in question are still marked for replication.
I think you may need to manually update some of the system tables to remove
the marking for replication on the object.
I don't have my poster here at the office, so i couldn't tell you which
tables specically to look at.
I would guess sysobjects.xtype....
Rick Sawtell
MCT, MCSD, MCDBA
"Sasan Saidi" <SasanSaidi@.discussions.microsoft.com> wrote in message
news:260846C9-A09A-415A-8028-715D66021376@.microsoft.com...
> Hi,
> I have a box running SQL 7 with replication. I restored one of the
> replicated database to another SQL 7 with no replication. A developer
needed
> to test an upgrade of an application (MS Great Plains) using that
database.
> The application states that the tables are part of a replication. As far
as I
> know, when you restore a replicated DB to another server (with no
> replication), the replication infomation is lost. I have also ran
> sp_removedbreplication successfully but we still have the same problem.
> Any ideas?
> --
> --
> I saw it work in a cartoon once so I am pretty sure I can do it.
Cannot Remotely Access SQL Server Standard Named Instance
Good Day,
I am creating a SQL Named instance as a testing environment. This instance is on the same physical box as my Development environment, both are SQL 2005 standard edition. From the server in Management Studio, I can load, and interact with both instances. From a remote connection (e.g., my pc) I cannot access the named instance. I am getting the following:
Connect to Server
X Cannot connect to <server>\<named instance>
Additional Information
An error has occured while establishing a connection to the server. When connecting to SQL Sever 2006, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)(Microsoft SQL Server)
I have checked, and rechecked the server settings for this named instance, and remote connections are set to "allow" I have enabled TCPIP and Named Pipes prototocals, and have ensured that my firewall is allowing the "listenting port" for the named instance, and have even tried turning off my XP firewall during testing.
I am sure that I have probably missed something, and have searched the community but only have been able to find resolutions that I have already tried. Is there more?
Thanks in advance for any help and guidance you can provide.
hi mt,
please be guided by this article
http://forums.microsoft.com/MSDN/AddPost.aspx?PostID=807492&SiteID=1
regards,
joey
|||" error: 26 - ErrorLocating Server/Instance Specified", it means that it's trying to
locate the SQL Server using SSRP but could not get contact with SQL
Browser. So, please make sure your SQL Browser is running.
|||Yes, that is absolutely it. I did not set up the Browser Severvice to run. Thank you.Cannot register SQL Server 2000SP3 from client computer
and there is no data in the server at all besides default data. I have
my workstation that I have installed client tools on. I am attempting
to log into the sql server via the enterprise manager. I decided to
use the sql account sa to login. I figured if any account would get in
it would be that one. However I am mistaken because it seems that no
matter what I try I cannot get it to work. I get the following errror:
SQL Server does not exist or access denied.ConnectionOpne(Connect())
Any help would be greatly appreciated...
Graham Hill
grahamhil@.yahoo.com
Hi,
This error will come due to below reasons:-
1. Network issue - Not able to connect from client to SQL server machine
2. SQL server Service might be down
3. Connecting to wrong machine
Can you try creating a Alias of the SQL server in you client using "CLient
Network utility". USe the TCP/IP protocol , IP and port number of server.
After that use this Alias name to register in enterprise manager.
See the below link.
http://support.microsoft.com/default...;en-us;Q328306
Thanks
Hari
MCDBA
"G-ram" <grahamhil@.yahoo.com> wrote in message
news:55739f20.0407211734.8345d96@.posting.google.co m...
> I have a sql server residing on a win2k3 box. It is a new installation
> and there is no data in the server at all besides default data. I have
> my workstation that I have installed client tools on. I am attempting
> to log into the sql server via the enterprise manager. I decided to
> use the sql account sa to login. I figured if any account would get in
> it would be that one. However I am mistaken because it seems that no
> matter what I try I cannot get it to work. I get the following errror:
> SQL Server does not exist or access denied.ConnectionOpne(Connect())
> Any help would be greatly appreciated...
> Graham Hill
> grahamhil@.yahoo.com
|||Graham,
If you have a firewall on either computer, please disable it for tests
and see what happens.
Also let us know what authentication mode you have set up - either
Windows Authentication mode, Mixed mode, or SQL Server mode. If yiou
selected Windows Authentication then you may not be able to log in
under the SA account.
Lou Arnold
On 21 Jul 2004 18:34:05 -0700, grahamhil@.yahoo.com (G-ram) wrote:
>I have a sql server residing on a win2k3 box. It is a new installation
>and there is no data in the server at all besides default data. I have
>my workstation that I have installed client tools on. I am attempting
>to log into the sql server via the enterprise manager. I decided to
>use the sql account sa to login. I figured if any account would get in
>it would be that one. However I am mistaken because it seems that no
>matter what I try I cannot get it to work. I get the following errror:
>SQL Server does not exist or access denied.ConnectionOpne(Connect())
>Any help would be greatly appreciated...
>Graham Hill
>grahamhil@.yahoo.com
Cannot register SQL Server 2000SP3 from client computer
and there is no data in the server at all besides default data. I have
my workstation that I have installed client tools on. I am attempting
to log into the sql server via the enterprise manager. I decided to
use the sql account sa to login. I figured if any account would get in
it would be that one. However I am mistaken because it seems that no
matter what I try I cannot get it to work. I get the following errror:
SQL Server does not exist or access denied.ConnectionOpne(Connect())
Any help would be greatly appreciated...
Graham Hill
grahamhil@.yahoo.comHi,
This error will come due to below reasons:-
1. Network issue - Not able to connect from client to SQL server machine
2. SQL server Service might be down
3. Connecting to wrong machine
Can you try creating a Alias of the SQL server in you client using "CLient
Network utility". USe the TCP/IP protocol , IP and port number of server.
After that use this Alias name to register in enterprise manager.
See the below link.
http://support.microsoft.com/defaul...b;en-us;Q328306
Thanks
Hari
MCDBA
"G-ram" <grahamhil@.yahoo.com> wrote in message
news:55739f20.0407211734.8345d96@.posting.google.com...
> I have a sql server residing on a win2k3 box. It is a new installation
> and there is no data in the server at all besides default data. I have
> my workstation that I have installed client tools on. I am attempting
> to log into the sql server via the enterprise manager. I decided to
> use the sql account sa to login. I figured if any account would get in
> it would be that one. However I am mistaken because it seems that no
> matter what I try I cannot get it to work. I get the following errror:
> SQL Server does not exist or access denied.ConnectionOpne(Connect())
> Any help would be greatly appreciated...
> Graham Hill
> grahamhil@.yahoo.com|||Graham,
If you have a firewall on either computer, please disable it for tests
and see what happens.
Also let us know what authentication mode you have set up - either
Windows Authentication mode, Mixed mode, or SQL Server mode. If yiou
selected Windows Authentication then you may not be able to log in
under the SA account.
Lou Arnold
--
On 21 Jul 2004 18:34:05 -0700, grahamhil@.yahoo.com (G-ram) wrote:
>I have a sql server residing on a win2k3 box. It is a new installation
>and there is no data in the server at all besides default data. I have
>my workstation that I have installed client tools on. I am attempting
>to log into the sql server via the enterprise manager. I decided to
>use the sql account sa to login. I figured if any account would get in
>it would be that one. However I am mistaken because it seems that no
>matter what I try I cannot get it to work. I get the following errror:
>SQL Server does not exist or access denied.ConnectionOpne(Connect())
>Any help would be greatly appreciated...
>Graham Hill
>grahamhil@.yahoo.com
Sunday, March 25, 2012
Cannot preview/deploy error
Services evaluation installed (Visual Studio 2003), I get a blank screen with
no preview. My SQL statement appears to be fine, because I get no errors
when I execute it on the Data tab, and see the data that should be reported
on.
When I try to deploy the report from within Visual Studio, I get an error
message telling me that "The type initializer for
'Microsoft.ReportingServices.Diagnostics.CatalogItemUrlBuilder' threw an
exception", and nothing gets deployed. Is there any way to get details on
this exception thrown, or a known way to prevent this?
If I upload the .rdl file into the http://localhost/Reports report manager
site manually, the report generates and displays without any kind of errors.Several people have reported this error, but we have never identified the
source. Can you try debugging the Report Designer process? (Attach another
instance of Visual Studio as a debugger, enable catching exceptions and view
the call stack.) Send me a dump of the call stack.
Thanks,
--
Albert Yen
SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"B Shaffer" <B Shaffer@.discussions.microsoft.com> wrote in message
news:E6ED9D3F-10A7-49B5-AFD9-D2411E702815@.microsoft.com...
> When I try to preview a report developed an on XP Pro box with Reporting
> Services evaluation installed (Visual Studio 2003), I get a blank screen
> with
> no preview. My SQL statement appears to be fine, because I get no errors
> when I execute it on the Data tab, and see the data that should be
> reported
> on.
> When I try to deploy the report from within Visual Studio, I get an error
> message telling me that "The type initializer for
> 'Microsoft.ReportingServices.Diagnostics.CatalogItemUrlBuilder' threw an
> exception", and nothing gets deployed. Is there any way to get details on
> this exception thrown, or a known way to prevent this?
> If I upload the .rdl file into the http://localhost/Reports report manager
> site manually, the report generates and displays without any kind of
> errors.|||This problem was bizarre - after restarting my PC the following day, the
problems with deploying the reports and previewing reports went away. I've
been able to deploy and preview without any difficulty since.
"Albert Yen [MSFT]" wrote:
> Several people have reported this error, but we have never identified the
> source. Can you try debugging the Report Designer process? (Attach another
> instance of Visual Studio as a debugger, enable catching exceptions and view
> the call stack.) Send me a dump of the call stack.
> Thanks,
> --
> Albert Yen
> SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "B Shaffer" <B Shaffer@.discussions.microsoft.com> wrote in message
> news:E6ED9D3F-10A7-49B5-AFD9-D2411E702815@.microsoft.com...
> > When I try to preview a report developed an on XP Pro box with Reporting
> > Services evaluation installed (Visual Studio 2003), I get a blank screen
> > with
> > no preview. My SQL statement appears to be fine, because I get no errors
> > when I execute it on the Data tab, and see the data that should be
> > reported
> > on.
> >
> > When I try to deploy the report from within Visual Studio, I get an error
> > message telling me that "The type initializer for
> > 'Microsoft.ReportingServices.Diagnostics.CatalogItemUrlBuilder' threw an
> > exception", and nothing gets deployed. Is there any way to get details on
> > this exception thrown, or a known way to prevent this?
> >
> > If I upload the .rdl file into the http://localhost/Reports report manager
> > site manually, the report generates and displays without any kind of
> > errors.
>
>
Monday, March 19, 2012
Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user xx
hi,
so i have a new box and I'm trying to get my websites and SQL Server 2005 Standard Edition working on it, but the pages give me the following error when I try to load them:
"Cannot Open Database "XXXX" requested by login. The login failed. Login failed for user 'xxx'"
Everything seems exactly the same settings and user-wise from my old box to my new one, but nevertheless everything I've tried gives me the same error.
I've tried creating new users in SQL Server and giving them appropriate permissions to my database. I've even tried just using the built in 'sa' account. Nothing seems to change the error, except when I give it the incorrect password then it just says 'login failed'
This leads me to believe that i'm successfully logging into the SQL Server, but it doesn't want to give me access to the database I'm requesting access too. But "apparently" the account i'm using should have access to the database. If nothing else the 'sa' account should, but that didn't work either.
I'm stumped. Any ideas?
Check the database settings for user you are trying to login with and make sure they have permission and deny data reader is not checked.|||yep, the user currently has SELECT, UPDATE, INSERT, DELETE, and CONNECT permission selected.|||Look in the database properties under users and make sure the user has permissions there|||yep, the user is even marked as the dbowner.|||
here is my connection string just in case it's something funny there, but this connection string works on my old box with apparently the exact same settings
<
addname="ConnectionString"connectionString="Server=ServerName;Database=MyDatabase;User ID=MyID;Password=MyPassword;Trusted_Connection=False"providerName="System.Data.SqlClient" />|||ha!
the problem was that when I restored my database (from the old box to the new box), SQL Server replaced a certain character in the name with a different character. Namely replaced "\" with "_".
So it wasn't finding the database... I didn't need those five hours of my life anyways ;-)
Saturday, February 25, 2012
Cannot install SQL 2000 Reporting Services on W2K3 server
I want to install SQL 2000 Reporting Services Component on a Windows Server
2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
message 'System Check Results --> ASP.NET is not installed or is not
registered with your Web Server". However, I'd checked the Web service
extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
the Reporting Services Database on the SQL 2000 cluster?
TIA.Hi, I have the same problem, I "only" have the error that I dont have asp.net
installed or configured, despite that it is installed and configured, I have
both asp.net 1.1 and 2.0, I have tried to switch between both, but the result
is the same error, any ideas? Have you got a solution yet?
DQ
"M C" wrote:
> Hi ALL,
> I want to install SQL 2000 Reporting Services Component on a Windows Server
> 2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
> message 'System Check Results --> ASP.NET is not installed or is not
> registered with your Web Server". However, I'd checked the Web service
> extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
> v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
> the Reporting Services Database on the SQL 2000 cluster?
> TIA.
>
>|||SOLUTION that helped me!!
FIX: Error "ASP.NET v1.1 not Installed" while installing Sql Server 2000
Reporting Services
I finally had the chance to rebuild my dev machine with the RTM version of
Sql Server 200 Reporting Services [SQL2kRS] and ran into an unusual error.
During the "Check Prerequisites" stage of installation, it said that I didnt
have ASP.NET v1.1 installed on my PC. Considering that I do web-development
with VS.NET 2003 on this PC I was a bit perplexed why it said that.
After much digging and exploring, I finally discovered the problem. A
recent install of the new XP version of the Longhorn Command Shell had
installed the .NET Framework v2.0.31113.33 and set it as the Root Version of
the framework for ASP.NET.
So, the fix is pretty trivial, just update the RootVer registry value to
correctly (or temporarily) show v1.1.4322.573.
[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"
Strangely enough, this didnt seem to be affecting my ASP.NET applications.
*shrug*
None of this was documented in the verbose Help files that shipped with
SQL2kRS. This got me thinking about the nature of help files. Far too
often, I see FAQ's and "Common Issues" under the Troubleshooting section of
help files, yet rarely do I have those "common" problems.
I would much prefer a generic section on, "How to troubleshoot", "Where to
look for error clues", and provide deep lists of "Why an application or
installation might fail".
In this case, I actually did find a good reference in the Help entitled "Log
Files Used During Installation". This section explained how to locate the
log files created during installation, and this is how I eventually solved
the problem.
For reference, in SQL2kRS there are 3 main places to look for log files;
C:\Program Files\Microsoft SQL Server\80\RS Setup Bootstrap\Log\RSStp_.cab
(inside the CAB)
AND
%temp%\rsstp<integer>.log
(<integer> = number to make filename unique. e.g. rsstp2.log)
AND
%temp%\RSMSI<integer>.log
The latter 2 log files are the same ones that get copied into the CAB file
listed above, but its still useful knowledge in case something fails before
they get added to the CAB.
"DQ" wrote:
> Hi, I have the same problem, I "only" have the error that I dont have asp.net
> installed or configured, despite that it is installed and configured, I have
> both asp.net 1.1 and 2.0, I have tried to switch between both, but the result
> is the same error, any ideas? Have you got a solution yet?
> DQ
>
> "M C" wrote:
> > Hi ALL,
> >
> > I want to install SQL 2000 Reporting Services Component on a Windows Server
> > 2003 with SP1 box. While I ran the SQL 2000 setup.exe, it prompted the error
> > message 'System Check Results --> ASP.NET is not installed or is not
> > registered with your Web Server". However, I'd checked the Web service
> > extensions and 'Active Server Pages', 'ASP.NET v1.1.4322' and 'ASP.NET
> > v2.0.50727' had been allowed. Do anyone have the same problem? Can I install
> > the Reporting Services Database on the SQL 2000 cluster?
> >
> > TIA.
> >
> >
> >
Sunday, February 12, 2012
Cannot Generate SSPI context
I disabled the Namedpipes and enabled the TCP/IP
protocol in the the sql server box. The box/server
is rebooted after this change. My client workstation
is not to connect to the SQL Server. The SQL Server is
running. With in the SQL Server box, I can use query
analyzer to connect to sql server and works.
From my client workstation, I receive the below error
message.
"Cannot Generate SSPI context"
I restart my workstation too. Still the same problem.
I tried the possible solutions given in the web site.
Article#: 269541.
Could you please help me.
Thanks
Saravanan KunjuSome things to check -
can you ping the server from your workstation?
Have you tried setting up an alias to the server from your
workstation using the Client Network Utility?
You should also refer to the following article for
additional troubleshooting steps:
HOW TO: Troubleshoot the "Cannot Generate SSPI Context"
Error Message
http://support.microsoft.com/?id=811889
-Sue
On Tue, 20 Apr 2004 09:34:54 -0700, "Saravanan Kunju"
<kavisarav@.yah00.com> wrote:
>Hi,
>I disabled the Namedpipes and enabled the TCP/IP
>protocol in the the sql server box. The box/server
>is rebooted after this change. My client workstation
>is not to connect to the SQL Server. The SQL Server is
>running. With in the SQL Server box, I can use query
>analyzer to connect to sql server and works.
>From my client workstation, I receive the below error
>message.
> "Cannot Generate SSPI context"
>I restart my workstation too. Still the same problem.
>I tried the possible solutions given in the web site.
>Article#: 269541.
>Could you please help me.
>Thanks
>Saravanan Kunju
>