Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts

Tuesday, March 20, 2012

Booi.ini switch

Hello,

I read a lot of artical but still can't understand.

I have SQL 2005 ent edition 32BIT on Windows 2003 Ent R2 32 bit.

I have 4GB on my machine.

What switch I need ton the boot.ini

/3GB

/Userva=2900

/PAE (is this only if I have more than 4GB?)

Thanks

KBA http://support.microsoft.com/kb/274750 for more infomation.|||

Thanks but this is for SQL 2000/7 and I need for SQL 2005,

Aslo I can't found there the /USERVA

|||

Idanle,

You need to look at the bottom of the support link doc Satya gave to you...

|||

PAE is useful for systems owning more than 4GB of RAM

/3GB limits the kernel space to just 1GB instead of 2GB to allow your applications to use up to 3GB instead of up to 2GB.

AWE is used by certain programs that support it (like SQLSRV05), usually along with PAE to provide your applications with more than 2GB of address space which is the norm.

Since your server is 4GB you should use /3GB if you believe the server won't slow down by limiting it to 1GB of kernel address space. PAE need not concern you for 4GB

|||

Thanks a lot

so if I have SQL 2005 on 4GB rammachine I need to use

/3GB /AWE

|||

If you want all your applications on the server (including SQL server) to use 3GB then use /3GB

If you want only SQL Server to use 3GB then use AWE

You're welcome

|||

Dear JohDas,

my server runs with Windows 2003 small business server sp2 and we use SQL 2005 workgroup edition sp1. The physical memory is 3.5 Gbytes, paging file 2-4 Gbytes. Also the server has two Intel Xeon cpus. This is a dedicated SQL server.

We dont get any memory erros but we monitored a poor performance (user transactions take longer to finish), so we want to allow SQL to use more memory, we are trying to figure out the correct configuration. Do you think the following setup for boot.ini is correct and adequate:

/3Gb /userva=2560 /AWE

Regards,

ZindrosH


|||

Hi ZindrosH,

the memory SQL Server reserves is different from what the OS keeps for itself. You could have 4 GB of RAM and have SQL Server using only 512MB of it due to bad configuration.

Use this query to see the configuration about the minimum and maximum memory that SQL Server uses:

SP_CONFIGURE ‘show advanced options’,1

GO

RECONFIGURE

GO

SP_CONFIGURE

GO

and change it accordingly to your needs

Cheers,

John

|||

Dear John,

we haven't set any specific values to min &max server memory. We use the default values.

Because the box has more than 2 Gbytes (it has 3.5 Gbytes) memory and SQL 2005 Workgroup edition might use up to 3 Gbytes we would like to let SQL to use more memory. To my knowledge, one way, is to set specific values to boot.ini file. I am not pretty sure what these values should be.

May be this: /3Gb /userva=2560 /AWE

or

May be this: /3Gb /userva=2560 /PAE

or any other combination or option ?

Because the server is out to production we do not have the chance to play with these values.

Regards,

ZindrosH

|||


PAE is only required for SQL Server to use more than 4 GB of physical memory - you don't need it

Generally, for a standalone SQL Server, AWE is preferable to 3GB as it allows only SQL Server to take advantage of more than 2GB of RAM

The account used for SQL services will have to be given Windows "lock pages in memory" administrative credentials.

and then running this query to set AWE and max server memory:

sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 3072
RECONFIGURE
GO

You should always keep at least 1 GB of RAM for the OS

For more info check this KB article: 274750 and SQL books online

|||

Dear John,

thank for your time and patience. I have read not only the links you provided but much more. Thats why I am confused....!

So, PAE is out.

Also since AWE is not supported for SQL 2005 Workgroup edition (I get a relative error when I try to set AWE from Management Studio), what remains is to use /3Gb and /userva=2560 to boot.ini. I guess, this setting will allow 2.5 Gbytes for all applications, including SQL and 1 Gbyte for OS.

What do you suggest, should I try this ?

ZindrosH

Booi.ini switch

Hello,

I read a lot of artical but still can't understand.

I have SQL 2005 ent edition 32BIT on Windows 2003 Ent R2 32 bit.

I have 4GB on my machine.

What switch I need ton the boot.ini

/3GB

/Userva=2900

/PAE (is this only if I have more than 4GB?)

Thanks

KBA http://support.microsoft.com/kb/274750 for more infomation.|||

Thanks but this is for SQL 2000/7 and I need for SQL 2005,

Aslo I can't found there the /USERVA

|||

Idanle,

You need to look at the bottom of the support link doc Satya gave to you...

|||

PAE is useful for systems owning more than 4GB of RAM

/3GB limits the kernel space to just 1GB instead of 2GB to allow your applications to use up to 3GB instead of up to 2GB.

AWE is used by certain programs that support it (like SQLSRV05), usually along with PAE to provide your applications with more than 2GB of address space which is the norm.

Since your server is 4GB you should use /3GB if you believe the server won't slow down by limiting it to 1GB of kernel address space. PAE need not concern you for 4GB

|||

Thanks a lot

so if I have SQL 2005 on 4GB rammachine I need to use

/3GB /AWE

|||

If you want all your applications on the server (including SQL server) to use 3GB then use /3GB

If you want only SQL Server to use 3GB then use AWE

You're welcome

|||

Dear JohDas,

my server runs with Windows 2003 small business server sp2 and we use SQL 2005 workgroup edition sp1. The physical memory is 3.5 Gbytes, paging file 2-4 Gbytes. Also the server has two Intel Xeon cpus. This is a dedicated SQL server.

We dont get any memory erros but we monitored a poor performance (user transactions take longer to finish), so we want to allow SQL to use more memory, we are trying to figure out the correct configuration. Do you think the following setup for boot.ini is correct and adequate:

/3Gb /userva=2560 /AWE

Regards,

ZindrosH


|||

Hi ZindrosH,

the memory SQL Server reserves is different from what the OS keeps for itself. You could have 4 GB of RAM and have SQL Server using only 512MB of it due to bad configuration.

Use this query to see the configuration about the minimum and maximum memory that SQL Server uses:

SP_CONFIGURE ‘show advanced options’,1

GO

RECONFIGURE

GO

SP_CONFIGURE

GO

and change it accordingly to your needs

Cheers,

John

|||

Dear John,

we haven't set any specific values to min &max server memory. We use the default values.

Because the box has more than 2 Gbytes (it has 3.5 Gbytes) memory and SQL 2005 Workgroup edition might use up to 3 Gbytes we would like to let SQL to use more memory. To my knowledge, one way, is to set specific values to boot.ini file. I am not pretty sure what these values should be.

May be this: /3Gb /userva=2560 /AWE

or

May be this: /3Gb /userva=2560 /PAE

or any other combination or option ?

Because the server is out to production we do not have the chance to play with these values.

Regards,

ZindrosH

|||


PAE is only required for SQL Server to use more than 4 GB of physical memory - you don't need it

Generally, for a standalone SQL Server, AWE is preferable to 3GB as it allows only SQL Server to take advantage of more than 2GB of RAM

The account used for SQL services will have to be given Windows "lock pages in memory" administrative credentials.

and then running this query to set AWE and max server memory:

sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 3072
RECONFIGURE
GO

You should always keep at least 1 GB of RAM for the OS

For more info check this KB article: 274750 and SQL books online

|||

Dear John,

thank for your time and patience. I have read not only the links you provided but much more. Thats why I am confused....!

So, PAE is out.

Also since AWE is not supported for SQL 2005 Workgroup edition (I get a relative error when I try to set AWE from Management Studio), what remains is to use /3Gb and /userva=2560 to boot.ini. I guess, this setting will allow 2.5 Gbytes for all applications, including SQL and 1 Gbyte for OS.

What do you suggest, should I try this ?

ZindrosH

Sunday, March 11, 2012

Blocking SQL server by machine name?

Hello,
I've Windows 2000 server with SQL 2000 server running.
I have a SQL user (let's call miniSa) which is mostly "sa" on one SQL box.
And that account is used to all over the places (VB apps,Web app, DTS
connection). Now I know that a person shouldn't be access to the SQL box bu
t
he does using the account. Only way I can track down him is from SQL profil
e
with his machine name.
Is there a way that I can block the SQL box only from a specific machine nam
e?
Thank you in advance.
SangHun"SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
news:F23A84F9-6350-4BE8-B002-62A9BD320BCB@.microsoft.com...
> I've Windows 2000 server with SQL 2000 server running.
> I have a SQL user (let's call miniSa) which is mostly "sa" on one SQL box.
> And that account is used to all over the places (VB apps,Web app, DTS
> connection). Now I know that a person shouldn't be access to the SQL box
but
> he does using the account. Only way I can track down him is from SQL
profile
> with his machine name.
> Is there a way that I can block the SQL box only from a specific machine
name?
It's kind of ugly, but you could do TCP/IP filtering on the server level and
block the IP address of the computer that your "SQL user" uses. A better way
would be a review of the security implementation, eliminate this commonly
used account and implement Windows Authentication with nt group membership.
Steve|||Thanks for the reply Steve.
Using TCP/IP Filtering is not an option because of DHCP server. I may use
MAC address but that way that user may not use all the apps in the server.
I
don't want that happen either. I want just SQL server databases access
denied from the PC.
I will work on the whole problem but I need some time and ofcourse runing
several projects, support developers, and admin issues......tough.
Any other suggestions?
SangHun
"Steve Thompson" wrote:

> "SangHunJung" <SangHunJung@.discussions.microsoft.com> wrote in message
> news:F23A84F9-6350-4BE8-B002-62A9BD320BCB@.microsoft.com...
> but
> profile
> name?
> It's kind of ugly, but you could do TCP/IP filtering on the server level a
nd
> block the IP address of the computer that your "SQL user" uses. A better w
ay
> would be a review of the security implementation, eliminate this commonly
> used account and implement Windows Authentication with nt group membership
.
> Steve
>
>|||
> I will work on the whole problem but I need some time and ofcourse runing
> several projects, support developers, and admin issues......tough.
> Any other suggestions?
Yes, I still recommend my previous suggestion, some times there are no
+easy+ solutions. Sorry.
Steve
[vbcol=seagreen]
commonly[vbcol=seagreen]
membership.|||You can use IPSec to block a particular machine from contacting another
machine on the network.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Blocking MS Access from linking tables...

Good morning...
I have an Access front end that uses SQL Server linked tables. SQL Server
uses Windows authentication. I have one Windows group that all Access users
are a member of. I added that group to SQL Server logins and gave it
public, datareader, and datawriter rights to the one database that's used.
My front end is locked down, but I want to stop users from creating a new
.mdb and linking SQL Server tables through DSNs or ADO connections or even
just importing the links from the actual front end.. I've tried setting the
"denydatareader" security policy - that keeps the SQL tables from being seen
in the import/link list- but also blocks read rights from the actual front
end database. I could set an Access database password on the front end to
block importing the links, but that only solves one of the three problems
and I want to stay away from Access security altogether.
Is there a way to stop users from creating their own DSNs or connection
objects or linking tables while still using Windows authentication?
Thanks.
Matthew Wells
MWells@.FirstByte.netNo. If you're using Windows authentication, and have granted
users/roles permissions on the base tables, then they can get at the
data no matter what tool they use. An alternative would be to revoke
permissions to public on the tables, and create an Access application
that does not use linked tables, but instead uses pass-through queries
to execute stored procedures. This is a lot more work since you'll
need to create an unbound FE, but it can be done. Only users who are
comfortable working with stored procedures would be able to get at the
data. Another option would be application roles, but they are a really
poor choice for linked table apps. see
http://support.microsoft.com/defaul...;EN-US;Q229564.
--Mary
On Thu, 28 Oct 2004 13:54:05 GMT, "Matthew Wells"
<MWells@.FirstByte.net> wrote:

>Good morning...
>I have an Access front end that uses SQL Server linked tables. SQL Server
>uses Windows authentication. I have one Windows group that all Access user
s
>are a member of. I added that group to SQL Server logins and gave it
>public, datareader, and datawriter rights to the one database that's used.
>My front end is locked down, but I want to stop users from creating a new
>.mdb and linking SQL Server tables through DSNs or ADO connections or even
>just importing the links from the actual front end.. I've tried setting th
e
>"denydatareader" security policy - that keeps the SQL tables from being see
n
>in the import/link list- but also blocks read rights from the actual front
>end database. I could set an Access database password on the front end to
>block importing the links, but that only solves one of the three problems
>and I want to stay away from Access security altogether.
>Is there a way to stop users from creating their own DSNs or connection
>objects or linking tables while still using Windows authentication?
>Thanks.
>Matthew Wells
>MWells@.FirstByte.net
>|||I read that article. It seems to apply only to ADO conenctions. Aren't
linked tables DAO? Does connection pooling work the same way? This is a
database that was converted from Access to SQL Server. We have to lock down
the data from any outside attempts to get it. I don't want to use SQL
authentication because I don't want to maintain two sets of security logins.
I know that using an Access form can create multiple SPIDs on SQL Server
(combo box rowsources et al). What is the downside of using Application
Roles?
Thanks.
Matthew Wells
MWells@.FirstFleet.com
"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
news:vh62o051su3gi6fsaljgvmh1me12b8fu8p@.
4ax.com...
> No. If you're using Windows authentication, and have granted
> users/roles permissions on the base tables, then they can get at the
> data no matter what tool they use. An alternative would be to revoke
> permissions to public on the tables, and create an Access application
> that does not use linked tables, but instead uses pass-through queries
> to execute stored procedures. This is a lot more work since you'll
> need to create an unbound FE, but it can be done. Only users who are
> comfortable working with stored procedures would be able to get at the
> data. Another option would be application roles, but they are a really
> poor choice for linked table apps. see
> http://support.microsoft.com/defaul...;EN-US;Q229564.
> --Mary
> On Thu, 28 Oct 2004 13:54:05 GMT, "Matthew Wells"
> <MWells@.FirstByte.net> wrote:
>
Server[vbcol=seagreen]
users[vbcol=seagreen]
used.[vbcol=seagreen]
even[vbcol=seagreen]
the[vbcol=seagreen]
seen[vbcol=seagreen]
front[vbcol=seagreen]
to[vbcol=seagreen]
>|||Yes, connection pooling works the same way. If you are serious about
locking down the SQL Server database, then DO NOT use Access as a
front-end unless you use it in an unbound scenario as I described
below. You will need to revoke or deny permissions on the tables and
create parameterized stored procedures for all DML operations so that
users can interact with the data only through your stored procedures,
which are executed using a least-priviledged account.
Application roles are intrinsically insecure because you must store
the password that activates them on the client, where it can be
discovered by a determined attacker. If you create an unbound
application that executes under least priviledges, then there likely
won't be much penalty for using them (other than performance) or much
harm if the password is uncovered, but then there's not much benefit,
either. Using Windows authentication is more secure than SQL logins,
and if all users belong to roles that have extremely restricted
permissions that only allow them to execute parameterized stored
procedures, then that's about the best you can do. You can also
provide additional verification and validation in your stored
procedure code (for example, only allowing users to access rows that
they "own").
There is code and discussion of the techniques involved in writing an
unbound Access application in the book described in my sig. It's a lot
of work, but if security is a priority then you have to do it. Access
was designed to be easy to use, not secure.
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Mon, 01 Nov 2004 14:29:21 GMT, "Matthew Wells"
<MWells@.FirstByte.net> wrote:

>I read that article. It seems to apply only to ADO conenctions. Aren't
>linked tables DAO? Does connection pooling work the same way? This is a
>database that was converted from Access to SQL Server. We have to lock dow
n
>the data from any outside attempts to get it. I don't want to use SQL
>authentication because I don't want to maintain two sets of security logins
.
>I know that using an Access form can create multiple SPIDs on SQL Server
>(combo box rowsources et al). What is the downside of using Application
>Roles?
>Thanks.
>Matthew Wells
>MWells@.FirstFleet.com
>"Mary Chipman" <mchip@.online.microsoft.com> wrote in message
> news:vh62o051su3gi6fsaljgvmh1me12b8fu8p@.
4ax.com...
>Server
>users
>used.
>even
>the
>seen
>front
>to
>

Wednesday, March 7, 2012

Block Size on Hardware for SQL Server 2000 on Windows enterprise 2

Any idea of best block size for hardware for SQL server 2000 on windows
enterprise 2003 edition?
Thanks
- NT
>
> Any idea of best block size for hardware for SQL server 2000 on windows
> enterprise 2003 edition?
> Thanks
> --
> - NT
According to:
http://www.microsoft.com/technet/pro...n/instant.mspx
Select the Appropriate Allocation Unit Size (ALU)
"Consider matching the file system ALU to the block size of the application
you are using. If SQL Server is using a 4 KB block size, when you format a
file system on a new disk drive, launch Disk Administrator, create the
partition, commit the partition changes, select Format, and then set the
ALU to 4096 bytes. Matching the file system block sizes can improve the
efficiency of the disk transfers when you use the application. For more ALU
size options, use the format command from the command prompt versus the
Disk Administrator tool."
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Block Port 1433 on windows 2000 server

Hi
I have a question regarding the SQL Server(SQL Server 7) port 1433.
Some body is trying to hack into our Windows 2000 server through port
1433. Is there a way i can close this port? I tried using a tool
called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
when we run netstat, it still looks like they are able to connect to
the server using port 1433. Has anyone come across this problem? I
would appreciate it very much if somebody could send in any
suggestions regarding this.
Thanks,
AnnIPSec can be used or a Personal Firewall.
813878 How to Block Specific Network Protocols and Ports by Using IPSec
http://support.microsoft.com/?id=813878
If this computer is on the internet it should be behind a firewall. By
default a firewall will block all incoming traffic, unless you specifically
allow it.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||The issue isn't really "closing ports" - it's blocking access to them.
Are you using ISA? If not, you need a firewall. I'd pick up a cheap and
cheerful firewall appliance - I like the NetGear FR114P.
Ann wrote:
> Hi
> I have a question regarding the SQL Server(SQL Server 7) port 1433.
> Some body is trying to hack into our Windows 2000 server through port
> 1433. Is there a way i can close this port? I tried using a tool
> called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
> when we run netstat, it still looks like they are able to connect to
> the server using port 1433. Has anyone come across this problem? I
> would appreciate it very much if somebody could send in any
> suggestions regarding this.
> Thanks,
> Ann|||On 12 Jul 2004 14:56:40 -0700, nsajus@.yahoo.com (Ann) wrote:

>I have a question regarding the SQL Server(SQL Server 7) port 1433.
>Some body is trying to hack into our Windows 2000 server through port
>1433. Is there a way i can close this port?
Don't open it in your firewall. Or any other port you don't want
accessed.
Jeff|||Hi
This sounds like your SQL Server is not behind the firewall or as the others
have suggested the firewall is not configured correctly.
How do you know someone is trying to access the SQL Server? If this is being
reported from the firewall then it may be because it is dropping it!!
If you are not using windows only authentication, then make sure that you
have a strong sa password.You could run the Microsoft Baseline Security
Analyzer http://www.microsoft.com/technet/se...s/mbsahome.mspx to
make sure it is configured sensibly. I would also look at running IIS
lockdown on any webserver
http://www.microsoft.com/security/g...odtech/IIS.mspx
Check out the advice on:
http://www.microsoft.com/sql/techin...t.aspx?tabid=24
John
"Ann" <nsajus@.yahoo.com> wrote in message
news:cca0635f.0407121356.55ef3590@.posting.google.com...
> Hi
> I have a question regarding the SQL Server(SQL Server 7) port 1433.
> Some body is trying to hack into our Windows 2000 server through port
> 1433. Is there a way i can close this port? I tried using a tool
> called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
> when we run netstat, it still looks like they are able to connect to
> the server using port 1433. Has anyone come across this problem? I
> would appreciate it very much if somebody could send in any
> suggestions regarding this.
> Thanks,
> Ann|||Hi Ann.
The easy one is to buy a firewall box from your local computer store
or If you are using a windows server 2003 use the firewall insite
windows server 2003 (ICF). Click on the link to see how to enable it.
http://www.microsoft.com/resources/...le_firewall.asp
After you either buy a firewall box or enabled ICF on your server then
try this link:
- www.grc.com
- Click ShieldsUp
- Roll down to HOT SPOT and click again shieldsUp
- click proceed
- write 1433 in the text field and click "User Specified Custom Port
Probe"
- See if its stealth.
- You can then click common ports to see if the common ports are
stealth or click all service ports to see if other ports are
open...(The best is if every one are green and not red)
Hope you understand this and solve this problem..
Danni, MCP[vbcol=seagreen]|||Sorry. i forgot it was a Windows 2000 server. There is not a ICF.
You could also get a software firewall like ZoneAlarm? If the server
is in a big firm it mabye better with a firewall box.
Danni|||On 13 Jul 2004 01:22:45 -0700, dev@.euro-consult.dk wrote:

>Sorry. i forgot it was a Windows 2000 server. There is not a ICF.
>You could also get a software firewall like ZoneAlarm?
For home machines, that is fine, as would be the Sygate product. For
anything used 'in anger' this is a risky solution.

>If the server is in a big firm it mabye better with a firewall box.
In any situation where the data and system availability/integrity is
valuable, a hardware firewall solution is the only way to go.

Block Port 1433 on windows 2000 server

Hi
I have a question regarding the SQL Server(SQL Server 7) port 1433.
Some body is trying to hack into our Windows 2000 server through port
1433. Is there a way i can close this port? I tried using a tool
called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
when we run netstat, it still looks like they are able to connect to
the server using port 1433. Has anyone come across this problem? I
would appreciate it very much if somebody could send in any
suggestions regarding this.
Thanks,
Ann
IPSec can be used or a Personal Firewall.
813878 How to Block Specific Network Protocols and Ports by Using IPSec
http://support.microsoft.com/?id=813878
If this computer is on the internet it should be behind a firewall. By
default a firewall will block all incoming traffic, unless you specifically
allow it.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||The issue isn't really "closing ports" - it's blocking access to them.
Are you using ISA? If not, you need a firewall. I'd pick up a cheap and
cheerful firewall appliance - I like the NetGear FR114P.
Ann wrote:
> Hi
> I have a question regarding the SQL Server(SQL Server 7) port 1433.
> Some body is trying to hack into our Windows 2000 server through port
> 1433. Is there a way i can close this port? I tried using a tool
> called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
> when we run netstat, it still looks like they are able to connect to
> the server using port 1433. Has anyone come across this problem? I
> would appreciate it very much if somebody could send in any
> suggestions regarding this.
> Thanks,
> Ann
|||On 12 Jul 2004 14:56:40 -0700, nsajus@.yahoo.com (Ann) wrote:

>I have a question regarding the SQL Server(SQL Server 7) port 1433.
>Some body is trying to hack into our Windows 2000 server through port
>1433. Is there a way i can close this port?
Don't open it in your firewall. Or any other port you don't want
accessed.
Jeff
|||Hi
This sounds like your SQL Server is not behind the firewall or as the others
have suggested the firewall is not configured correctly.
How do you know someone is trying to access the SQL Server? If this is being
reported from the firewall then it may be because it is dropping it!!
If you are not using windows only authentication, then make sure that you
have a strong sa password.You could run the Microsoft Baseline Security
Analyzer http://www.microsoft.com/technet/sec.../mbsahome.mspx to
make sure it is configured sensibly. I would also look at running IIS
lockdown on any webserver
http://www.microsoft.com/security/gu...dtech/IIS.mspx
Check out the advice on:
http://www.microsoft.com/sql/techinf...ty/default.asp
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=24
John
"Ann" <nsajus@.yahoo.com> wrote in message
news:cca0635f.0407121356.55ef3590@.posting.google.c om...
> Hi
> I have a question regarding the SQL Server(SQL Server 7) port 1433.
> Some body is trying to hack into our Windows 2000 server through port
> 1433. Is there a way i can close this port? I tried using a tool
> called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
> when we run netstat, it still looks like they are able to connect to
> the server using port 1433. Has anyone come across this problem? I
> would appreciate it very much if somebody could send in any
> suggestions regarding this.
> Thanks,
> Ann
|||Hi Ann.
The easy one is to buy a firewall box from your local computer store
or If you are using a windows server 2003 use the firewall insite
windows server 2003 (ICF). Click on the link to see how to enable it.
http://www.microsoft.com/resources/d...e_firewall.asp
After you either buy a firewall box or enabled ICF on your server then
try this link:
- www.grc.com
- Click ShieldsUp
- Roll down to HOT SPOT and click again shieldsUp
- click proceed
- write 1433 in the text field and click "User Specified Custom Port
Probe"
- See if its stealth.
- You can then click common ports to see if the common ports are
stealth or click all service ports to see if other ports are
open...(The best is if every one are green and not red)
Hope you understand this and solve this problem..
Danni, MCP[vbcol=seagreen]
|||Sorry. i forgot it was a windows 2000 server. There is not a ICF.
You could also get a software firewall like ZoneAlarm? If the server
is in a big firm it mabye better with a firewall box.
Danni
|||On 13 Jul 2004 01:22:45 -0700, dev@.euro-consult.dk wrote:

>Sorry. i forgot it was a windows 2000 server. There is not a ICF.
>You could also get a software firewall like ZoneAlarm?
For home machines, that is fine, as would be the Sygate product. For
anything used 'in anger' this is a risky solution.

>If the server is in a big firm it mabye better with a firewall box.
In any situation where the data and system availability/integrity is
valuable, a hardware firewall solution is the only way to go.

Block Port 1433 on windows 2000 server

Hi

I have a question regarding the SQL Server(SQL Server 7) port 1433.
Some body is trying to hack into our Windows 2000 server through port
1433. Is there a way i can close this port? I tried using a tool
called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
when we run netstat, it still looks like they are able to connect to
the server using port 1433. Has anyone come across this problem? I
would appreciate it very much if somebody could send in any
suggestions regarding this.

Thanks,
AnnThe issue isn't really "closing ports" - it's blocking access to them.
Are you using ISA? If not, you need a firewall. I'd pick up a cheap and
cheerful firewall appliance - I like the NetGear FR114P.

Ann wrote:
> Hi
> I have a question regarding the SQL Server(SQL Server 7) port 1433.
> Some body is trying to hack into our Windows 2000 server through port
> 1433. Is there a way i can close this port? I tried using a tool
> called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
> when we run netstat, it still looks like they are able to connect to
> the server using port 1433. Has anyone come across this problem? I
> would appreciate it very much if somebody could send in any
> suggestions regarding this.
> Thanks,
> Ann|||On 12 Jul 2004 14:56:40 -0700, nsajus@.yahoo.com (Ann) wrote:

>I have a question regarding the SQL Server(SQL Server 7) port 1433.
>Some body is trying to hack into our Windows 2000 server through port
>1433. Is there a way i can close this port?

Don't open it in your firewall. Or any other port you don't want
accessed.

Jeff|||Hi

This sounds like your SQL Server is not behind the firewall or as the others
have suggested the firewall is not configured correctly.

How do you know someone is trying to access the SQL Server? If this is being
reported from the firewall then it may be because it is dropping it!!

If you are not using windows only authentication, then make sure that you
have a strong sa password.You could run the Microsoft Baseline Security
Analyzer http://www.microsoft.com/technet/se...s/mbsahome.mspx to
make sure it is configured sensibly. I would also look at running IIS
lockdown on any webserver
http://www.microsoft.com/security/g...odtech/IIS.mspx

Check out the advice on:
http://www.microsoft.com/sql/techin...ity/default.asp
http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=24

John

"Ann" <nsajus@.yahoo.com> wrote in message
news:cca0635f.0407121356.55ef3590@.posting.google.c om...
> Hi
> I have a question regarding the SQL Server(SQL Server 7) port 1433.
> Some body is trying to hack into our Windows 2000 server through port
> 1433. Is there a way i can close this port? I tried using a tool
> called Ipsecpol.exe ( Internet Protocol Security Policies Tool). But
> when we run netstat, it still looks like they are able to connect to
> the server using port 1433. Has anyone come across this problem? I
> would appreciate it very much if somebody could send in any
> suggestions regarding this.
> Thanks,
> Ann|||Hi Ann.

The easy one is to buy a firewall box from your local computer store
or If you are using a windows server 2003 use the firewall insite
windows server 2003 (ICF). Click on the link to see how to enable it.
http://www.microsoft.com/resources/...le_firewall.asp

After you either buy a firewall box or enabled ICF on your server then
try this link:
- www.grc.com
- Click ShieldsUp
- Roll down to HOT SPOT and click again shieldsUp
- click proceed
- write 1433 in the text field and click "User Specified Custom Port
Probe"
- See if its stealth.
- You can then click common ports to see if the common ports are
stealth or click all service ports to see if other ports are
open...(The best is if every one are green and not red)

Hope you understand this and solve this problem..

Danni, MCP
> >I have a question regarding the SQL Server(SQL Server 7) port 1433.
> >Some body is trying to hack into our Windows 2000 server through port
> >1433. Is there a way i can close this port?|||Sorry. i forgot it was a windows 2000 server. There is not a ICF.
You could also get a software firewall like ZoneAlarm? If the server
is in a big firm it mabye better with a firewall box.

Danni|||On 13 Jul 2004 01:22:45 -0700, dev@.euro-consult.dk wrote:

>Sorry. i forgot it was a windows 2000 server. There is not a ICF.
>You could also get a software firewall like ZoneAlarm?

For home machines, that is fine, as would be the Sygate product. For
anything used 'in anger' this is a risky solution.

>If the server is in a big firm it mabye better with a firewall box.

In any situation where the data and system availability/integrity is
valuable, a hardware firewall solution is the only way to go.

Saturday, February 25, 2012

BLOB Merge Replication

Hi,

I have setup a Merge Replication between a SQL Server 2005 and a SQL Server Mobile using native C++ code in Windows CE 5. Replication of normal data types (nvarchar, ints etc) works great, but when I try to replicate a blob about 1.5 MB the performance is awful. The download phase seems to be quick while the applytime (printed in debugger) when the database on my CE device is updated is about 3 minutes for 1.5MB binary data which is unacceptable since the database gets locked up during the applytime. The BLOB column is defined as image data type which shall hold up to 1GB data. I have tried to disable compression during replication, but it doesnt matter. Does anyone have some experience of using merge replication with blobs in SQL Server Mobile?

My Idea was to use merge replication as a way to transfer CAB-files for installation on the Windows CE 5 device by storing them as BLOB:s, but the bad performance may make it impossible.

Ideas? Anyone?

Best regards

Johan Johansson

I'm appending the debug output from the merge replication of the table containing the 1.5 MB BLOB.

SQLCECA30: Client Agent Log Start --
SQLCECA30: 08/23/2006-16:37:41 CSSCEMerge::SingleRun id=0 hr=0 bread=8027251 bwritten=273 c_urows=0 c_drows=0 s_urows=5 s_drows=0 md_n=0 md_c=0 md_r=0 app=mpsim.exe
SQLCECA30: 08/23/2006-16:37:41 CSSCEMerge::Run totalsynctime=222 uploadtime=371 applytime=217185 id=0 publisher='se-cwo-ddb-1' publication='Software' initialsync=1 bread=8027251 bwritten=273 c_urows=0 c_drows=0 s_urows=5 s_drows=0 loops=1 app=mpsim.exe

|||

About the only thing you can do is to factor out the BLOB itself into a related table. For example, let's say right now you have a table called "Orders" which has 10 columns, one of which is a customer signature (image column in SQL Mobile). Every time any column in the orders table is updated, the whole row is replicated, including the image. It would be more efficient to have an Orders table and a separate OrderSignatures table, related by a foreign key.

Darren

|||

Yes, thank you for the suggestion.

I must say that I'm dissapointed in the performance. I mean 1.5 MB binary data is not alot in these days and it is almost impossible to handle for SQL Server Mobile in a merge replication. Can I expect the same bad performance when I replicate alot of rows (lets say 3000) with more ordinary data (say a few columns with ints and varchar(50)) or is this performance problem only related to dealing with BLOBs?

Johan

|||

Johan,

I was thinking about your post some more and it occurs to me that you are trying to solve the problem of automatically downloading CAB files

from the server to the CE5 device. I also frequently have this requirement when a mobile app must be automatically updating. There are some

great samples (they are not native code, but you can get the idea of how to do this) of auto-updating by downloading CABs to the device at:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/AutoUpdater.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/AUTD_Functionality_NETCF_WebServices.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetcomp/html/DeploymentPatterns.asp

Regards,

Darren

|||

Thank you Darren,

I will have a look at the documents before I decide how I'm going to implement this.

Best regards

Johan

Blob data

Can someone please give me an example in C# on how to retrieve an Image from a Table and store i into a Picture box on a windows form? In addition, how to insert a blob record into a table as well.Reading BLOBs from SQL Server and display it inaWindows FormPictureBox
http://www.akadia.com/services/dotnet_load_blob.html|||Does any one have an example that they have used and written themselves? This example is very confusing.|||Check the code in the following article. It is from the Microsoft Knowledge base article.
http://www.kbalertz.com/Feedback_326502.aspx|||Just in case the above article doesn't suffice your requirement, let me know and I shall post the code written by me.

Friday, February 24, 2012

Blaster Worm Patch incompatibility with SQL 2k

I have heard of a couple of instances when the MS Blaster
patch is applied to a SQL 2k server, the server then has
problems booting back into Windows 2000. I have also
heard that MS PSS is aware of this issue, but information
hasn't come out on it yet.
Does anyone know what the incompatibility is between the
MS Blaster Worm fix and SQL Server 2000 on a Windows 2000
server? If so, please let me know.
Thanks,
DaveHI John,
Thanks for the offer. I did see the RAS alert yesterday.
The SQL server / MS Blaster patch incompatibility was
mentioned to a colleague of mine by PSS last night, after
he applied the patch and couldn't get the SQL server to
boot into Windows correctly. It may be something that
hasnt officially been communicated from MS yet maybe.
Thanks,
Dave
>--Original Message--
>I subscribe to the microsoft security bulletins and
>according to the one I received yesterday that flaw in
>their patch has to do with RAS not SQL. I can froward
the
>email directly to you if you wish.
>JOhn
>
>>--Original Message--
>>I have heard of a couple of instances when the MS
Blaster
>>patch is applied to a SQL 2k server, the server then has
>>problems booting back into Windows 2000. I have also
>>heard that MS PSS is aware of this issue, but
information
>>hasn't come out on it yet.
>>Does anyone know what the incompatibility is between the
>>MS Blaster Worm fix and SQL Server 2000 on a Windows
2000
>>server? If so, please let me know.
>>Thanks,
>>Dave
>>.
>.
>|||I've had the patch installed for a month and haven't seen a problem.
A question on your wording. Is the problem that Windows won't boot after
the patch is installed on a Windows system that is used as a SQL Server, or
that SQL Server won't start on a Windows system that has the patch
installed?
--
Hal Berenson, SQL Server MVP
True Mountain Group LLC
"Dave" <dnajac@.ezecastlesoftware.com> wrote in message
news:00ad01c3627c$041779e0$a301280a@.phx.gbl...
> HI John,
> Thanks for the offer. I did see the RAS alert yesterday.
> The SQL server / MS Blaster patch incompatibility was
> mentioned to a colleague of mine by PSS last night, after
> he applied the patch and couldn't get the SQL server to
> boot into Windows correctly. It may be something that
> hasnt officially been communicated from MS yet maybe.
> Thanks,
> Dave
> >--Original Message--
> >I subscribe to the microsoft security bulletins and
> >according to the one I received yesterday that flaw in
> >their patch has to do with RAS not SQL. I can froward
> the
> >email directly to you if you wish.
> >
> >JOhn
> >
> >
> >
> >>--Original Message--
> >>I have heard of a couple of instances when the MS
> Blaster
> >>patch is applied to a SQL 2k server, the server then has
> >>problems booting back into Windows 2000. I have also
> >>heard that MS PSS is aware of this issue, but
> information
> >>hasn't come out on it yet.
> >>
> >>Does anyone know what the incompatibility is between the
> >>MS Blaster Worm fix and SQL Server 2000 on a Windows
> 2000
> >>server? If so, please let me know.
> >>
> >>Thanks,
> >>Dave
> >>.
> >>
> >.
> >|||What's a coincidence! One of my SQL boxes is having a similar problem.
This is a production server hosting SQL 2K as a backend for IIS on another
box. The O/S is W2K; both W2K and SQL2K are with most current SP and
patches. Starting about a month ago I lost connection to the box after I
restarted it. All production servers are at a data center so I had to drive
to the data center and did a power-off, power-on. When I arrived I saw a
DOS prompt blinking on the screen. That's it. It seemed that the box was
able to shut down SQL but failed to startup the OS. It happens twice to
this box so we are planning to rebuild this box. We don't want to drive to
the data center in the midnight just to cold boot the server. Can anyone at
MS verify this?
BTW, I have 5 SQL boxes and just one has this problem.
"Dave" <dnajac@.ezecastlesoftware.com> wrote in message
news:0a1601c36323$d9ae2660$a501280a@.phx.gbl...
> The issue that I heard of was that once this patch was
> applied to a Windows 2000 server running SQL 2000, upon
> reboot the Windows OS woould not complete startup
> successfully due to a logical disk error during the
> startup of Windows 2000.
> >--Original Message--
> >I've had the patch installed for a month and haven't seen
> a problem.
> >
> >A question on your wording. Is the problem that Windows
> won't boot after
> >the patch is installed on a Windows system that is used
> as a SQL Server, or
> >that SQL Server won't start on a Windows system that has
> the patch
> >installed?
> >
> >--
> >Hal Berenson, SQL Server MVP
> >True Mountain Group LLC
> >
> >
> >"Dave" <dnajac@.ezecastlesoftware.com> wrote in message
> >news:00ad01c3627c$041779e0$a301280a@.phx.gbl...
> >> HI John,
> >>
> >> Thanks for the offer. I did see the RAS alert
> yesterday.
> >> The SQL server / MS Blaster patch incompatibility was
> >> mentioned to a colleague of mine by PSS last night,
> after
> >> he applied the patch and couldn't get the SQL server to
> >> boot into Windows correctly. It may be something that
> >> hasnt officially been communicated from MS yet maybe.
> >>
> >> Thanks,
> >> Dave
> >> >--Original Message--
> >> >I subscribe to the microsoft security bulletins and
> >> >according to the one I received yesterday that flaw in
> >> >their patch has to do with RAS not SQL. I can froward
> >> the
> >> >email directly to you if you wish.
> >> >
> >> >JOhn
> >> >
> >> >
> >> >
> >> >>--Original Message--
> >> >>I have heard of a couple of instances when the MS
> >> Blaster
> >> >>patch is applied to a SQL 2k server, the server then
> has
> >> >>problems booting back into Windows 2000. I have also
> >> >>heard that MS PSS is aware of this issue, but
> >> information
> >> >>hasn't come out on it yet.
> >> >>
> >> >>Does anyone know what the incompatibility is between
> the
> >> >>MS Blaster Worm fix and SQL Server 2000 on a Windows
> >> 2000
> >> >>server? If so, please let me know.
> >> >>
> >> >>Thanks,
> >> >>Dave
> >> >>.
> >> >>
> >> >.
> >> >
> >
> >
> >.
> >

Thursday, February 16, 2012

Blank Page On Crystal Report 10

Hi Im' using Crystal Report 10 and the modules created works well when running on Windows XP, but when I try to run the modules under Windows 2003 or Windows 2000 then only a blank page is being displayed (without any error being returned).

Any idea? Please help!

Btw, Im' using Crstal Report Advanced Developer on all machines.Hello,

Can you please tell me if you got any answer for your problem as i'm getting the same issue too... Thanks in advance

bracoute
email addr: bracoute@.hotmail.com|||Yes me to but im using cystal report 8. In my development PC there are no problems but when i installed it at another PC to test it happens. the report have no error message but it jus blank??

please help anybody

Blank Page Hell!

Please help, I have posted about this problem before and trawled other posts
to help me but still can't find an answer!
The story...
WIndows 2003 server with latest SP's. SQL server 2000 with SP3a + Reporting
Services + SP1.
As administrator on machine able to upload and run reports. Created a
windows group (not with administrator privleges but user rights), added
users. These users can log into RS, but only get the blank screen without
'content' & 'properties' tab or create data source ect. options.
As administrator on reporting services I have given this group in reporting
services every permission possible, and they can access site security
settings and set things there. I have created a data source and uploaded a
report to a directory, again, as an administrator I have given this group
item level permissions, still no tabs.
I'm sure this is going to be something trivial in the end... but please help.
Let me know if you need more information.
Thanks QuintonI suspect that your reports are in a folder below the Home folder and you
gave permissions on this folder?
You need to assign the users at least Browser role on the Home folder for
them to be able to see its contents. Permissions on items are inherited
within the folder hierarchy.
Charles Kangai, MCDBA, MCT
"Quinton" wrote:
> Please help, I have posted about this problem before and trawled other posts
> to help me but still can't find an answer!
> The story...
> WIndows 2003 server with latest SP's. SQL server 2000 with SP3a + Reporting
> Services + SP1.
> As administrator on machine able to upload and run reports. Created a
> windows group (not with administrator privleges but user rights), added
> users. These users can log into RS, but only get the blank screen without
> 'content' & 'properties' tab or create data source ect. options.
> As administrator on reporting services I have given this group in reporting
> services every permission possible, and they can access site security
> settings and set things there. I have created a data source and uploaded a
> report to a directory, again, as an administrator I have given this group
> item level permissions, still no tabs.
> I'm sure this is going to be something trivial in the end... but please help.
> Let me know if you need more information.
> Thanks Quinton

Tuesday, February 14, 2012

Blackberry Server MSDE and active directory authentication

To all, thanks in advance,
I have blackberry server running sql msde 2000 (sp4), which is
authenticated via windows integrated with an active directory user
account. When I changed the password on said user account, restart the
mssqlserver service, it fails to start with a 560 error. I had to
changed said user account back to the old password in order for the
mssqlserver service to start. I wanted know where in ms sql msde 2000,
I needed to make the change in order for this service to start. I also
tried starting the service using local system account and it would not
start either. All help with this is greatly appreciated.
JB
Hi
Control Panel > Services. The Service can be stopped and started from there,
and the account password can be changed there for the service.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
<jon.jefferson@.gmail.com> wrote in message
news:1131849352.800496.311170@.g47g2000cwa.googlegr oups.com...
> To all, thanks in advance,
> I have blackberry server running sql msde 2000 (sp4), which is
> authenticated via windows integrated with an active directory user
> account. When I changed the password on said user account, restart the
> mssqlserver service, it fails to start with a 560 error. I had to
> changed said user account back to the old password in order for the
> mssqlserver service to start. I wanted know where in ms sql msde 2000,
> I needed to make the change in order for this service to start. I also
> tried starting the service using local system account and it would not
> start either. All help with this is greatly appreciated.
> JB
>
|||Mike
Thanks for your response, but I did that and the service would not
start under with the new password. The only idea I did not try was to
restart the Server.
Thanks,
JB
|||Mike,
Also, there are other services that start with this same service
account (i.e. all the blackberry services,) and those start fine,
except for errors in the Apps event log because the msssqlserver
service would not start with the same user account change for some
strange reason. I am changing passwords to in AD because I am taking
over duties after someone has left and need to change passwords for
security purposes. This is my only hold up.
JB

Black Windows when starting SQL Server Agent

Hello guys,
I just wanted to ask you a question regarding a funny
behavior on my server. Out of nowhere, when I start the
SQL Server Agent, a command window appears, with the path
to sqlagent.exe, but nothing else happens. The Agent runs
fine while that window is open, but when I close it, it
stops. This was not happening before. I wonder if the
agent is corrupted or something like that. I tried copying
the sqlagent.exe file from another computer, where this
behavior is not showing and it still happens. I wonder if
another file is corrupted.
Any comments and/or suggestions will be appreciated.
Thanks.What version / service pack of SQL Server are you running ..?
--
HTH
Ryan Waight, MCDBA, MCSE
"Francisco Elizondo" <drcoco@.softhome.net> wrote in message
news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
> Hello guys,
> I just wanted to ask you a question regarding a funny
> behavior on my server. Out of nowhere, when I start the
> SQL Server Agent, a command window appears, with the path
> to sqlagent.exe, but nothing else happens. The Agent runs
> fine while that window is open, but when I close it, it
> stops. This was not happening before. I wonder if the
> agent is corrupted or something like that. I tried copying
> the sqlagent.exe file from another computer, where this
> behavior is not showing and it still happens. I wonder if
> another file is corrupted.
> Any comments and/or suggestions will be appreciated.
> Thanks.|||I'm running SQL Server 2000, with Service Pack 3, but the
problem started before I applied SP3. I applied it to see
if that would fix the problem, but it didn't.
Thanks
>--Original Message--
>What version / service pack of SQL Server are you
running ..?
>--
>HTH
>Ryan Waight, MCDBA, MCSE
>"Francisco Elizondo" <drcoco@.softhome.net> wrote in
message
>news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
>> Hello guys,
>> I just wanted to ask you a question regarding a funny
>> behavior on my server. Out of nowhere, when I start the
>> SQL Server Agent, a command window appears, with the
path
>> to sqlagent.exe, but nothing else happens. The Agent
runs
>> fine while that window is open, but when I close it, it
>> stops. This was not happening before. I wonder if the
>> agent is corrupted or something like that. I tried
copying
>> the sqlagent.exe file from another computer, where this
>> behavior is not showing and it still happens. I wonder
if
>> another file is corrupted.
>> Any comments and/or suggestions will be appreciated.
>> Thanks.
>
>.
>|||Francisco,
In the services configuration panel, open sqlserveragent service. In the
LogOn tab, uncheck "Allow service to interact with desktop" checkbox which
is available only when running the service undes localsystem account.
"Francisco Elizondo" <drcoco@.softhome.net> wrote in message
news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
> Hello guys,
> I just wanted to ask you a question regarding a funny
> behavior on my server. Out of nowhere, when I start the
> SQL Server Agent, a command window appears, with the path
> to sqlagent.exe, but nothing else happens. The Agent runs
> fine while that window is open, but when I close it, it
> stops. This was not happening before. I wonder if the
> agent is corrupted or something like that. I tried copying
> the sqlagent.exe file from another computer, where this
> behavior is not showing and it still happens. I wonder if
> another file is corrupted.
> Any comments and/or suggestions will be appreciated.
> Thanks.|||Are you seing any messages in the SQL Agents ErrorLog.
Right Click 'SQL Server Agent' and Display ErrorLog
--
HTH
Ryan Waight, MCDBA, MCSE
"Francisco Elizondo" <drcoco@.softhome.net> wrote in message
news:0b3e01c3a546$526fd3a0$a601280a@.phx.gbl...
> I'm running SQL Server 2000, with Service Pack 3, but the
> problem started before I applied SP3. I applied it to see
> if that would fix the problem, but it didn't.
> Thanks
> >--Original Message--
> >What version / service pack of SQL Server are you
> running ..?
> >
> >--
> >HTH
> >Ryan Waight, MCDBA, MCSE
> >
> >"Francisco Elizondo" <drcoco@.softhome.net> wrote in
> message
> >news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
> >> Hello guys,
> >>
> >> I just wanted to ask you a question regarding a funny
> >> behavior on my server. Out of nowhere, when I start the
> >> SQL Server Agent, a command window appears, with the
> path
> >> to sqlagent.exe, but nothing else happens. The Agent
> runs
> >> fine while that window is open, but when I close it, it
> >> stops. This was not happening before. I wonder if the
> >> agent is corrupted or something like that. I tried
> copying
> >> the sqlagent.exe file from another computer, where this
> >> behavior is not showing and it still happens. I wonder
> if
> >> another file is corrupted.
> >> Any comments and/or suggestions will be appreciated.
> >> Thanks.
> >
> >
> >.
> >|||No errors in the errorlog. Only loading information for
the service. The service runs fine, but I'm just concerned
about the command window not closing. If I close it, the
service stops.
Thanks.
>--Original Message--
>Are you seing any messages in the SQL Agents ErrorLog.
>Right Click 'SQL Server Agent' and Display ErrorLog
>--
>HTH
>Ryan Waight, MCDBA, MCSE
>"Francisco Elizondo" <drcoco@.softhome.net> wrote in
message
>news:0b3e01c3a546$526fd3a0$a601280a@.phx.gbl...
>> I'm running SQL Server 2000, with Service Pack 3, but
the
>> problem started before I applied SP3. I applied it to
see
>> if that would fix the problem, but it didn't.
>> Thanks
>> >--Original Message--
>> >What version / service pack of SQL Server are you
>> running ..?
>> >
>> >--
>> >HTH
>> >Ryan Waight, MCDBA, MCSE
>> >
>> >"Francisco Elizondo" <drcoco@.softhome.net> wrote in
>> message
>> >news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
>> >> Hello guys,
>> >>
>> >> I just wanted to ask you a question regarding a funny
>> >> behavior on my server. Out of nowhere, when I start
the
>> >> SQL Server Agent, a command window appears, with the
>> path
>> >> to sqlagent.exe, but nothing else happens. The Agent
>> runs
>> >> fine while that window is open, but when I close it,
it
>> >> stops. This was not happening before. I wonder if the
>> >> agent is corrupted or something like that. I tried
>> copying
>> >> the sqlagent.exe file from another computer, where
this
>> >> behavior is not showing and it still happens. I
wonder
>> if
>> >> another file is corrupted.
>> >> Any comments and/or suggestions will be appreciated.
>> >> Thanks.
>> >
>> >
>> >.
>> >
>
>.
>|||Did you check the other recommendation? The service config?
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Francisco Elizondo" <drcoco@.softhome.net> wrote in message
news:0bcd01c3a54c$739f40a0$a601280a@.phx.gbl...
> No errors in the errorlog. Only loading information for
> the service. The service runs fine, but I'm just concerned
> about the command window not closing. If I close it, the
> service stops.
> Thanks.
> >--Original Message--
> >Are you seing any messages in the SQL Agents ErrorLog.
> >
> >Right Click 'SQL Server Agent' and Display ErrorLog
> >
> >--
> >HTH
> >Ryan Waight, MCDBA, MCSE
> >
> >"Francisco Elizondo" <drcoco@.softhome.net> wrote in
> message
> >news:0b3e01c3a546$526fd3a0$a601280a@.phx.gbl...
> >> I'm running SQL Server 2000, with Service Pack 3, but
> the
> >> problem started before I applied SP3. I applied it to
> see
> >> if that would fix the problem, but it didn't.
> >>
> >> Thanks
> >> >--Original Message--
> >> >What version / service pack of SQL Server are you
> >> running ..?
> >> >
> >> >--
> >> >HTH
> >> >Ryan Waight, MCDBA, MCSE
> >> >
> >> >"Francisco Elizondo" <drcoco@.softhome.net> wrote in
> >> message
> >> >news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
> >> >> Hello guys,
> >> >>
> >> >> I just wanted to ask you a question regarding a funny
> >> >> behavior on my server. Out of nowhere, when I start
> the
> >> >> SQL Server Agent, a command window appears, with the
> >> path
> >> >> to sqlagent.exe, but nothing else happens. The Agent
> >> runs
> >> >> fine while that window is open, but when I close it,
> it
> >> >> stops. This was not happening before. I wonder if the
> >> >> agent is corrupted or something like that. I tried
> >> copying
> >> >> the sqlagent.exe file from another computer, where
> this
> >> >> behavior is not showing and it still happens. I
> wonder
> >> if
> >> >> another file is corrupted.
> >> >> Any comments and/or suggestions will be appreciated.
> >> >> Thanks.
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >|||Well, it seems like that did the trick. Thanks a lot for
all the help. I will keep you updated if anything else
happens. Sorry to bother you if my dumb questions. :-D
Francisco
>--Original Message--
>Francisco,
>In the services configuration panel, open sqlserveragent
service. In the
>LogOn tab, uncheck "Allow service to interact with
desktop" checkbox which
>is available only when running the service undes
localsystem account.
>"Francisco Elizondo" <drcoco@.softhome.net> wrote in
message
>news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
>> Hello guys,
>> I just wanted to ask you a question regarding a funny
>> behavior on my server. Out of nowhere, when I start the
>> SQL Server Agent, a command window appears, with the
path
>> to sqlagent.exe, but nothing else happens. The Agent
runs
>> fine while that window is open, but when I close it, it
>> stops. This was not happening before. I wonder if the
>> agent is corrupted or something like that. I tried
copying
>> the sqlagent.exe file from another computer, where this
>> behavior is not showing and it still happens. I wonder
if
>> another file is corrupted.
>> Any comments and/or suggestions will be appreciated.
>> Thanks.
>
>.
>|||Yeps, tried the service config, and it did work. This is
the first time something like this happened and I was
scared that it had to do with the sql server install.
Thanks again for all your help.
>--Original Message--
>Did you check the other recommendation? The service
config?
>--
>Tibor Karaszi, SQL Server MVP
>Archive at:
>http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Francisco Elizondo" <drcoco@.softhome.net> wrote in
message
>news:0bcd01c3a54c$739f40a0$a601280a@.phx.gbl...
>> No errors in the errorlog. Only loading information for
>> the service. The service runs fine, but I'm just
concerned
>> about the command window not closing. If I close it, the
>> service stops.
>> Thanks.
>> >--Original Message--
>> >Are you seing any messages in the SQL Agents ErrorLog.
>> >
>> >Right Click 'SQL Server Agent' and Display ErrorLog
>> >
>> >--
>> >HTH
>> >Ryan Waight, MCDBA, MCSE
>> >
>> >"Francisco Elizondo" <drcoco@.softhome.net> wrote in
>> message
>> >news:0b3e01c3a546$526fd3a0$a601280a@.phx.gbl...
>> >> I'm running SQL Server 2000, with Service Pack 3, but
>> the
>> >> problem started before I applied SP3. I applied it to
>> see
>> >> if that would fix the problem, but it didn't.
>> >>
>> >> Thanks
>> >> >--Original Message--
>> >> >What version / service pack of SQL Server are you
>> >> running ..?
>> >> >
>> >> >--
>> >> >HTH
>> >> >Ryan Waight, MCDBA, MCSE
>> >> >
>> >> >"Francisco Elizondo" <drcoco@.softhome.net> wrote in
>> >> message
>> >> >news:0c5b01c3a53f$77c2be80$a301280a@.phx.gbl...
>> >> >> Hello guys,
>> >> >>
>> >> >> I just wanted to ask you a question regarding a
funny
>> >> >> behavior on my server. Out of nowhere, when I
start
>> the
>> >> >> SQL Server Agent, a command window appears, with
the
>> >> path
>> >> >> to sqlagent.exe, but nothing else happens. The
Agent
>> >> runs
>> >> >> fine while that window is open, but when I close
it,
>> it
>> >> >> stops. This was not happening before. I wonder if
the
>> >> >> agent is corrupted or something like that. I tried
>> >> copying
>> >> >> the sqlagent.exe file from another computer, where
>> this
>> >> >> behavior is not showing and it still happens. I
>> wonder
>> >> if
>> >> >> another file is corrupted.
>> >> >> Any comments and/or suggestions will be
appreciated.
>> >> >> Thanks.
>> >> >
>> >> >
>> >> >.
>> >> >
>> >
>> >
>> >.
>> >
>
>.
>

BizTalk Server 2004 Installation Query

I am trying ti install BizTalk Server 2004 on a Windows 2000 Server platform.While i try to configure BizTalk Server 2004 I get the undersaid error

Failed to create subscription datatbase "BizTalkMsgBoxdb" on server"XXX"
Statements could not be prepared
Conflicting locking hints specified
Conflicting locking hints specified
Conflicting locking hints specified

SqlScript file "C:\ProgramFiles\MicrosoftBizTalkserver2004\schema\\msgboxlogic.sql"
SqlCommandBatch:"Create procedure [dbo].[int_PurgeMessageZeroSumTAble]@.
Aggressive int
as
declare..."

Can someone ehelp me out to resolve this error
Thanks and Regards
Rohit

I got this error trying to install BizTalk 2004 on SQL Server 2005.

To work around this error, I edited the file C:\Program Files\Microsoft BizTalk Server 2004\Schema\MsgBoxLogic.sql, as follows:

Find this procedure:
CREATE PROCEDURE [dbo].[int_PurgeMessageZeroSumTable]
After the ELSE, look for
DELETE FROM MessageParts WITH (ROWLOCK)
And remove the “WITH (ROWLOCK)”
Do the same for these:
DELETE FROM Spool WITH (ROWLOCK)
DELETE FROM TrackedMessages WITH (ROWLOCK)
Then find:
CREATE PROCEDURE [dbo].[int_PurgePartZeroSumTable]
And after the ELSE find these and do the same thing:
DELETE FROM Fragments WITH (ROWLOCK)
DELETE FROM Parts WITH (ROWLOCK)

After making these changes to the file, you can get past this point in the configuration wizard. You will then encounter another error:

Deploying BAM infrastructure: Failed to set up BAM database(s). Invalid column name 'XLOCK'. Invalid column name 'ROWLOCK'. Parameters supplied for object 'dbo.bam_Metadata_RTAMutex' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.

In the database BamPrimaryImport, set the compatibility level to SQL Server 2000. You can then hit Retry in the configuraiton wizard, and the next error is:

Failure to add BAM Primary Import database (database: BAMPrimaryImport, server: MyServer) to BizTalk group (database: BizTalkMgmtDb, server: MyServer).

Darnit, someone went and changed sp_helpuser!

This is where I'm stuck.

|||

Hi,

Did u solve this problem? i m also stuck up exactly in the same place..plz give me a solution, if u ve solved it...

Sumanesh

|||The same problem here, did anyone find out how to solve this?|||I was told this is because SQL Server 2005 and BizTalk 2004 are not compatible.|||If you get the message

"Failure to add BAM Primary Import database (database:

BAMPrimaryImport, server: MyServer) to BizTalk group (database:

BizTalkMgmtDb, server: MyServer). "

When using SQL Server 2004 it appears to be due to biztalk not cleaning up after itself after a configuration failure.

Open Control Panels > User Accounts click on the Advanced tab and then on the Advanced button.

Delete the following groups (some may not exist yet depending when the past failure occured)

BizTalk Application Users

BizTalk Isolated Host Users

BizTalk Server Administrators

EDI Subsystem Users

SSO Administrators

SSO Affiliate Administrators

This got past the error mentioned above when using SQL Server 2004|||

i got the same problem

any solutions ?

the last post does not got past the error if using SQL Server 2005

|||

Hi,

I am also configuring Biztalk Server 2004 on SQL Server 2005.

You work around helped, but it only creaded the first three databases.

While it was still on "Now Configuring: Biztalk WMI" it throws the following error:

"ActiveX component can't create object"

Please help

Wonder Andile Hlongwane

BizTalk Server 2004 Installation Query

I am trying ti install BizTalk Server 2004 on a Windows 2000 Server platform.While i try to configure BizTalk Server 2004 I get the undersaid error

Failed to create subscription datatbase "BizTalkMsgBoxdb" on server"XXX"
Statements could not be prepared
Conflicting locking hints specified
Conflicting locking hints specified
Conflicting locking hints specified

SqlScript file "C:\ProgramFiles\MicrosoftBizTalkserver2004\schema\\msgboxlogic.sql"
SqlCommandBatch:"Create procedure [dbo].[int_PurgeMessageZeroSumTAble]@.
Aggressive int
as
declare..."

Can someone ehelp me out to resolve this error
Thanks and Regards
Rohit

I got this error trying to install BizTalk 2004 on SQL Server 2005.

To work around this error, I edited the file C:\Program Files\Microsoft BizTalk Server 2004\Schema\MsgBoxLogic.sql, as follows:

Find this procedure:
CREATE PROCEDURE [dbo].[int_PurgeMessageZeroSumTable]
After the ELSE, look for
DELETE FROM MessageParts WITH (ROWLOCK)
And remove the “WITH (ROWLOCK)”
Do the same for these:
DELETE FROM Spool WITH (ROWLOCK)
DELETE FROM TrackedMessages WITH (ROWLOCK)
Then find:
CREATE PROCEDURE [dbo].[int_PurgePartZeroSumTable]
And after the ELSE find these and do the same thing:
DELETE FROM Fragments WITH (ROWLOCK)
DELETE FROM Parts WITH (ROWLOCK)

After making these changes to the file, you can get past this point in the configuration wizard. You will then encounter another error:

Deploying BAM infrastructure: Failed to set up BAM database(s). Invalid column name 'XLOCK'. Invalid column name 'ROWLOCK'. Parameters supplied for object 'dbo.bam_Metadata_RTAMutex' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.

In the database BamPrimaryImport, set the compatibility level to SQL Server 2000. You can then hit Retry in the configuraiton wizard, and the next error is:

Failure to add BAM Primary Import database (database: BAMPrimaryImport, server: MyServer) to BizTalk group (database: BizTalkMgmtDb, server: MyServer).

Darnit, someone went and changed sp_helpuser!

This is where I'm stuck.

|||

Hi,

Did u solve this problem? i m also stuck up exactly in the same place..plz give me a solution, if u ve solved it...

Sumanesh

|||The same problem here, did anyone find out how to solve this?
|||I was told this is because SQL Server 2005 and BizTalk 2004 are not compatible.
|||If you get the message
"Failure to add BAM Primary Import database (database: BAMPrimaryImport, server: MyServer) to BizTalk group (database: BizTalkMgmtDb, server: MyServer). "
When using SQL Server 2004 it appears to be due to biztalk not cleaning up after itself after a configuration failure.
Open Control Panels > User Accounts click on the Advanced tab and then on the Advanced button.
Delete the following groups (some may not exist yet depending when the past failure occured)
BizTalk Application Users
BizTalk Isolated Host Users
BizTalk Server Administrators
EDI Subsystem Users
SSO Administrators
SSO Affiliate Administrators
This got past the error mentioned above when using SQL Server 2004
|||

i got the same problem

any solutions ?

the last post does not got past the error if using SQL Server 2005

|||

Hi,

I am also configuring Biztalk Server 2004 on SQL Server 2005.

You work around helped, but it only creaded the first three databases.

While it was still on "Now Configuring: Biztalk WMI" it throws the following error:

"ActiveX component can't create object"

Please help

Wonder Andile Hlongwane

BizTalk Server 2004 Installation Query

I am trying ti install BizTalk Server 2004 on a Windows 2000 Server platform.While i try to configure BizTalk Server 2004 I get the undersaid error

Failed to create subscription datatbase "BizTalkMsgBoxdb" on server"XXX"
Statements could not be prepared
Conflicting locking hints specified
Conflicting locking hints specified
Conflicting locking hints specified

SqlScript file "C:\ProgramFiles\MicrosoftBizTalkserver2004\schema\\msgboxlogic.sql"
SqlCommandBatch:"Create procedure [dbo].[int_PurgeMessageZeroSumTAble]@.
Aggressive int
as
declare..."

Can someone ehelp me out to resolve this error
Thanks and Regards
Rohit

I got this error trying to install BizTalk 2004 on SQL Server 2005.

To work around this error, I edited the fileC:\Program Files\Microsoft BizTalk Server 2004\Schema\MsgBoxLogic.sql, as follows:

Find this procedure:
CREATE PROCEDURE [dbo].[int_PurgeMessageZeroSumTable]
After the ELSE, look for
DELETE FROM MessageParts WITH (ROWLOCK)
And remove the “WITH (ROWLOCK)”
Do the same for these:
DELETE FROM Spool WITH (ROWLOCK)
DELETE FROM TrackedMessages WITH (ROWLOCK)
Then find:
CREATE PROCEDURE [dbo].[int_PurgePartZeroSumTable]
And after the ELSE find these and do the same thing:
DELETE FROM Fragments WITH (ROWLOCK)
DELETE FROM Parts WITH (ROWLOCK)

After making these changes to the file, you can get past this point in the configuration wizard. You will then encounter another error:

Deploying BAM infrastructure: Failed to set up BAM database(s). Invalid column name 'XLOCK'. Invalid column name 'ROWLOCK'. Parameters supplied for object 'dbo.bam_Metadata_RTAMutex' which is not a function. If the parameters are intended as a table hint, a WITH keyword is required.

In the database BamPrimaryImport, set the compatibility level to SQL Server 2000. You can then hit Retry in the configuraiton wizard, and the next error is:

Failure to add BAM Primary Import database (database: BAMPrimaryImport, server: MyServer) to BizTalk group (database: BizTalkMgmtDb, server: MyServer).

Darnit, someone went and changed sp_helpuser!

This is where I'm stuck.

|||

Hi,

Did u solve this problem? i m also stuck up exactly in the same place..plz give me a solution, if u ve solved it...

Sumanesh

|||The same problem here, did anyone find out how to solve this?
|||I was told this is because SQL Server 2005 and BizTalk 2004 are not compatible.
|||If you get the message
"Failure to add BAM Primary Import database (database: BAMPrimaryImport, server: MyServer) to BizTalk group (database: BizTalkMgmtDb, server: MyServer). "
When using SQL Server 2004 it appears to be due to biztalk not cleaning up after itself after a configuration failure.
Open Control Panels > User Accounts click on the Advanced tab and then on the Advanced button.
Delete the following groups (some may not exist yet depending when the past failure occured)
BizTalk Application Users
BizTalk Isolated Host Users
BizTalk Server Administrators
EDI Subsystem Users
SSO Administrators
SSO Affiliate Administrators
This got past the error mentioned above when usingSQL Server 2004
|||

i got the same problem

any solutions ?

the last post does not got past the error if using SQL Server 2005

|||

Hi,

I am also configuring Biztalk Server 2004 on SQL Server 2005.

You work around helped, but it only creaded the first three databases.

While it was still on "Now Configuring: Biztalk WMI" it throws the following error:

"ActiveX component can't create object"

Please help

Wonder Andile Hlongwane

Friday, February 10, 2012

BIP Portal

Hi everyone,

I've just installed the BIP portal on an Application Server running Windows 2000 with the latest Service Pack and I choose to install the BIP database on a database Server. I've put my user in the BIP_ADMIN on the Application server's local windows user-group and also in the BIP_USERS role on the database BIP. If I try to browse the URL on the the application server it works well, but when I try to browse from my local machine thorough the network I get the following message: User 'AGFBRASIL\GAVieira' do not currently have access to the database. Please add the user to 'BIP_USERS' user group on SQL server's machine or contact the system administrator.

Anyone could help me?

Thanks in advance,

Genilson from So Paulo, Brazil.Hi Paulo
Try to connect to the database from your local computer without BIP.
Thanks,
Igor

Originally posted by gavieira
Hi everyone,

I've just installed the BIP portal on an Application Server running Windows 2000 with the latest Service Pack and I choose to install the BIP database on a database Server. I've put my user in the BIP_ADMIN on the Application server's local windows user-group and also in the BIP_USERS role on the database BIP. If I try to browse the URL on the the application server it works well, but when I try to browse from my local machine thorough the network I get the following message: User 'AGFBRASIL\GAVieira' do not currently have access to the database. Please add the user to 'BIP_USERS' user group on SQL server's machine or contact the system administrator.

Anyone could help me?

Thanks in advance,

Genilson from So Paulo, Brazil.|||Hi Igor,

Ok, I've already tried and it worked well. I think the problem is with BIP application.

Thanks,

Genilson|||Then ensure the defined user 'AGFBRASIL\GAVieira' has required privilege on SQL side to connect to the database.|||Hello Satya,

Yes. This user is owner of the database.|||May try the BIP site for any information for this behaviour.|||Hello gavieira

I've got the same problem and
thread http://www.dbforums.com/t803897.html
( after translation from German ;)
helped me to solve it partially

I've created login BIPuser on SQL Server with PUBLIC access to
BIP database (it turned out that BIP_USER role membership isn't neccessery in my case)
and modified web.config in BIP directory on IIS

<add key="Authentication" value="SQL" />
<add key="UserID" value="BIPuser" />
<add key="Password" value="password" />

The problem IMHO concerns failed delagation for user logged into application server through IIS to SQl on another server - it tries to connect as nt anonymous

I'll also be greatfull if gurues suggest more appropriate solution|||If you're using nT authentication then ensure IIS is configured to use the same, if not ensure login used has necessary privilege to access SQL from IIS>