Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Thursday, March 22, 2012

April CTP:error when attaching db and when creating file in filegroup

Hi.
I'm using SQL Server 2005 beta 2 April CTP:

I am always getting this error while trying to attach a database and even when I try to create a file in a filegroup for table partitioning.

Error:

The file "<filename> " is compressed but does not reside in a read-only database or filegroup. The file must be decompressed.

is it a security problem?

Thanks
Christina

I found out that it will not accept a file if it is not found under the
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
folder.

|||I saw the same thing but is that the expected behavior. Can we not create database with database files any where on the hard drive.|||

I am not aware of such requirement, but based on your error message
I think your file is compressed (or is placed on compressed disk or folder)

Could you please check it. Click on the file property and go to Advance attributes to see if

"Compress contents to save disk space" is activated (checked).

Do the same for the file folder. If this is the case, please deactivate it.

SQL Server supports compressions with some limitations

(see Using NTFS Compression with Read-Only Secondary Filegroups and Read-Only Databases under Read-only filegroups in BOL)

Thanks

Mirek

|||Christina -
Did you have a chance the check if your file is using compressed media?
Thanks
Mirek|||Dear Mirek,
Thanks for your input.
I just tried it and as u said, it worked.

Regards,
Christina

April CTP installation failed

I've already installed VSTS 2005 Beta2 and I try to install workstation components of April CTP. What should I try to pass th error?
The error is at the end of installation:

Failed to generate type library 'C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.
System.EnterpriseServices

Server stack trace:
at System.EnterpriseServices.RegistrationDriver.InstallAssembly(RegistrationConfig regConfig, Object obSync)

at System.EnterpriseServices.RegistrationHelperTx.InstallAssemblyFromConfig(RegistrationConfig& regConfig, Object sync)

at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)

at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.EnterpriseServices.RegistrationThreadWrapper.PropInstallResult()

at System.EnterpriseServices.RegistrationHelper.InstallAssemblyFromConfig(RegistrationConfig& regConfig)

at System.EnterpriseServices.RegistrationHelper.InstallAssembly(String assembly, String& application, String partition, String& tlb, InstallationFlags installFlags)

at System.EnterpriseServices.RegistrationHelper.InstallAssembly(String assembly, String& application, String& tlb, InstallationFlags installFlags)

at Microsoft.SqlServer.Setup.SetupHelper.InstallAssembly(String AssemblyName)
End of Log is:
--
MSI (s) (00:10) [20:06:56:332]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1A4.tmp, Entrypoint: CommitTransaction
05/17/05 20:06:56 DDSet_Status: LANGID: 1049
05/17/05 20:06:56 DDSet_Entry: CommitTransaction started
05/17/05 20:06:56 DDSet_Status: LANGID: 1049
05/17/05 20:06:56 DDSet_Entry: CMsHelpObject constructor
05/17/05 20:06:56 DDSet_Status: LANGID: 1049
05/17/05 20:06:56 DDSet_Entry: CHelpCrypto constructor
05/17/05 20:06:56 DDSet_Exit: CHelpCrypto destructor
05/17/05 20:06:57 DDSet_Status: CommitTransaction()->IHxRegisterSession::CommitTransaction() returned 0.
05/17/05 20:06:57 DDSet_Status: CommitTransaction()->{90032DD0-ABEE-4424-AC1E-B076BDD4E350} was successfully committed.
05/17/05 20:06:57 DDSet_Exit: CMsHelpObject destructor
05/17/05 20:06:57 DDSet_Exit: CommitTransaction ended
MSI (s) (00:4C) [20:06:57:707]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1A5.tmp, Entrypoint: Do_sqlAssemblyRegSvcs
<Func Name='LaunchFunction'>
Function=Do_sqlAssemblyRegSvcs
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlAssemblyRegSvcs
PerfTime Start: Do_sqlAssemblyRegSvcs : Tue May 17 20:06:59 2005
<Func Name='Do_sqlAssemblyRegSvcs'>
Unable to install .NET Framework Service C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll
<EndFunc Name='Do_sqlAssemblyRegSvcs' Return='1603' GetLastError='14007'>
PerfTime Stop: Do_sqlAssemblyRegSvcs : Tue May 17 20:07:55 2005
Gathering darwin properties for failure handling.
Error Code: 1603
MSI (s) (00!3C) [20:08:07:770]: Product: Microsoft SQL Server 2005 Tools CTP -- Error 29635. The setup has encountered an unexpected error while Installing .NET Frameworks Assemblies. The error is : .


Error 29635. The setup has encountered an unexpected error while Installing .NET Frameworks Assemblies. The error is : .

<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='14007'>
Doing Action: Do_sqlAssemblyRegSvcs
PerfTime Start: Do_sqlAssemblyRegSvcs : Tue May 17 20:08:07 2005
--

I am encountering the same error. Does anyone have a solution?

Thx.|||Hi,

I believe that this link can help http://lab.msdn.microsoft.com/vs2005/get/vsbeta2installissues/default.aspx

regards
Nilton

|||Hi,
I ignored the error and the rest of the install proceeded fine. I did have problems with launching Management Studio(see my post here).

These issues may or may not be related. I got this error (the one you refer to) when installing from a copy of the DVD handed out at a seminar. The funny thing is , when i installed from the ISO, i didnt get the error but management studio didnt launch either.

Did you Abort or Ignore the error? Try IGNORE and see what happens?

HTH

Cheers
Benjy|||Actually I really have ignored the error and tools were installed.
Management Studio cannot run. It tries to send an error report to Microsoft. Other tools work fine.
Some info about error can be found in the Application log:

sqlwb.exe, 2000.90.1116.0, msenv.dll, 8.0.50215.44, 0x000a209e.

Error of application ..., version ..., module ..., version ..., address ...

I don't have any workaround. Try to reinstall didn't help.

WBR,
Stone

appSettings from web.config cannot be referenced in emailed report subscription

Server Software:

SQL Server 2000 (all sp's up to date)

SSRS 2000 (all sp's up to date)

We have an error when a report subscription is sent via email.

Our report definitions reference a key in the web.config file so that we can have a single location to reference our department's name in all reports. Our department name changes frequently as our company is bought and sold and it is difficult to manually update 700+ reports.

In report designer we have a text field with the following value expression:

=System.Configuration.ConfigurationSettings.appSettings("Department").ToString()

Our web.config looks like this:

<?xml version="1.0" encoding="utf-8" ?>

<configuration>

....extra settings truncated for brevity...

<appSettings>

<add key="Department" value="Report created by: Corporate Reporting and Analysis" />

</appSettings>

</configuration>

The reports work perfectly in every aspect accept when they are schedules to be emailed. When the email recipient receives the email (not matter what format, mhtl, pdf, etc...) the department string value is replaced with: #Error

Is this a bug with the report schedule and deilvery component? ..or is there a permission problem when accessing: System.Configuration.ConfigurationSettings.appSettings("Department").ToString() ?

Any help would be greatly appreciated.

Thank you

Well, I believe I solved the issue:

The report scheduling service is located in another folder:

C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\ReportServer\bin\ReportingServicesService.exe

...and its configuration file is called:

ReportingServicesService.exe.config

All we had to do was modify this config file to match our web.config appSettings and "Presto!" it worked.

<configuration>

....extra settings truncated for brevity...

<appSettings>

<add key="Department" value="Report created by: Corporate Reporting and Analysis" />

</appSettings>

</configuration>

Also, remember to restart the "ReportServer" service after updating the ReportingServicesService.exe.config file in order to immediately reset the changes.

Monday, March 19, 2012

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon Shargorodsky
Leon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com
|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard tha
t
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:

> Leon Shargorodsky wrote:
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Applying SP2a to SQL 2000/Win 2003

I'm getting this error message while trying to apply SP3a to SQL Server 2000
Standard that runs on Windows Server 2003:
"Setup was unable to verify the state of the server for an upgrade. Verify
the server is able to start and that you provided a valid sa password and
restart setup"
My sa password is definitely valid (verified), I'm able to stop and restart
SQL Server service manually with no problem. Please advise, this problem
happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard that
runs on Windows Server 2003.
Thanks you in advance for your help,
Leon ShargorodskyLeon Shargorodsky wrote:
> I'm getting this error message while trying to apply SP3a to SQL
> Server 2000 Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade.
> Verify the server is able to start and that you provided a valid sa
> password and restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
> restart SQL Server service manually with no problem. Please advise,
> this problem happens every time I try to run SP3 or SP3a for SQL
> Server 2000 Standard that runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky
Maybe the problem is related to the service account your using for the
SQL service. Is this a new SQL Server installation? If so, what SP are
you currently running? Stopping and restarting the service are
independent of the "sa" account and password. I assume you have logged
into SQL Server from Query Analyzer using the "sa" login and everything
works fine.
--
David Gugick
Imceda Software
www.imceda.com|||I've tried LocalSystem acount as well as customized acount with admin
priveledges.
Yes, I'm able to log in with my sa cridentials using Query Analyzer.
This is new SQL installation 8.00.194 this is why I'm trying to apply SP3a.
"David Gugick" wrote:
> Leon Shargorodsky wrote:
> > I'm getting this error message while trying to apply SP3a to SQL
> > Server 2000 Standard that runs on Windows Server 2003:
> >
> > "Setup was unable to verify the state of the server for an upgrade.
> > Verify the server is able to start and that you provided a valid sa
> > password and restart setup"
> >
> > My sa password is definitely valid (verified), I'm able to stop and
> > restart SQL Server service manually with no problem. Please advise,
> > this problem happens every time I try to run SP3 or SP3a for SQL
> > Server 2000 Standard that runs on Windows Server 2003.
> >
> > Thanks you in advance for your help,
> >
> > Leon Shargorodsky
> Maybe the problem is related to the service account your using for the
> SQL service. Is this a new SQL Server installation? If so, what SP are
> you currently running? Stopping and restarting the service are
> independent of the "sa" account and password. I assume you have logged
> into SQL Server from Query Analyzer using the "sa" login and everything
> works fine.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Maybe something here will help:
http://www.aspfaq.com/2440
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:9480C132-32CE-4FB1-B8C4-0474DDDFBB2C@.microsoft.com...
> I'm getting this error message while trying to apply SP3a to SQL Server
2000
> Standard that runs on Windows Server 2003:
> "Setup was unable to verify the state of the server for an upgrade. Verify
> the server is able to start and that you provided a valid sa password and
> restart setup"
> My sa password is definitely valid (verified), I'm able to stop and
restart
> SQL Server service manually with no problem. Please advise, this problem
> happens every time I try to run SP3 or SP3a for SQL Server 2000 Standard
that
> runs on Windows Server 2003.
> Thanks you in advance for your help,
> Leon Shargorodsky

Sunday, March 11, 2012

Apply sql2k post sp4 fix 2162 on cluster

I applied sql2k post sp4 fix 2040 and 2162 on active node of the cluster without error, the version number is 8.00.2162. When failover the cluster and double check version number again, it's 8.00.2040. That means fix 2162 didn't push to passive node. So I tried apply fix 2162 on current active node but stopped with KB904660(ENU) setup error: An error in updating your system has occurred. Can't find any log file, and OS is win2k3 enterprise edition with sp1. Anyone got similar issue?

You should get a higher build of Hotfix package. The issue you are reporting is a known bug and has been fixed in later builds.

thanks

Raja

Information on this page is posted as is and no warranty as to the accuracy of any of the presented information

Thursday, March 8, 2012

Application-defined or object-defined error 40002

I am using 6.5 .
Here is the error that i get
Think that tempdb is small how do i change that or what is this error about'

--------
AIMSMan
--------
Application-defined or object-defined error 40002

37000: [Microsoft][ODBC SQL Server Driver][SQL Server]Can't allocate space for object '##RevByNetSALIMJUMMA' in database 'tempdb' because the 'default' segment is full. If you ran out of space in Syslogs, dump the transaction log. Otherwise, use ALTER DATABASE or sp_extendsegment to increase the size of the segment.( 1105)

ODBC

--------
Abort Retry Ignore
--------You'll have to increase the data device where tempdb resides (I do hope that you have it on a separate device) and then expand the database. I do not recommend to use segments on tempdb.|||How , i am new from oracle

i have set 2 devices as

1) Data
2) log

Pls tell me in detail

Tks
SEJ|||Default segment corresponds to data device.

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, Oskar
A comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:

> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, OskarA comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:
> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Application v. Error log. Will I miss anything important?

Hi,
Will I miss anything important in MS SQL Server 2000 if I monitor only MS
Windows 2000 application event log and don't monitor SQL Server error log?
What exactly will I miss?
-- Many thanks, OskarA comment to my previous post.
I suppose errors with severity 19 an higher ar logged into Windows
Application log, so I shouldn't miss any of them when they happen. Is that
true? Also if in SQL Server Enterprise Manager I configure a particular
message so that it is logged, I should see it in Application event log too,
right?
-- Thanks again, Oskar.
"Oskar" wrote:

> Hi,
> Will I miss anything important in MS SQL Server 2000 if I monitor only MS
> Windows 2000 application event log and don't monitor SQL Server error log?
> What exactly will I miss?
> -- Many thanks, Oskar
>

Wednesday, March 7, 2012

Application Roles ENCRYPT function Valid Password Characters

When I try to use the ODBC canonical ENCRYPT function for SP_SETAPPROLE, I
get an ODBC error when certain otherwise good characters are used in the
password. What characters are and are not allowed for passwords for
application roles while using the ENCRYPT function?You might ask me what is a good password? Here is a sample:
wZ726BcF_vR?goLVmxgsGLkZpqQbZ<Yfu<?L<t
RQzCa85c?"DXtI,QPbUtIyBSJbqF?
(without the line return)
"Chuck Hawkins" <charles.hawkins@.NOSPAMjenzabar.net> wrote in message
news:ebySvpBfFHA.3944@.TK2MSFTNGP10.phx.gbl...
> When I try to use the ODBC canonical ENCRYPT function for SP_SETAPPROLE, I
> get an ODBC error when certain otherwise good characters are used in the
> password. What characters are and are not allowed for passwords for
> application roles while using the ENCRYPT function?
>|||You can find the valid characters in the books online help
topic: Security Rules.
You can find the topic in the index under passwords, rules
for
-Sue
On Tue, 28 Jun 2005 15:49:06 -0400, "Chuck Hawkins"
<charles.hawkins@.NOSPAMjenzabar.net> wrote:

>When I try to use the ODBC canonical ENCRYPT function for SP_SETAPPROLE, I
>get an ODBC error when certain otherwise good characters are used in the
>password. What characters are and are not allowed for passwords for
>application roles while using the ENCRYPT function?
>|||Thank you, Sue. I went back and re-wrote my password generation script to
remove references to the unallowed characters mentioned in Security Rules
for passwords - []{}(),;?*! @..
I'm still having the problem with the ENCRYPT function. I execute:
sp_setapprole
@.rolename = 'TEST',
@.password = {Encrypt N
'ro111гPM0ci?TxmOK
e3qJDtSV?Xrи"S??D
k2?q6L?EvrvI1mOENycWpLvz
jL?3kn'}
--@.password = {Encrypt N 'easy'}
,@.encrypt = 'odbc'
go
And get:
[Microsoft][ODBC SQL Server Driver]Syntax error or access violation
I know I don't have a syntax error (other than an ugly password). When I
switch the TEST app role over to a password of 'easy', it works.
Am I supposed to put braces [] around the password somehow?
So the question remains, what characters are not allowed for passwords? I
know []{}(),;?*! @.. are not, but I don't have any of these.
Chuck
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:99a4c1p6996f5mklnjbq0hhmapjunkv95u@.
4ax.com...
> You can find the valid characters in the books online help
> topic: Security Rules.
> You can find the topic in the index under passwords, rules
> for
> -Sue
> On Tue, 28 Jun 2005 15:49:06 -0400, "Chuck Hawkins"
> <charles.hawkins@.NOSPAMjenzabar.net> wrote:
>
>|||Incidentally, here is the ugly password generation code:
set nocount on
declare @.counter int,
@.password varchar(128),
@.char char(1),
@.charindex int,
@.loop int
/* Unallowed characters:
! = 33
( = 40
) = 41
, = 40
* = 42
; = 59
? = 63
@. = 64
[ = 91
] = 93
{ = 123
} = 125
*/
select @.counter = 1, @.password = ''
while @.counter < 2
begin
--Restrict the password to 0-9, A-Z, and a-z
select @.loop = 1
while @.loop = 1
begin
select @.charindex = convert(int, rand() * 254)
if (@.charindex between 65 and 90 or @.charindex between 97 and 122)
and @.charindex not in (33,40,41,42,59,63,64,91,93,123,125)
--or @.charindex between 161 and 255 or @.charindex between 130 AND 140
select @.loop = 0
end
--Accumulate characters for password string
select @.char = char(@.charindex)
select @.password = @.password + @.char
select @.counter = @.counter + 1
end
while @.counter < 4
begin
--Restrict the password to 0-9, A-Z, and a-z
select @.loop = 1
while @.loop = 1
begin
select @.charindex = convert(int, rand() * 254)
if (@.charindex between 48 and 57 or @.charindex between 65 and 90 or
@.charindex between 97 and 122)
and @.charindex not in (33,40,41,42,59,63,64,91,93,123,125)
--or @.charindex between 161 and 255 or @.charindex between 130 AND 140
select @.loop = 0
end
--Accumulate characters for password string
select @.char = char(@.charindex)
select @.password = @.password + @.char
select @.counter = @.counter + 1
end
while @.counter < 5
begin
--Restrict the password to 0-9
select @.loop = 1
while @.loop = 1
begin
select @.charindex = convert(int, rand() * 254)
if @.charindex between 48 and 57 --or @.charindex between 65 and 90 or
@.charindex between 97 and 122
and @.charindex not in (33,40,41,42,59,63,64,91,93,123,125)
--or @.charindex between 161 and 255 or @.charindex between 130 AND 140
select @.loop = 0
end
--Accumulate characters for password string
select @.char = char(@.charindex)
select @.password = @.password + @.char
select @.counter = @.counter + 1
end
while @.counter < 10
begin
-- Restrict the password to NOT 0-9, A-Z, and a-z
select @.loop = 1
while @.loop = 1
begin
select @.charindex = convert(int, rand() * 254)
if --@.charindex between 48 and 57 or @.charindex between 65 and 90 or
@.charindex between 97 and 122
--or
(@.charindex between 161 and 255 or @.charindex between 130 AND 140)
and @.charindex not in (33,40,41,42,59,63,64,91,93,123,125)
select @.loop = 0
end
--Accumulate characters for password string
select @.char = char(@.charindex)
select @.password = @.password + @.char
select @.counter = @.counter + 1
end
while @.counter < 11
begin
--Restrict the password to 0-9
select @.loop = 1
while @.loop = 1
begin
select @.charindex = convert(int, rand() * 254)
if @.charindex between 48 and 57 --or @.charindex between 65 and 90 or
@.charindex between 97 and 122
and @.charindex not in (33,40,41,42,59,63,64,91,93,123,125)
--or @.charindex between 161 and 255 or @.charindex between 130 AND 140
select @.loop = 0
end
--Accumulate characters for password string
select @.char = char(@.charindex)
select @.password = @.password + @.char
select @.counter = @.counter + 1
end
while @.counter < 129
begin
--Restrict the password to 0-9, A-Z, and a-z
select @.loop = 1
while @.loop = 1
begin
select @.charindex = convert(int, rand() * 254)
if (@.charindex between 48 and 57 or @.charindex between 65 and 90 or
@.charindex between 97 and 122
or @.charindex between 161 and 255 or @.charindex between 130 AND 140)
and @.charindex not in (33,40,41,42,59,63,64,91,93,123,125)
select @.loop = 0
end
--Accumulate characters for password string
select @.char = char(@.charindex)
select @.password = @.password + @.char
select @.counter = @.counter + 1
end
select RTRIM(@.password) AS Password
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:99a4c1p6996f5mklnjbq0hhmapjunkv95u@.
4ax.com...
> You can find the valid characters in the books online help
> topic: Security Rules.
> You can find the topic in the index under passwords, rules
> for
> -Sue
> On Tue, 28 Jun 2005 15:49:06 -0400, "Chuck Hawkins"
> <charles.hawkins@.NOSPAMjenzabar.net> wrote:
>
>|||What I've discovered:
The password characters are not allowed for or the canonical ENCRYPT functio
n does not work with characters with the following ASCII codes:
(33,40,41,42,59,63,64,91,93,123,125,130,
132,133,134,135,136,137,139,161,162,
166,167,168,169,171,172,173,174,175,176,
177,180,182,184,187,188,189,190,191,
215,247)
Further, in order for the ENCRYPT function to work, the password cannot be m
ore than 64 characters (vice 128 allowed in Security Rules).
All that said, it still doesn't work. When I enter the following code, I can
not get the SP_SETAPPROLE to work:
exec sp_dropapprole 'TEST_APPROLE'
go
exec sp_addapprole
@.rolename = 'TEST_APPROLE',
@.password = 'rwq4?37ctEPn0izwhJ6dq
dACSZcfmfia?fWG
'
go
sp_setapprole
@.rolename = 'TEST_APPROLE',
@.password = {Encrypt N 'rwq4?37ctEPn0izwhJ6dq
dACSZc
fmfia?fWG'}
--@.password = {Encrypt N 'easy'}
,@.encrypt = 'odbc'
go
Server: Msg 2764, Level 16, State 1, Procedure sp_setapprole, Line 41
Incorrect password supplied for application role 'TEST_APPROLE'.
So the question remains, what are valid password characters for application
roles in order for the ENCRYPT function to work?
And now we have a new question, why does the ENCRYPT function limit you to 6
4 characters? I have my suppositions but I'd love to hear from someone who k
nows.
Chuck Hawkins
"Chuck Hawkins" <charles.hawkins@.NOSPAMjenzabar.net> wrote in message news:OUXAtKKfFHA.572@.T
K2MSFTNGP15.phx.gbl...
> Thank you, Sue. I went back and re-wrote my password generation script to
> remove references to the unallowed characters mentioned in Security Rules
> for passwords - []{}(),;?*! @..
> I'm still having the problem with the ENCRYPT function. I execute:
>
> sp_setapprole
> @.rolename = 'TEST',
> @.password = {Encrypt N
> 'ro111гPM0ci?TxmOK
e3qJDtSV?Xrи"S??
Dk2?q6L?EvrvI1mOENycWpLv
zjL?3kn'}
> --@.password = {Encrypt N 'easy'}
> ,@.encrypt = 'odbc'
> go
>
> And get:
> [Microsoft][ODBC SQL Server Driver]Syntax error or access violatio
n
>
> I know I don't have a syntax error (other than an ugly password). When I
> switch the TEST app role over to a password of 'easy', it works.
>
> Am I supposed to put braces [] around the password somehow?
>
> So the question remains, what characters are not allowed for passwords? I
> know []{}(),;?*! @.. are not, but I don't have any of these.
>
> Chuck
>
> "Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:99a4c1p6996f5mklnjbq0hhmapjunkv95u@.
4ax.com...
>
>

Saturday, February 25, 2012

Application Login SQL Error

I created aASP.net 2.0 application usingC# on VS2005
The application access several database on a remoteSQL Server 2005

I recently added Login functionalties to the application, this created a MDF in the app_data folder.

Everything works fine on my local desk top...

I can access my remote SQL Server 2005

and the local MDF file works fine, I can create account, login and all that fun stuff

So I Published the site to my target server:

Which is the same server running the SQL Server 2005

The parts of the application that does not require login works fine, I can access the SQL server 2005 with ease..see data, update, everything

However when ever I try to login or create an account from the application(MDF file) I get this:

An error has occurred while establishing a connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote connections.
(provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

I can only assume that the problem is with the MDF file.

Can anyone point me in the right direction?

Thank you
Andre

This is often fixed by ensuring the Initial Catalog entry is in the connectionstring.

.....Initial Catalog=yourFileWithoutTheExt....

I just reread the error...actually, I think it's because you are trying to administer the DB from your PC, and it's not setup that way.

|||

Thank you for responding,

On my target server I do not have SQL Express but SQL server 2005 and the remote setting for that is correct.

I changed my application from using the local SQL Express MDF file to use the SQL server 2005 for membership and roles by running aspnet_sql.exe to set up the database.

And all is working.

Thanks again

Andre

Friday, February 24, 2012

application failover error

We currently have a system that uses sql server 2005 mirroring. In testing the application, we fail over the database in the middle of a 2.0 .NET web application. The failover partner is specified in the connection string.

The next request to the web server results in an error page popping up with the message "A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"

This message only occurs for the first request to the web server, all subsequent requests sucessfully access the new failed over database.

Thanks for any suggestions.

I'm having the same problem and haven't yet found anything. I know that if you leave the app alone for at 1.5 minutes and then try to execute it again it will connect just fine. Some timeout is occurring that is then allowing the app to connect and I'm trying to find a way to force that timeout after a failover condition.

Let me know if you have any luck. :-)

|||This confused me also. From what I can tell, this is by

design. If you want the user to see no errors, the application

needs to trap the error and re-open the connection. The

documentation says

http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

Assume a client is successfully connected to the principal, and a database

mirroring failover (automatic, manual, or forced) occurs. The next time

the application attempts to use the connection, the ADO.NET or SQL Native

Client driver will detect that the connection to the old principal has failed,

and will automatically retry connecting to the new principal as specified in

the failover partner name.

This message talks more about it:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=752968&SiteId=1|||

Could I get some feedback from a Microsoft person if this is supposed to be a "feature" or a "bug" so I could go back to the customer with an answer?

Thanks.

|||

Yes, this is expected behavior. Your application needs to handle these errors and retry the connection.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||

I'm not sure if that's true.

I'm catching the error using a TRY CATCH statement and once I try to connect again after catching the error I still am unable to connect. The only way I'll be able to connect is if I leave my app alone for about 60 seconds and then try to connect. At that point it will work just fine.

This is a sample of my code:

Dim constring As String = "Server=SQL01.eqa\Fantabet;Failover Partner=SQL02.eqa\Fantabet;" _
& "Database=test;" _
& "UID=FailTest2;PWD=test;Network=dbmssocn"

Using con As New SqlConnection(constring)

Using cmd As New SqlCommand
Try 'First TRY statement to catch errors when opening the connection
con.Open()
cmd.Connection = con
cmd.CommandText = "INSERT INTO SystemsTest (FirstName, LastName)VALUES ('SQLWriter','" & con.DataSource & "')"
Try 'Second Try statement only for executing the SQL Command
cmd.ExecuteNonQuery()
Catch ex As SqlException
lblresult.Text = "Error"

Catch ex As SqlException
con.Close()
lblresult.Text = lblresult.Text & "<BR>Con.open error<BR>Error code = " & ex.ErrorCode & "<BR>Error Description = " & ex.Message
End Try

lblprimary.Text = "Current Primary Database = " & con.DataSource

con.Close()
con.Dispose()
End Using
End Using

So what my code does is that it tries to open the connection and if everything goes smooth a SQL command is executed but if an error is encountered while opening the connection object then the sub procedure finishes and changes the text of a label to "Error". The SQLConnection object is closed manually using a con.close but also by design since I'm using a "Using" statement.

Yet when I try to execute the procedure afterwards it still cannot connect. I must wait about 60 seconds to the procedure will work again.

|||

Matt,

Thanks for your response. My understanding based on Microsoft’s documentation, was that there were no modification required in the application code.

In the event of a fail-over, the sqlclient would try the partner database. In Explicit mode you can even provide the partner in the connection string.

Can you point me to MS documentation that supports your response?

Thank you

application failover error

We currently have a system that uses sql server 2005 mirroring. In testing the application, we fail over the database in the middle of a 2.0 .NET web application. The failover partner is specified in the connection string.

The next request to the web server results in an error page popping up with the message "A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)"

This message only occurs for the first request to the web server, all subsequent requests sucessfully access the new failed over database.

Thanks for any suggestions.

I'm having the same problem and haven't yet found anything. I know that if you leave the app alone for at 1.5 minutes and then try to execute it again it will connect just fine. Some timeout is occurring that is then allowing the app to connect and I'm trying to find a way to force that timeout after a failover condition.

Let me know if you have any luck. :-)

|||This confused me also. From what I can tell, this is by

design. If you want the user to see no errors, the application

needs to trap the error and re-open the connection. The

documentation says

http://www.microsoft.com/technet/prodtechnol/sql/2005/dbmirror.mspx

Assume a client is successfully connected to the principal, and a database

mirroring failover (automatic, manual, or forced) occurs. The next time

the application attempts to use the connection, the ADO.NET or SQL Native

Client driver will detect that the connection to the old principal has failed,

and will automatically retry connecting to the new principal as specified in

the failover partner name.

This message talks more about it:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=752968&SiteId=1|||

Could I get some feedback from a Microsoft person if this is supposed to be a "feature" or a "bug" so I could go back to the customer with an answer?

Thanks.

|||

Yes, this is expected behavior. Your application needs to handle these errors and retry the connection.

Regards,

Matt Hollingsworth

Sr. Program Manager

SQL Server High Availability

|||

I'm not sure if that's true.

I'm catching the error using a TRY CATCH statement and once I try to connect again after catching the error I still am unable to connect. The only way I'll be able to connect is if I leave my app alone for about 60 seconds and then try to connect. At that point it will work just fine.

This is a sample of my code:

Dim constring As String = "Server=SQL01.eqa\Fantabet;Failover Partner=SQL02.eqa\Fantabet;" _
& "Database=test;" _
& "UID=FailTest2;PWD=test;Network=dbmssocn"

Using con As New SqlConnection(constring)

Using cmd As New SqlCommand
Try 'First TRY statement to catch errors when opening the connection
con.Open()
cmd.Connection = con
cmd.CommandText = "INSERT INTO SystemsTest (FirstName, LastName)VALUES ('SQLWriter','" & con.DataSource & "')"
Try 'Second Try statement only for executing the SQL Command
cmd.ExecuteNonQuery()
Catch ex As SqlException
lblresult.Text = "Error"

Catch ex As SqlException
con.Close()
lblresult.Text = lblresult.Text & "<BR>Con.open error<BR>Error code = " & ex.ErrorCode & "<BR>Error Description = " & ex.Message
End Try

lblprimary.Text = "Current Primary Database = " & con.DataSource

con.Close()
con.Dispose()
End Using
End Using

So what my code does is that it tries to open the connection and if everything goes smooth a SQL command is executed but if an error is encountered while opening the connection object then the sub procedure finishes and changes the text of a label to "Error". The SQLConnection object is closed manually using a con.close but also by design since I'm using a "Using" statement.

Yet when I try to execute the procedure afterwards it still cannot connect. I must wait about 60 seconds to the procedure will work again.

|||

Matt,

Thanks for your response. My understanding based on Microsoft’s documentation, was that there were no modification required in the application code.

In the event of a fail-over, the sqlclient would try the partner database. In Explicit mode you can even provide the partner in the connection string.

Can you point me to MS documentation that supports your response?

Thank you

Application Event error

What could be causing this error in the event log?
SuperSocket info: Failed to get Exclusive port use(MSAFD
Tcpip [TCP/IP]) : Error 10013.It's often related to permissions for the SQL Server service
account. Have you made any changes to the service account
and what type of permissions does it have? I've seen the
error when people have changed the account but didn't do it
through Enterprise Manager or when they set up the account
to be more restrictive, not in the local admins (which is
fine) but didn't set all the correct rights and permissions.
-Sue
On Mon, 13 Oct 2003 08:52:32 -0700, "Jennifer Hennes"
<jennifer.hennes@.bartwest.com> wrote:
>What could be causing this error in the event log?
>SuperSocket info: Failed to get Exclusive port use(MSAFD
>Tcpip [TCP/IP]) : Error 10013.

application error

My SSIS package will just hang (do nothing) after validation of the package tasks. I realised that it does 2 validation. It then hits "starting exectuing" and then nothing. I mean nothing. It just stays the same. When I look into the logg file, the same message as in the output window. My package has parallel extract of data from the same datasource, but different tables. I dont know if that the problem but i really doubt it because i have done parallel table downloads countless times in version 2000. When i go into the data task window, the source task does no even indicate that its downloading (color yellow). Is there any reason why this will happen? Ooo, but the tasks executes just fine when i execute them individually (right click > execute).

Perhaps there is some blocking on the source system? There could be in any number of reasons and I would hazard a guess that the problem isn't in SSIS.

-Jamie

|||what do you mean by the source system. I keep getting errors like the one below. Im pulling down a table called ACT with ACT source task and destination task. For some reason, after pulling down a couple of records, it generates this error or sometimes it just hangs.

[ACT SOURCE [1]] Error: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutput(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuffer90[] buffers, IntPtr ppBufferWirePacket)|||

By source system I mean the "thing" from which you are extracting data.

What is the ACT source task? There is no such thing as a "source task" so I am assuming you mean "source component".

Is this a custom component (i.e. It is something that isn't provided out of the box with SSIS)?

-Jamie

|||

the act source task is an source component but not a custom source component. In any case, i changed the maxconcurrentexecution = -1 to 13. It seemed to start just fine but then failed at the very end when after pulling down almost all of the records. Now, this time the error was

[ACT SOURCE [1]] Error: System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.PrimeOutput(Int32 outputs, Int32[] outputIDs, PipelineBuffer[] buffers) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostPrimeOutp(IDTSManagedComponentWrapper90 wrapper, Int32 outputs, Int32[] outputIDs, IDTSBuf

and the warnings i got before that is

[DTS.Pipeline] Information: The buffer manager detected that the system was low on virtual memory, but was unable to swap out any buffers. 2 buffers were considered and 2 were locked. Either not enough memory is available to the pipeline because not enough is installed, other processes are using it, or too many buffers are locked.

Now, I dont know how this is possible but im running on a 64x xeon DP 3.02 with multi processor with nothing running on it except for SQL 2005 at present. It didnt look like it was even using 10% of the machines capabilities so i dont understand why it will complain about memory.

|||

Well, it looks from the copied text that you were running this package from the designer (BIDS). If that is the case then you are running in the WoW as a 32 bit process so you only would have a 2GB virtual address space.

Matt

|||Is there a work around to this problem so i have consume mor virtual addresss space the 2GB "if" that is the problem which i think might be because smaller tables are able to download without any problem.|||

You can run the package using the 64 bit version of DTExec if you have installed the 64 bit version of SSIS. That is not limited by the 2GB virtual address space.

Matt

|||

my odbc driver (DB/C 4) is a 32bit driver and that would mean if i should install SSIS in 64x, i wont be able to see my 32x odbc driver from SSIS because it will be registered in the data source manager for 32x under WOW or is there a way to go around this. Would you suggest that im better off with the 32x version of windows server 2003 even though i wont be using the full potential of the 64x machine (which i would like to ).

by the way, i installed the 32 version of SSIS

|||

There is no way to do this if your driver is 32 bits. You would have to run the package in 32 bits and then have the limitation of the 2GB virtual address space (you could use the /3GB switch to get 3GB which can sometimes help, but I believe you would actually need to be running a 32 bit OS to use this switch, although I am not certain of this). Since you are running in the WoW you are running the package as if it was 32 bits so using a 32 bit OS wouldn't buy you anything (except as I mentioned perhaps the option of using the /3GB switch).

Matt

|||

So basically, im screwed. Aaaaaaaaaaaaaaaa, i convienced my manager to get a 64x machine because it will make our process faster and because i was having the same memory problem on the development machine. He is going to cut my pay check into half unless Bill calls him and beg for me. My worry is if 2gb is an issue, it could be that 3gb will be an issue to since i cant really weigh how my virtual memory the processs will need. Im really in a pinch now.

why will the SQL team put a virtual memory limit on the 32x?

|||

It is not the SQL team. The OS only provides 2GB of virtual address space to any individual process. A 32 bit number can only reference 4GB of address space and the OS reserves 2GB for system virtual address space and 2GB for application virtual address space (1 and 3 when using the /3GB switch, respectively). All applications are subject to this not just SSIS.

Matt

|||Matt David, could you please elaborate more on the 2gb. When im downloading a table, i suppose the data is held in memory till its all downloaded and then inserted. So if the entire data that im downloading is more the 2gb, you are saying its not possible. Or what you mean is that each field like int, string can hold a maximum of 2gb of data.|||

No the entire virtual memory address space is 2GB. That means everything, the application, the data, etc. SSIS tries to alleviate this by swapping to disk when in low memory condition but sometimes there is not enough swapable so it can still fail.

Also, we don't hold everything in memory. We hold buffers in memory and when they get to a destination they are inserted and then the memory is freed. However, depending on what you are doing in your dataflow we may not be able to swap/free enough to not fail due to out of memory conditions.

You should also note that virtual memory does need some physical memory backing so there are cases when you can not run out of virtual memory but will run out of the physical backing and this can also cause out of memory failures. You don't mention how much physical memory your PC has but generally this is not an issue on 64 bit boxes.

Matt

|||what were you doing at the time of the error?Idid not do anything however I finished work from internet explorer6.0 and I closed it befor I turn off computer when I closed it the error is appear always


which language are you developing with?I did not devloping any language the langauge that I use in ienternet explorer is english and some time I open arabic site and comes to my mail messages in arabic I open it


does this happen in IE in general, even if you are not developing within the IDE? yes thats happen in IE in general


thanks for all help

Application error

What do I do to fix the "the application failed to initalize properly (0xc0000142), Click on OK to termainate the application.

You are going to have to provide more information.

What are you doing when that occurs?

What application/client tool are you using?

What version of SQL Server are you using? And patch level?

What is your OS version and patch level?

|||

Any updates on that ?

Jens K. Suessmeyer


http://www.sqlserver2005.de

Application error

System always popup this message:

Application popup: oprd.exe - Application Error : The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.

I recommend contacting Veritas for help with their application.

Application error

What do I do to fix the "the application failed to initalize properly (0xc0000142), Click on OK to termainate the application.

You are going to have to provide more information.

What are you doing when that occurs?

What application/client tool are you using?

What version of SQL Server are you using? And patch level?

What is your OS version and patch level?

|||

Any updates on that ?

Jens K. Suessmeyer


http://www.sqlserver2005.de