Showing posts with label laptop. Show all posts
Showing posts with label laptop. Show all posts

Tuesday, March 27, 2012

Authorization ticket not received by LogonUser

Hi, I integrated with
ReportingServices using Forms Authentication followed the instruction of the
article from microsoft, it works fine on my laptop (Windows 2003 server and
sql2000), but when I try to duplicate it on our company server (windows 2000
and sql2000), I always got the error: Authorization ticket not received by
LogonUser, when I try to login as the ReportAdmin user.
Could someone help?
Thank you at advance.
YanDid you ever find a solution this problem?
I'm having the same issue. It works on my LapTop but when I duplicate
exactly what I have on the Server, it doesn't work.
Thanks.
"Authorization ticket" wrote:
> Hi, I integrated with
> ReportingServices using Forms Authentication followed the instruction of the
> article from microsoft, it works fine on my laptop (Windows 2003 server and
> sql2000), but when I try to duplicate it on our company server (windows 2000
> and sql2000), I always got the error: Authorization ticket not received by
> LogonUser, when I try to login as the ReportAdmin user.
>
> Could someone help?
> Thank you at advance.
> Yan|||Make sure the <UrlRoot> element value in the RSReportServer.config file is
the same URL value you are using to call the ReportService.asmx.
This error will happen if you have <UrlRoot> =http://MACHINENAME/ReportServer and you are calling the web service like
http://localhost/ReportServer/ReportService.asmx
Not sure if that's the issue but it's something to check. For the auth
cookie to work, the cookie domains have to be the same.
--
Adrian M.
MCP
"Jon-Slem" <JonSlem@.discussions.microsoft.com> wrote in message
news:C1AC412B-0DCA-4F69-A590-650CDB81B344@.microsoft.com...
> Did you ever find a solution this problem?
> I'm having the same issue. It works on my LapTop but when I duplicate
> exactly what I have on the Server, it doesn't work.
> Thanks.
> "Authorization ticket" wrote:
>> Hi, I integrated with
>> ReportingServices using Forms Authentication followed the instruction of
>> the
>> article from microsoft, it works fine on my laptop (Windows 2003 server
>> and
>> sql2000), but when I try to duplicate it on our company server (windows
>> 2000
>> and sql2000), I always got the error: Authorization ticket not received
>> by
>> LogonUser, when I try to login as the ReportAdmin user.
>>
>> Could someone help?
>> Thank you at advance.
>> Yan|||I don't get it.
I fixed this and I'm still getting the error. I didn't even have do this on
my laptop.
Did your work right after you made the change? I made the change in the
ReportingService.cs file, I changed it to the machine name. The config file
was already the machine, no change was need there.
If you have any idea, please give my a buzz.
Thank.
"Adrian M." wrote:
> Make sure the <UrlRoot> element value in the RSReportServer.config file is
> the same URL value you are using to call the ReportService.asmx.
> This error will happen if you have <UrlRoot> => http://MACHINENAME/ReportServer and you are calling the web service like
> http://localhost/ReportServer/ReportService.asmx
> Not sure if that's the issue but it's something to check. For the auth
> cookie to work, the cookie domains have to be the same.
> --
> Adrian M.
> MCP
> "Jon-Slem" <JonSlem@.discussions.microsoft.com> wrote in message
> news:C1AC412B-0DCA-4F69-A590-650CDB81B344@.microsoft.com...
> > Did you ever find a solution this problem?
> > I'm having the same issue. It works on my LapTop but when I duplicate
> > exactly what I have on the Server, it doesn't work.
> > Thanks.
> >
> > "Authorization ticket" wrote:
> >
> >> Hi, I integrated with
> >> ReportingServices using Forms Authentication followed the instruction of
> >> the
> >> article from microsoft, it works fine on my laptop (Windows 2003 server
> >> and
> >> sql2000), but when I try to duplicate it on our company server (windows
> >> 2000
> >> and sql2000), I always got the error: Authorization ticket not received
> >> by
> >> LogonUser, when I try to login as the ReportAdmin user.
> >>
> >>
> >> Could someone help?
> >>
> >> Thank you at advance.
> >>
> >> Yan
>
>

Authorization problems with SQL Developer's edition

I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.
I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
Thomas
"Steve Z" wrote:

> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.
|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:

Authorization problems with SQL Developer's edition

I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login just
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:
> I just installed developer's edition on a new laptop. Other machines in the
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instance
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
> I would try to connect to it via its IP address using a SQL Server login just
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
> > I just installed developer's edition on a new laptop. Other machines in the
> > network cannot connect to this new instance.
> >
> > At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
> > (we are inside a small network anyway - no need for local firewalls - I
> > guess).
> >
> > Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> > username under COMPUTER MANAGEMENT and disabled it.
> >
> > Now it's getting login failed for user NULL.
> >
> > Seems it's not on the network like the old laptop was. The old laptop did
> > not authenticate to the network, it logged in locally, but the SQL instance
> > was visible and connectable.
> >
> > I cannot seem to add DOMAIN\usernames to this instance.
> >
> > Any direction would be greatly appreciated.

Authorization problems with SQL Developer's edition

I just installed developer's edition on a new laptop. Other machines in the
network cannot connect to this new instance.
At first it was TIMEOUTS - so I turned off the new WINDOWS firewall feature
(we are inside a small network anyway - no need for local firewalls - I
guess).
Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
username under COMPUTER MANAGEMENT and disabled it.
Now it's getting login failed for user NULL.
Seems it's not on the network like the old laptop was. The old laptop did
not authenticate to the network, it logged in locally, but the SQL instance
was visible and connectable.
I cannot seem to add DOMAIN\usernames to this instance.
Any direction would be greatly appreciated.I would try to connect to it via its IP address using a SQL Server login jus
t
in case it is a DNS issue. Just a thought...
--
Thomas
"Steve Z" wrote:

> I just installed developer's edition on a new laptop. Other machines in t
he
> network cannot connect to this new instance.
> At first it was TIMEOUTS - so I turned off the new WINDOWS firewall featur
e
> (we are inside a small network anyway - no need for local firewalls - I
> guess).
> Then it was trying to connect as USERNAME = GUEST. I found GUEST as a
> username under COMPUTER MANAGEMENT and disabled it.
> Now it's getting login failed for user NULL.
> Seems it's not on the network like the old laptop was. The old laptop did
> not authenticate to the network, it logged in locally, but the SQL instanc
e
> was visible and connectable.
> I cannot seem to add DOMAIN\usernames to this instance.
> Any direction would be greatly appreciated.|||I am not a network person - and it really does show sometimes...
I did not join the domain properly with this new laptop.
Now that I've done that it's all set...
"Thomas" wrote:
[vbcol=seagreen]
> I would try to connect to it via its IP address using a SQL Server login j
ust
> in case it is a DNS issue. Just a thought...
> --
> Thomas
>
> "Steve Z" wrote:
>sql

Saturday, February 25, 2012

Audit Failures whenever I start the SQL Enterprise Manager

Hi,
When ever I start the Enterprise manger client from my laptop(Client), I see
the Failure Audit in the Security Eventlog. I registered all the servers
using sql authentication. I am running SQL Enterprisemanger on Windows Xp.
Here is one of the error:
Unprotection of auditable protected data.
Data Description: SQL Server Registration
Key Identifier: 1f3ba71a-6f52-4e58-8007-43ced74242b4
Protected Data Flags: 0x0
Protection Algorithms: 3DES-168 , SHA1-160
Failure Reason: 0x8009000B
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Can anybody having the fix for this, because my securtiy Auditing team
questioning these failures.
Thanks
rb
1. Do you have encryption enabled on the client or server?
2. When this happens is the laptop connected to the network?
3. Do you have any IPSec rules setup for the SQL Server?
"rb" <srbssr@.yahoo.com> wrote in message
news:efxp4cN9EHA.2600@.TK2MSFTNGP09.phx.gbl...
> Hi,
> When ever I start the Enterprise manger client from my laptop(Client), I
see
> the Failure Audit in the Security Eventlog. I registered all the servers
> using sql authentication. I am running SQL Enterprisemanger on Windows Xp.
> Here is one of the error:
> Unprotection of auditable protected data.
> Data Description: SQL Server Registration
> Key Identifier: 1f3ba71a-6f52-4e58-8007-43ced74242b4
> Protected Data Flags: 0x0
> Protection Algorithms: 3DES-168 , SHA1-160
> Failure Reason: 0x8009000B
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Can anybody having the fix for this, because my securtiy Auditing team
> questioning these failures.
> Thanks
> rb
>

Sunday, February 12, 2012

Attached DB not working properly in Vista Ultimate enviroment

hi,

i have installed SQLEXPRESS (SQL Server 9.0.3042) on my windows ultimate laptop. of late am facing this issue of database. this database is from SQl 7.0 Desktop edition(the one that i use in my office machine with Xp SP2). As such it works fine in SQL 2000 server after attachment (for test).

i have run SQLEXPRESS as administrator to make/attach new database. i can attach the database easily and can even view tables and other stuffs inside database in administrator mode. the issue pops up when i run SQLEXPRESS in normal mode. when i try to open and view the same DB's content, error pops up stating

"The database XXX is not accessible. (Micorosoft.sqlserver.express.objectExplorer)"

i cannot access this DB via VB 6 form as it dosnt show up at all in database list when tried to connect via ADODC.

i want to make this DB accessibility as normal operation, not previliged only to administrator as application run on normal mode only.

the issue dosnt arise when i locally make a new database as it can be accessed when run in normal mode also. why does this happen to database that is attached and not to ones locally made.

pls guide me as i usually do my works at home and making whole database again will surely take lots of pain. why not it just attach then start working, not asking for preveliged mode.

thanks in adv
Nyaken

Hi,

Try checking the owner of the attached database. I found that when i restored a db I had to then set the ownership afferwards otherwise I couldn't access it.

Chris

|||

hi,

thanks for the prompt re. well, as per ur suggestion i have explored all possibiliites to find a way to change the ownership of database but alas!!! i just couldnt make it. can you pls guide me to take this corrective measure, please. i hope everything must be done in administrative mode only, isnt it?

awaiting for your re

regs

ken

|||

Hi,

If you right click on the attached database and select properties then go the the files page, you should see that the second text box down (the owner field) is blank. If so, set an owner by clicking the elipsis next to the box. After you have clicked all the ok's you can check the owner was set by going back to the files page, and if the box now is not empty then the owner was set. You should be able to use the database now.

Hope this helps,

Chris

P.s. I did try to post this yesterday several times but the forum kept giving me an "unkown error"