Showing posts with label update. Show all posts
Showing posts with label update. Show all posts

Tuesday, March 27, 2012

Cannot remotely login to SQL Express since last windows update

Since today (after installing the latest Windows Updates !on my local machine!) I cannot login to a SQLExpress instance remotely; stating that it cannot find the server/instance.

The weird thing is: it only happens when I want to login to the non-default instance (sqlexpress 2005) (<IP>\<instance>).

When i'm using the default instance (msde 2000 or sqlexpress 2005 on another machine) (<IP>) it seems to work fine.

Does this have something to do with the windows updates, or is it just a coincedence?

Thanks in advance,

Remco RosThis is probably due to the update changed your setting. Just check your firewall on the server and put sqlbrowser.exe or UDP port 1434 to exception. Also make sure your sqlbrowser is running.|||we didn't install the updates on the server (yet) only on the client, so it must be a client thing.

Server:
Win 2003 / SQL Express 2005
Tcp/ip / named pipes: yes
sqlbrowser running
firewall exception on 1434udp 1433tcp.

tested on these client(s):
Local (without latest updates): CAN connect
XP Home with SQL Server Management studio (with lates windows updates): CANNOT connect
XP Pro with SQL Server Management studio Express (with lates windows updates): CANNOT connect
Win 2003 with SQL Server Management studio Express

(WITHOUT lates windows updates): CAN connect.

I see a pattern here...|||Are you sure your SQL Express listens on TCP port 1433 since your put 1433 in exception? What's the result if you run "telnet yourserver sql_tcp_port"? Can it connect? Could it be possible that IPSEC blocked the traffic between the problem machine if the IPSEC is on?

Tuesday, March 20, 2012

Cannot open file : C:\Program Files\Microsoft SQL Server\80\Tools\

Why is MICROSOFT not putting out any help on this topic. It is INCREDIBLY
frustrating not to have the documentation.
I'm runnig Win XP Pro w/update Service packs
SQL Server 2000 Developer sp3
I have done the following fruitlessly
Sent the error report when BOL fails because of hh.exe or hhctrl.ocx
Update the version of BOL
Modified the hhcolreg.dat to have the same value as the C:\Program
Files\Microsoft SQL Server\80\Tools\Books\sql80.col
Unregistered and registered the hhctrl.ocx ActiveX Control
LP
Hi
You may want to post the full error number and message. This may be a
corruption or a permissions issue. Also check that you are not restricted by
a group policy.
Try removing BOL and installing it in a different directory.
John
"LP" wrote:

> Why is MICROSOFT not putting out any help on this topic. It is INCREDIBLY
> frustrating not to have the documentation.
> I'm runnig Win XP Pro w/update Service packs
> SQL Server 2000 Developer sp3
>
> I have done the following fruitlessly
> Sent the error report when BOL fails because of hh.exe or hhctrl.ocx
> Update the version of BOL
> Modified the hhcolreg.dat to have the same value as the C:\Program
> Files\Microsoft SQL Server\80\Tools\Books\sql80.col
> Unregistered and registered the hhctrl.ocx ActiveX Control
> LP
sql

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.
If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:

>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:
>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterprise
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Cannot open Enterprise Manager

I have performed a windows update on the server and now i am presented with
an error when trying to open enterprise manager. The MMC cannot find the
file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterpris
e
Manager.msc
My sql server resides on D: and I have never had a problem opening SQL
Enterprise Manager. I can access the enterprise manager by adding the
snapin. Any ideas.If you are launching it from a program icon those are all
shortcuts. Right click on the icon and select properties and
check the path to your SQL Server Enterprise Manager.msc
file.
-Sue
On Mon, 7 Nov 2005 06:30:09 -0800, KMD
<KMD@.discussions.microsoft.com> wrote:

>I have performed a windows update on the server and now i am presented with
>an error when trying to open enterprise manager. The MMC cannot find the
>file C:\Program Files\Microsoft SQL Server\80\Tools\Bin\SQL Server Enterpri
se
>Manager.msc
>My sql server resides on D: and I have never had a problem opening SQL
>Enterprise Manager. I can access the enterprise manager by adding the
>snapin. Any ideas.

Sunday, March 11, 2012

Cannot Modify tables after Replication Switched off

If you run:
select replinfo from sysobjects
where name = 'yourtablename'
What comes back? If there is a 1, then update it to 0. If
it's not a 1 then I'll have a rethink!
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
"Adrian320" wrote:

> What if the number in sysobjects is 3 instead of 1, no problem?
> If I get the error message that ad hoc updates to sysobjects is not
> configured, how do I change that parameter.
> Thanks.
In Enterprise manager: Check "Allow modifications to be made directly to the
system catalogs" under Tools ->SQL Server Configuration Properties ->Server
Settings.
|||What if the number in sysobjects is 3 instead of 1, no problem?
If I get the error message that ad hoc updates to sysobjects is not
configured, how do I change that parameter.
Thanks.
"Paul Ibison" wrote:

> If you run:
> select replinfo from sysobjects
> where name = 'yourtablename'
> What comes back? If there is a 1, then update it to 0. If
> it's not a 1 then I'll have a rethink!
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>

Saturday, February 25, 2012

Cannot install SP1 on SQL Server 2005 (64bit)

Hi,

I'm having problems installing SP1 on one of our servers.

If I try to install the x64 version of SP1 setup says it can not update my server and I should use x86 version. Trying to install the x86 version results in the message I should use x64 version....

Any ideas?

Regards, Jan

What version of SQL do you have on the machine? x64 or x86? And when are you getting the error?

Thanks,
Sam Lester (MSFT)

|||

Hi Sam,

version is Microsoft SQL Server Standard Edition (64-bit). I get this error after doubleclicking the service pack .exe file.

Regards,

Jan

|||

OK, just to confirm what is on the box, can you go to Add/Remove Programs, click on change, and then on Report. This will show everything that the discovery process finds associated with SQL Server. This may help us figure out why the detection is giving you the error.

Also, can you supply the package name that you're trying to run?

Thanks,
Sam

|||

Hi Sam,

here is the report:


SIAM

The following components are installed on this server

MSSQLSERVER

Analysis Services

[Version: 9.00.1399.06 Edition: Standard Edition (64-bit) Patch level: 9.00.1399.06 Language: English (United States)]

Database Engine

[Version: 9.00.1399.06 Edition: Standard Edition (64-bit) Patch level: 9.00.1399.06 Language: English (United States)]

Common components

Integration Services

[Version: 9.00.1399.06 Edition: Standard Edition (64-bit) Patch level: 9.00.1399.06 Language: English (United States)]

Notification Services

[Version: 9.00.1399.06 Edition: Standard Edition (64-bit) Patch level: 9.00.1399.06 Language: English (United States)]

Workstation Components

[Version: 9.00.1399.06 Edition: Standard Edition (64-bit) Patch level: 9.00.1399.06 Language: English (United States)]


Regards,

Jan

|||

Great, thanks for posting the info! And to confirm, are you running this SP1 package:

SQLServer2005SP1-KB913090-x64-ENU.exe

from

http://www.microsoft.com/downloads/details.aspx?familyid=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&displaylang=en

Thanks,
Sam

|||

Hi,

no I didn't run this package but SQLServer2005SP1-KB913090-x64-ENU.exe (most of our server are german version).

With the englisch version installation worked - thanks for the great support.

Anyway, the error message is a bit misleading...

Regards,

Jan

Thursday, February 16, 2012

Cannot get notification after update

Hi,

I set up a notification service on a database update that works the first time I create it (with the instanceConfig.xml the ADF file, subscriptions, etc...) But when I update the instanceConfig.xml, I cannot get the notifications anymore, I don't understand why.

Does anyone know what happen or had the same problem?

Thank you,

Aurelie

I had the same (or, similar) problem.

In my case, it was caused by the fact that I added new elements into my classes in the adf file (subscription class, notification class, ect) where I thought they should belong.

The fact is, I should have added them at the END of each class, NOT somewhere in between the existing elements. When you rebuild your NS application, and your database tables' schemas are changed, somehow the app stops "understanding" the new schemas...

Sorry, English is not my native language, so it's a bit difficult for me to explain exactly what I mean...

Basically, if you add new elements to (or, remove old ones from) your NS files, AND you are sure that you have not missed the necessary modifications in any of the other parts of the program (such as modifying your SMI files, custom formatters - if you have any, etc.), the easiest way to make sure that your app will not be "broken" is to delete your NS database and recreate it again by going through the full cicle of building your NS app as you did the first time.

This way, you will be sure that the database objects will be created according to the latest schemas specified by you.

FYI: I actually went through a very time-consuming and kinda "painful" process of checking and modifying ALL of my NS-related files, and eventually I got it working again, but the next times I had to add new fields and/or delete the existing fields, I did it far simpler and faster (see above): delete the DBs, and recreate them afresh. Unless you already have your app running in production, I strongly recommend this simple approach.

|||Modifying certain classes in an SSNS application requires that the underlying tables be changed. Rather than attempting to modify the existing tables, the update process copies the existing table to an OLD table and creates an all new table for the modified class.

Look to see if you have any OLD tables in your SSNS database. You'll need to migrate the data manually to the new tables.

HTH...

Joe

Cannot get notification after update

Hi,

I set up a notification service on a database update that works the first time I create it (with the instanceConfig.xml the ADF file, subscriptions, etc...) But when I update the instanceConfig.xml, I cannot get the notifications anymore, I don't understand why.

Does anyone know what happen or had the same problem?

Thank you,

Aurelie

I had the same (or, similar) problem.

In my case, it was caused by the fact that I added new elements into my classes in the adf file (subscription class, notification class, ect) where I thought they should belong.

The fact is, I should have added them at the END of each class, NOT somewhere in between the existing elements. When you rebuild your NS application, and your database tables' schemas are changed, somehow the app stops "understanding" the new schemas...

Sorry, English is not my native language, so it's a bit difficult for me to explain exactly what I mean...

Basically, if you add new elements to (or, remove old ones from) your NS files, AND you are sure that you have not missed the necessary modifications in any of the other parts of the program (such as modifying your SMI files, custom formatters - if you have any, etc.), the easiest way to make sure that your app will not be "broken" is to delete your NS database and recreate it again by going through the full cicle of building your NS app as you did the first time.

This way, you will be sure that the database objects will be created according to the latest schemas specified by you.

FYI: I actually went through a very time-consuming and kinda "painful" process of checking and modifying ALL of my NS-related files, and eventually I got it working again, but the next times I had to add new fields and/or delete the existing fields, I did it far simpler and faster (see above): delete the DBs, and recreate them afresh. Unless you already have your app running in production, I strongly recommend this simple approach.

|||Modifying certain classes in an SSNS application requires that the underlying tables be changed. Rather than attempting to modify the existing tables, the update process copies the existing table to an OLD table and creates an all new table for the modified class.

Look to see if you have any OLD tables in your SSNS database. You'll need to migrate the data manually to the new tables.

HTH...

Joe

Friday, February 10, 2012

Cannot find select stored procedure wizard in SQL 2000

I was using the SQL 2000 stored procedure wizard to create stored
procedures. I can create insert, delete and update SPs however I am
not able to create the select SP. The wizard does not offer the option
of selecting "select" type SP. thank you for your replys

comprajHi

Select is not supported through the CREATE PROCEDURE wizard. Try using Query
Analyser and the CREATE PROCEDURE statement described in books online.

http://msdn.microsoft.com/library/d...create_4hk5.asp

If you require select statements for a given table you can right click the
table in object browser and script the select statement to a new window.

John

"compraj" <rajeshgambhir@.hotmail.com> wrote in message
news:b3cb283a.0310220207.12c76283@.posting.google.c om...
> I was using the SQL 2000 stored procedure wizard to create stored
> procedures. I can create insert, delete and update SPs however I am
> not able to create the select SP. The wizard does not offer the option
> of selecting "select" type SP. thank you for your replys
> compraj