cant get any event from FormsAuthentication Sample in the report server ?

Hi i have used

http://msdn2.microsoft.com/en-gb/library/ms160724.aspx

to enable custom security in the report server,now custom security sample is working fine with my report server,

So bigger problem is my Software manager ask me to redesighn

UILogon.aspx page ?

Now the bigger problem is when redesign the UILogon.aspx page

I am having lot of problems in the sample ,thing is i cant get any button event from the

code behind it self ?

Error is saying that

"cannot handle Event 'Public Event Click(sender As Object, e As System.Web.UI.ImageClickEventArgs)' because they do not have the same signature."

Whats is the wrong with this ?

regards

sujithf ?

The only requirement for the method that handles the event is that it must have the same signature (parameters) as the delegate that is defined as the event handler for the event...If we put the Handles clause on a method whose signature does not match the delegate, then the compiler will give us a build error saying, "Method Car_Start cannot handle Event 'Start' because they do not have the same signature."

http://www.knowdotnet.com/articles/creatingevents3.html

http://msdn2.microsoft.com/en-us/library/00wh89xa.aspx

|||

Thank you very much for the help,

now its working with the help of u r answer,,........realy helped me lot

regards

sujithf

sql

Cant enable SQLCacheDependency

I have a SQL 2005 database and am running the 2.0 framework. I cannot seem to enable SQL caching on the db. I'm using the command line tool as follows:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regsql -S 99.99.999.999 -U
webteam -P sa -t tblname -d dbname -et

Enabling the table for SQL cache dependency.

.An error has happened. Details of the exception:
The database 'dbname' is not enabled for SQL cache notification
.

To enable a database for SQL cache notification, please use the System.Web.Cachi
ng.SqlCacheDependencyAdmin.EnableNotifications method, or the command line tool
aspnet_regsql. To use the tool, please run 'aspnet_regsql.exe -?' for more infor
mation.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>

I've replaced the ip address, dbname and tblname with ficticious names for obvious reasons here in the post.

What command can I enter to enable the database for caching?

Hi,

As show on the error message, you have to enable the cache notification on the whole database, using SqlCacheDependencyAdmin.EnableNotifications() method.

I can reproduce the error on my machine. And after calling this method, aspnet_regsql works fine.

HTH. If anything is unclear, please feel free to mark this post as Not Answered and post your reply. Thanks!

|||

Kevin, I'n not sure how to use the method you described. I tried to execute it from the command line as follows, but didn't work. It looks like I need to apply it in a .net program...

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>SqlCacheDependencyAdmin.EnableNotifications(Data Source=99.99.999.999;Initial Catalog=dbname;UserID=id;Password=pswd)
'SqlCacheDependencyAdmin.EnableNotifications' is not recognized as an internal or external command,operable program or batch file.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>

How should I apply this method. Thanks so much...

|||

Kevin, I'n not sure how to use the method you described. I tried to execute it from the command line as follows, but didn't work. It looks like I need to apply it in a .net program...

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>SqlCacheDependencyAdmin.EnableNotifications(Data Source=99.99.999.999;Initial Catalog=dbname;UserID=id;Password=pswd)
'SqlCacheDependencyAdmin.EnableNotifications' is not recognized as an internal or external command,operable program or batch file.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>

How should I apply this method. Thanks so much...

|||

Hi wsyeager,

This code is not executed from command line. It's a C# code.

You can create a project and execute this in the Form.Load event handler for a trial.

sql

Can't enable Full Text on database

Got a strange problem.
Had a SQL 7.0 Box with FTS on a database. Worked fine except for one quirk
we never tracked down. Starting up the MSSearch Service would fail 1/2 the
time due to timeout. Other 1/2 would take a long time (like sometimes an
hour) to start.
Upgraded to SQL 2000, no SP.
Upgrade went fine, similar startup problems.
Applied SP4.
Got the usual warning about having to recreate indices, etc. Not a problem
since we were releasing new code specifically for SQL 2000 FT.
Now... well it just doesn't work.
For example, if I try to start an index build on a table, I get Error 15601:
Full-Text Search is not enabled for the current database...
Ok, no problem.. try
sp_fulltext_database 'enable'
get
Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user
account
First thought was try to synchronize the passwords (i.e. start/stop SQL
Server, change to local account and then back to the domain account so that
MSSearch can talk to it.)
No Joy.
So, at this point I'm either facing calling Microsoft, or taking the server
offline for a day while I uninstall SQL 2000, reinstall it and re-attach the
databases and hope that works.
Suggestions?
--
Greg D. Moore
President Green Mountain Software
Personal: http://stratton.greenms.com
SQL Server Consulting sql at greenms.com
Hi Greg,
Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
7.0 was problematic at best...
In regards to error "The Microsoft Search service cannot be administered
under the present user account", have you removed or altered the
BUILTIN\Administrators login? If so, then this breaks FTS as the MSSearch
service uses this account to login into SQL Server. If you cannot add back
this login or cannot alter the login back to all of its default for security
reasons, you can use the following SQL code to enable the localsystem
account to have the proper security as a workaround:
exec sp_grantlogin N'NT Authority\System'
exec sp_defaultdb N'NT Authority\System', N'master'
exec sp_defaultlanguage N'NT Authority\System','us_english'
exec sp_addsrvrolemember N'NT Authority\System', sysadmin
See KB article 263712 "INF: How To Prevent Windows NT Administrators From
Administering a Clustered SQL Server" at
http://support.microsoft.com/default...;EN-US;q263712 for details.
Hope that helps,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
> Got a strange problem.
> Had a SQL 7.0 Box with FTS on a database. Worked fine except for one
> quirk
> we never tracked down. Starting up the MSSearch Service would fail 1/2
> the
> time due to timeout. Other 1/2 would take a long time (like sometimes an
> hour) to start.
> Upgraded to SQL 2000, no SP.
> Upgrade went fine, similar startup problems.
> Applied SP4.
> Got the usual warning about having to recreate indices, etc. Not a
> problem
> since we were releasing new code specifically for SQL 2000 FT.
> Now... well it just doesn't work.
> For example, if I try to start an index build on a table, I get Error
> 15601:
> Full-Text Search is not enabled for the current database...
> Ok, no problem.. try
> sp_fulltext_database 'enable'
> get
> Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line
> 46
> The Microsoft Search service cannot be administered under the present user
> account
> First thought was try to synchronize the passwords (i.e. start/stop SQL
> Server, change to local account and then back to the domain account so
> that
> MSSearch can talk to it.)
> No Joy.
> So, at this point I'm either facing calling Microsoft, or taking the
> server
> offline for a day while I uninstall SQL 2000, reinstall it and re-attach
> the
> databases and hope that works.
> Suggestions?
>
>
> --
> --
> Greg D. Moore
> President Green Mountain Software
> Personal: http://stratton.greenms.com
> SQL Server Consulting sql at greenms.com
>
|||"John Kane" <jt-kane@.comcast.net> wrote in message
news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Hi Greg,
> Yep, I remember your SQL 7.0 box & the related FTS problems as FTS in SQL
> 7.0 was problematic at best...
Oh good. :-)

> In regards to error "The Microsoft Search service cannot be administered
> under the present user account", have you removed or altered the
> BUILTIN\Administrators login?
Not that I am aware of.

> If so, then this breaks FTS as the MSSearch
> service uses this account to login into SQL Server. If you cannot add back
> this login or cannot alter the login back to all of its default for
security
> reasons, you can use the following SQL code to enable the localsystem
> account to have the proper security as a workaround:
> exec sp_grantlogin N'NT Authority\System'
> exec sp_defaultdb N'NT Authority\System', N'master'
> exec sp_defaultlanguage N'NT Authority\System','us_english'
> exec sp_addsrvrolemember N'NT Authority\System', sysadmin
Tried this, still no joy.
Did notice the database in question the name dbo was mapped to a login
called MONITOR (one of our internal accounts) instead of sa or
domain\administrator.
I've removed that mapping. So far hasn't helped.

> See KB article 263712 "INF: How To Prevent Windows NT Administrators From
> Administering a Clustered SQL Server" at
> http://support.microsoft.com/default...;EN-US;q263712 for
details.
>
Nothing here stood out.
Thanks though.

> Hope that helps,
> John
> --
> SQL Full Text Search Blog
> http://spaces.msn.com/members/jtkane/
>
> "Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in
message[vbcol=seagreen]
> news:8Ln0f.8178$QE1.857@.newsread2.news.atl.earthli nk.net...
an[vbcol=seagreen]
Line[vbcol=seagreen]
user
>
|||Hi Greg,
Hmm... It is possible it is something new &/or affected by SP4. I take it
you upgraded to SP4 directly from RTM, and not RTM to SP3 then to SP4.
Correct? I've not heard of any new FTS related bugs in SP4 that are
directly related to this error. However, there are two FIX kb articles
(http://support.microsoft.com/?kbid=900390 - post-SP4 and
http://support.microsoft.com/default...b;en-us;890043 - post SP3)
that I've blogged about in August, neither are well written IMHO.
The below workaround has in the past resolved this issue, however, in all
cases it was pre-SP4. As this is related to a possible SP4 issue, you might
want to open that support issue with MS PSS SQL Server support... :-(
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Greg D. Moore (Strider)" <mooregr_deleteth1s@.greenms.com> wrote in message
news:zFP0f.9074$vw6.4605@.newsread1.news.atl.earthl ink.net...
> "John Kane" <jt-kane@.comcast.net> wrote in message
> news:eDz9GhVyFHA.720@.TK2MSFTNGP15.phx.gbl...
> Oh good. :-)
>
> Not that I am aware of.
> security
> Tried this, still no joy.
> Did notice the database in question the name dbo was mapped to a login
> called MONITOR (one of our internal accounts) instead of sa or
> domain\administrator.
> I've removed that mapping. So far hasn't helped.
>
> details.
> Nothing here stood out.
> Thanks though.
> message
> an
> Line
> user
>

Cant enable database for full-text searching

When trying to create a new full-text catalogue for a database through enterprise manager the following error is generated:

The Microsoft Search service cannot be administered under the present user account

When attempting to enable a database for full-text searching by running the stored procedure "sp_fulltext_database" the following error message is recieved:

Server: Msg 7635, Level 16, State 1, Procedure sp_fulltext_database, Line 46
The Microsoft Search service cannot be administered under the present user account

The user account that the SQL service is running under has full administrative rights (including the privileges such as log on locally/as a batch/as a service etc - the SQL BUILTIN\Adminstrators login also exists) and the MSSQL and MS Search services have been stopped and started to ensure that the system account does have control of the MS Search service.

Although the text of the error message refers to user rights, line 46 of the stored procedure refers to the DBCC CALLFULLTEXT function and so it appears that the process is actually falling over when trying to drop catalogues.

The server was upgraded from SQL Server 6.5 to SQL Server 2000 and the Full-Text Search component was selected. However it was noticed that the folders Config, Projects and GatherLogs were not present under the following directory:

C:\Program files\Microsoft SQL Server\MSSQL\FTData\SQL Server\

(It was attempted to reinstall the Full-Text Search component from the SQL 2000 CD but as the component was already installed this wasnt possible)

The relevant config files, including the schema.txt, were then copied to the above location and it was ensured that the schema.txt file was the same in both the above location and the MSSQL\Binn folder (and on the SQL 2000 CD). But this has had no effect.

It has also been noticed that there is no registry key relating to:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ MSSQLServer\SQLFTSearch\Setup\Schema

However we have another server (which was a SQL 2000 install, as opposed to an upgrade) which also doesnt have this registry entry and that server isnt experiencing any problems with full-text search/indexing.

Can anyone suggest any other possible fixes before we resort to reinstalling SQL server?

Thanks,
ElaineHave you tried to run the stored procedure or sp_fulltext_database using query analyzer ?|||I'd be looking at the following closely ( assuming you may not have checked these out already ):

www.microsoft.com/technet

www.sqlmag.com

I'd be checking technet first as it sounds awfully like a upgrade "undocumented" type problem.

Apart from that, sounds like you have done everyting else right.

Try setting the SQL Server account to run under a domain account, but make sure you set the startup account to be the same in the Server Properties tab in EM as the account you use when you alter the startup account in Services. This is for the benefit of the Full Text service.

Post back if probs.

J.|||Thanks for your suggestions

...but we resorted to reinstalling SQL which has worked, so it appears that there might be problems with the full-text feature if you've upgraded to sql 2000 from 6.5 (as opposed to a straight 2000 install).

(we retained the databases by detaching them and copying the .mdf/.ldf files to another location. Then once the new install of SQL 2000 was complete we re-attached the databases - NB. the detach/attach method doesn't cover DTS packages. Also if specific users are created for a DB after reattaching you might need to delete them from the DB user section, then recreate them in the security logins section)