Pervassive Client Install

Would anyone install a Pervassive client application into the windows & sql
2005 cluster environment?
I don't see why not, although I'd prefer not to install Pervasive in any
environment.
Hal Berenson, President
PredictableIT, LLC
http://www.predictableit.com
"John Kamensky" <jkamensky@.whitfordww.com> wrote in message
news:%23fTtgDCVGHA.5332@.TK2MSFTNGP10.phx.gbl...
> Would anyone install a Pervassive client application into the windows &
> sql 2005 cluster environment?
>
sql

Pervassive Client Install

Would anyone install a Pervassive client application into the windows & sql
2005 cluster environment?I don't see why not, although I'd prefer not to install Pervasive in any
environment.
--
Hal Berenson, President
PredictableIT, LLC
http://www.predictableit.com
"John Kamensky" <jkamensky@.whitfordww.com> wrote in message
news:%23fTtgDCVGHA.5332@.TK2MSFTNGP10.phx.gbl...
> Would anyone install a Pervassive client application into the windows &
> sql 2005 cluster environment?
>

Pervassive Client Install

Would anyone install a Pervassive client application into the windows & sql
2005 cluster environment?I don't see why not, although I'd prefer not to install Pervasive in any
environment.
Hal Berenson, President
PredictableIT, LLC
http://www.predictableit.com
"John Kamensky" <jkamensky@.whitfordww.com> wrote in message
news:%23fTtgDCVGHA.5332@.TK2MSFTNGP10.phx.gbl...
> Would anyone install a Pervassive client application into the windows &
> sql 2005 cluster environment?
>

persistent SQLBrowser error eventID 3

I have what looks like a completed install of SQL Server Express Edition, accomplished via unattended setup as part of a custom application (on a machine hereafter dubbed Machine "A").

So far, though, I can't access this instance from a remote SQL Server Management Studio because SSMSE can't see the installed database engine.

I've verified that:

The SQL Server Express installation on Machine A has remote connections enabled.

The SQLBrowser on Machine A is enabled and running.

Machine A's Windows Firewall is disabled.

Using a test tool, I can see that UDP messages sent to SQLBrowser (on port 1434), arrive (i.e. it complains about their format in the System Log).

It seems that Machine A's SQLBrowser isn't responding to requests, but there's no obvious reason why.

There's one clue in Machine A's event log:

Whenever SQLBrowser is started or restarted, there's a warning in the App Log:

"The configuration of the AdminConnection\TCP protocol in the SQL instance SQLEXPRESS is not valid." (eventid 3).

Any help will be much appreciated.

Thanks in advance
Josh

Some more diverse testing reveals that the problem seems to occur only when SSMSEE is running on Windows 2000.

The source of the problem appears to be that W2K is not picking up the correct instance name (in other words, it puts MYSERVER in the list of engines, but not MYSERVER\SQLEXPRESS). If I key in MYSERVER\SQLEXPRESS by hand, things work as expected.

Incidentally, I noticed that when running under XP, the Network Server list shows which version of the SQL Engine is running on each server, but under Windows 2000, it does this only for very few of the servers.

Is this a shade of a known problem?

Josh

Permissions not saved

HI,
SQL2k ( SP3a) ( I also install SP3a for the tools on my
workstation)
I encounter a strange problem when I try to set permissions on VIEW
Grant select on dbo.view_name to PUBLIC
Deny insert, update, delete on dbo.view_name to PUBLIC
With QA, when I execute thoses 2 commands ( Grant and Deny), those
commands are =93completed successfully=94 BUT =85. when I go to EM / Vi=
ew /
properties / permissions, nothing have been saved for PUBLIC role. If
I change persmission by clicking , go out of EM and when I go back in,
the permissions are back the way they were before I changed them
(nothing is saved)
Also, when I execute "sp_helprotect view_name" the result is:
Server: Msg 15330, Level 11, State 1, Procedure sp_helprotect, Line 346
There are no matching rows on which to report.
I tried with a =93user =93 instead of the PUBLIC role, and I have the sam=
e
problem.
I tries using SA account, and I have the same problem
I tried working on others worksations or on the console without success
I tried re-install =93sp3a=94 for the tools on my workstation without
success.
I will try to use PROFILER tomorrow.
Is it a bug with SP3a ? Is it a collation problem ?
Any idea '
Thank you
DannyHi Danny,
I believe I know the answer to part of your information. When EXEC
sp_helprotect <view name> returns a result set "There are no matching rows
on which to report", it means that a view by the name specificed does not
exist in the current database. Double check the database name listed in
the drop down at the top of Query Analyzer. Verify the database name shown
is the database name that contains the view name.
The second part of your information is more difficult to test. If you
register a server via SQL Enterprise Manager and you register using an
account that is part of the System Admin server role, you should be able to
make any permissions changes you wish and have them stick. My suspicion is
you registered SQL Server in SQL Enterprise Manager with an account that is
not a member of the System Admin role.
Please let me know what role the account holds within SQL Server.
Thanks.
Gary Whitley
This posting is provided "AS IS" with no warranties, and confers no rights.|||Thank you Gary,
I Verified that the BD's name shown is the database name that contains th=
e view
name.
I Verified that I registered SQL Server in SQL Enterprise Manager with an=
account that is
a member of the System Admin role. I also tried to register SQL Server in=
SQL
Enterprise Manager ans QA with "SA" .
Additional information: I have 2 similars DB on the same server machine.
For the first one, persmissions are saved and I can verify with SP_Helpro=
tect
For the other one, permissions are not saved and SP_Helprotect returns a=
result set "There are no matching rows on which to report",
Tonight dbreindex and Updatestat will be executed
Thank you
Danny
"Gary Whitley [MSFT]" a =E9crit :

quote:

---

> Hi Danny,
> I believe I know the answer to part of your information. When EXEC
> sp_helprotect <view name> returns a result set "There are no matching r=

---

ows

quote:

---

> on which to report", it means that a view by the name specificed does n=

---

ot

quote:

---

> exist in the current database. Double check the database name listed i=

---

n

quote:

---

> the drop down at the top of Query Analyzer. Verify the database name s=

---

hown

quote:

---

> is the database name that contains the view name.
> The second part of your information is more difficult to test. If you
> register a server via SQL Enterprise Manager and you register using an
> account that is part of the System Admin server role, you should be abl=

---

e to

quote:

---

> make any permissions changes you wish and have them stick. My suspicio=

---

n is

quote:

---

> you registered SQL Server in SQL Enterprise Manager with an account tha=

---

t is

quote:

---

> not a member of the System Admin role.
> Please let me know what role the account holds within SQL Server.
> Thanks.
> Gary Whitley
> This posting is provided "AS IS" with no warranties, and confers no rig=

---

hts.|||Danny,
Thank you for using the Microsoft newsgroups as your source for technical
information. In this particular case the complexity of your issue will
require in-depth troubleshooting and will not be best served by newsgroup
support. Please go to;
http://support.microsoft.com/common...=fh;en-us;cntac
tms
Select your region from the map and follow the instructions for contacting
our telephone support centers in your area.
Thank you.
Gary Whitley
This posting is provided "AS IS" with no warranties, and confers no rights.

Permission problems with sp_attach_db during installation

I successfully install SQL Express silently.

Then I try the following

-S .\INSTANCE -Q "sp_attach_db 'ATTACH_AS_NAME', 'C:\Program Files\APP_NAME\SQLData\APP_DB.MDF'"

This works...sometimes. But Many times I wll get a permissions error on the folder "C:\Program Files\APP_NAME". If I go and give "Everyone" "Full Permission" to the folder...it works fine.

My questions are:

1) What system users need access (and at what level) to this folder to do an attach? Because obviously giving everyone full access is bad.

2) Is there a better method for deploying a populated database with my application that this?

SQL service account needs modify privilege on "C:\Program Files\APP_NAME\SQLData\" path. If its running in Local system account then make sure SYSTEM or NT Authority \ System has modify privilege on the path
|||Do you know how to adjust the settings of that folder to allow that in a deployment package (Wise Install?)|||If you a trying to attach only the "mdf", use sp_attach_single_file_db and ignore your transaction log file(ldf)|||Hi,
1.) Click Start-->Run-->services.msc
2.) Check SQL Server startup account (Log On As)
3.) If its Local system then provide modify privilege for SYSTEM or NT Authority \ System for the folder "C:\Program Files\APP_NAME\SQLData\"
4.) If its some other ID provide modify privilege for the ID on "C:\Program Files\APP_NAME\SQLData\" folder.