Help with update forms: errors

Showing posts with label errors. Show all posts

Monday, March 26, 2012

Help! SQL errors after Win 2003 Upgrade

Help! I am in a jam and need help suggestions and ideas ASAP!
After performing an in-service operating system upgrade from Win 2000 to Win
2003 both of our SQL Server applications are behaving very badly. The SQL
applications are either giving us errors or unable to run at all. Veritas
Backup Exec is unablel to b
rowse the SQL Database and after working with them for several hours they ar
e stumped.
Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix thi
s mess? Or is the best fix going to be an all night server format and reins
tall of Windows 2003, SQL 2000, and all of the applications?
Thanks! in advance for anything you can give me.
NC Beach BumReapply SP3a.
Uninstall Veritas agent.
Reinstall Veritas agent.
What other application connectivity errors are you getting?
Check your alias settings in Client Network Utility. You may need remove
any alias settings that force named pipes connection to a local instance. I
have seen some problems with SQL Agent on those circumstances
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:66808E92-5A64-45AB-91C0-25321EC56C6C@.microsoft.com...
> Help! I am in a jam and need help suggestions and ideas ASAP!
> After performing an in-service operating system upgrade from Win 2000 to
Win 2003 both of our SQL Server applications are behaving very badly. The
SQL applications are either giving us errors or unable to run at all.
Veritas Backup Exec is unablel to browse the SQL Database and after working
with them for several hours they are stumped.
> Has anyone else heard of this issue? Would a reinstall of SQL SP3a fix
this mess? Or is the best fix going to be an all night server format and
reinstall of Windows 2003, SQL 2000, and all of the applications?
> Thanks! in advance for anything you can give me.
> NC Beach Bum
>|||Jeff,
THANKS! for your quick reply.
What I see in the applications are unable to make connections.
The web application is getting this error "Method '~' of object '~' failed."
It looks like the SQL Connections have been trashed.
One Accounting product is getting an error about not being able to log onto
the database.
Another Accounting product on the same SQL Server is not allowing us to post
data to the database.
I can live with the Veritas issues but the Accounting folks are getting a bi
t nasty.
Have you heard of this before and how confident are you that SQL SP3a will p
ut us back to normal?
NC Beach Bum|||"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:DF20331F-C553-48C8-8D31-9A5745A81F24@.microsoft.com...
> Jeff,
> THANKS! for your quick reply.
> What I see in the applications are unable to make connections.
Try to add this in your connection string:
"Network Library=DBMSSOCN"|||Geoff,
I am going to try and update MDAC and the SQL Service Pack
1) Run the MDAC 2.8 install
2) Run the SQL SP3a install
Does this make sense to you and is this the order you would suggest?
Thanks! NC Beach Bum|||That is the correct order. It shouldn't hurt.
You should start checking connectivity an dsee what does and doesn't
connect. Start with IP connectivity (Ping) and then work on SQL
connectivity with query analyzer. Try local and remote from Query Analyzer
and see what happens. Find out what connectivity works and what does not.
If you can connect locally, what does 'SELECT @.@.Version' return? Windows
2003 will disable the IP stack for SQL without SP3a to protect from the
Slammer worm.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"NC Beach Bum" <anonymous@.discussions.microsoft.com> wrote in message
news:59DBF52D-F7AE-4ACD-81A4-639C8E7E4D95@.microsoft.com...
> Geoff,
> I am going to try and update MDAC and the SQL Service Pack
> 1) Run the MDAC 2.8 install
> 2) Run the SQL SP3a install
> Does this make sense to you and is this the order you would suggest?
> Thanks! NC Beach Bum

Monday, March 19, 2012

Help! getting errors when trying to connect to SQL Server Management Studio

Hi All,

I have Windows 2003 Server with MSSQL 2005 Standard.

I am able to connect via Windows Authentication, but when I try to change it to SQL Server Authentication with user 'sa' I'm then being prompted with the error msg:

A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
Here is the entire list of msgs that are showing up:

===================================

Cannot connect to SOLELL-QGL5PG9D.

===================================

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476

Server Name: SOLELL-QGL5PG9D
Error Number: 233
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Any pointers?

-Alon.
Hi,

didi you enable mixed authentication or did you just enable the Windows Authentication ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||Hi Jens,

I installed the MSSQL a week and a half ago, and I believe it was set to Mixed. I simply don't remember.
Is there a way to know?
Can it be changed to Mixed mode in the event that I missed that? or do I need to uninstall and re-install from scratch?

thanks,

-Alon.
|||Hi Jens,

Since I didn't have any database created yet, I've uninstalled MSSQL and Re-installed it.
This time, I made sure it was set to the Mixed Mode.
I don't know if there was a way to verify an early install or if there is a way to change from
Windows Auth Only to Mixed mode, but Uninstalling and Re-installing took only 30 minutes and I had no databases that I needed to check previously,. so that was my solution.

Thanks for the interest.

-Alon.
|||

Hi,

just for the completion of your answer, the authentication mode can be investigated by using the SQL Server Management Studio and right clicking on the server, choosing the properties and viewing the setting in the Security pane. If you don′t have any visual tool for editing this you can use the registry key

Default instance:
"HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"

to 2 for mixed-mode or 1 for integrated.

Have in mind that changing the setting will need a restart of the server to apply.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Hey,

I had this same issue. My MSSQL 2005 server was setup on a port other than the default 1433. Once I added the port number to the connect string, I was able to connect. ie.: SERVERNAME, 9999

Good Luck.

Monday, March 12, 2012

Help! getting errors when trying to connect to SQL Server Management Studio

Hi All,

I have Windows 2003 Server with MSSQL 2005 Standard.

I am able to connect via Windows Authentication, but when I try to change it to SQL Server Authentication with user 'sa' I'm then being prompted with the error msg:

===================================

Cannot connect to SOLELL-QGL5PG9D.

===================================

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476

Server Name: SOLELL-QGL5PG9D
Error Number: 233
Severity: 20
State: 0

Program Location:

Any pointers?

-Alon.
Hi,

didi you enable mixed authentication or did you just enable the Windows Authentication ?

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||Hi Jens,

thanks,

-Alon.
|||Hi Jens,

Thanks for the interest.

-Alon.
|||

Hi,

Default instance:
"HKEY_LOCAL_MACHINE\Software\Microsoft\MSSqlserver\MSSqlServer\LoginMode"

to 2 for mixed-mode or 1 for integrated.

Have in mind that changing the setting will need a restart of the server to apply.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||Hey,

I had this same issue. My MSSQL 2005 server was setup on a port other than the default 1433. Once I added the port number to the connect string, I was able to connect. ie.: SERVERNAME, 9999

Good Luck.

Friday, February 24, 2012

Help with Web Sync sql 2005 to sql express

Hello,

OK I finally got the subscriber connected to the IIS server for replication. I am now getting errors when trying to apply the snap shot. Below is the error? Did I setup the publication incorrectly by selecting replication with another sql 2005? Am I supposed to select something different when trying to replicate between slq 2005 and sql express?

Source: Merge Replication Provider
Number: -2147201001
Message: The schema script 'activities_2.sch' could not be propagated to the subscriber.
2005-08-24 20:52:35.920 Percent Complete: 0
2005-08-24 20:52:35.920 Category:NULL
Source: Microsoft SQL Native Client
Number: 1703
Message: Online index operations can only be performed in Enterprise edition of SQL Server.

'activities_2.sch' script

drop Table [dbo].[activities]
go
SET ANSI_PADDING ON
go

SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[activities](
[activity] [varchar](50) NOT NULL,
[billing] [bit] NOT NULL,
[category] [varchar](50) NULL,
[rowguid] [uniqueidentifier] ROWGUIDCOL NOT NULL CONSTRAINT [MSmerge_df_rowguid_77F8C0F06FB942A7B7206EF4GD99AD745] DEFAULT (newsequentialid())
)

GO
SET ANSI_NULLS OFF
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
go
SET QUOTED_IDENTIFIER ON
go
ALTER TABLE [dbo].[activities] ADD CONSTRAINT [PK_activities] PRIMARY KEY CLUSTERED
(
[activity] ASC
)WITH (SORT_IN_TEMPDB = OFF, ONLINE = OFF)
GO

I've experienced the same problem but am struggling with the bitwise syntax for disabling the XMLIndex schema option using sp_changemergearticle. Could you provide an example?

Also, as an alternative workaround during development I've been manually commenting out the problem index from the .dri and .sch files in the snapshot:

--WITH (SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, ONLINE = OFF)

Obviously it would better to fix the XMLIndex schema option than to have to do this everytime I create a new snapshot!

Thanks, STEVE

|||The current schema option should be something like: 0x04nnnnnn
To remove the XML index, make it 0x00nnnnnn and run snapshot again and sync (reinit).

If it is 0x07nnnnnn, then make it 0x03nnnnnn.
Basically you want to remove the 04 part in it.|||The current schema options on my tables is :

0x000000000C034FD1

I tried changing it to

0x000000000C030FD1

but that didn't work.

Any ideas?

|||The current schema option: 0x000000000C034FD1
New one to try: 0x0000000008034FD1|||This was a known problem with Express subscribers.
Which CTP are you using? This should be fixed in the further CTPs. Either try the next CTP or there is a workaround below:

Meanwhile you can workaround the issue by disabling the XMLIndex schema option (0x04000000) on the table articles.

Use sp_changemergearticle to change the schema_option to remove this and then the snapshot should be applied correctly.

Monday, March 26, 2012

Help! SQL errors after Win 2003 Upgrade

Monday, March 19, 2012

Help! getting errors when trying to connect to SQL Server Management Studio

Monday, March 12, 2012

Help! getting errors when trying to connect to SQL Server Management Studio

Friday, February 24, 2012

Help with Web Sync sql 2005 to sql express

Help with update forms

Blog Archive

About Me