The problem with exporting Sub-Reports contained inside a Table or Matrix...will there be a service pack to fix the problem? As most reports consist of a table this is a major deficiency. Please advise...Support in Excel for subreports, tables and matrixes embedded within tables
and matrixes is on our feature wishlist for a future version. However, it is
unlikely that this feature would be implemented for a service pack of SQL
2000.
--
My employer's lawyers require me to say:
"This posting is provided 'AS IS' with no warranties, and confers no
rights."
"Prav Chand" <PravChand@.discussions.microsoft.com> wrote in message
news:292672DA-B98E-417B-92DB-4A41863B5FF3@.microsoft.com...
> The problem with exporting Sub-Reports contained inside a Table or
Matrix...will there be a service pack to fix the problem? As most reports
consist of a table this is a major deficiency. Please advise...
Showing posts with label fix. Show all posts
Showing posts with label fix. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Excel Column Data Type Issue
Ok, hopefully a simple issue with a simple fix. I'm importing data from an Excel spreadsheet with values such as: 10, 20, 20 Tall, 40, 40 Tall. The column imports but is treated as numeric with values 10, 20, 20, 40, 40. I set the cells to be treated as text in Excel. Any suggestions?Leave it to Microsoft to make this a painful process. Guessing data types is a nice feature and saves time, but sometimes, dang it, I just want to turn it off!
Anywho, try changing this registry key to 0 in order to change the default of scanning 8 rows to unlimited:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel|||Hi!
I have set the value in the registry (TypeGuessRows=0), but i still don't get the right data type.
What I have figured out:
Lets say I have 25 rows in my column in the Excel file. It that column 13 are numeric values and 12 are text. In this case the column gets indentified as a Numeric type.
Now if there are 12 numeric and 13 text values, then the type is set to text.
Is there any way to get JET engine indentify the coulmn type as text if there is only one text value?
It really sux if the type is determined by the majority of the values, this way there is no sence to increase the number of the sampled rows, as if you have more numeric values then the type will be numeric anyway.
Any help? Ideas?
Excel Column Data Type Issue
Ok, hopefully a simple issue with a simple fix. I'm importing data from an Excel spreadsheet with values such as: 10, 20, 20 Tall, 40, 40 Tall. The column imports but is treated as numeric with values 10, 20, 20, 40, 40. I set the cells to be treated as text in Excel. Any suggestions?Leave it to Microsoft to make this a painful process. Guessing data types is a nice feature and saves time, but sometimes, dang it, I just want to turn it off!
Anywho, try changing this registry key to 0 in order to change the default of scanning 8 rows to unlimited:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Excel|||Hi!
I have set the value in the registry (TypeGuessRows=0), but i still don't get the right data type.
What I have figured out:
Lets say I have 25 rows in my column in the Excel file. It that column 13 are numeric values and 12 are text. In this case the column gets indentified as a Numeric type.
Now if there are 12 numeric and 13 text values, then the type is set to text.
Is there any way to get JET engine indentify the coulmn type as text if there is only one text value?
It really sux if the type is determined by the majority of the values, this way there is no sence to increase the number of the sampled rows, as if you have more numeric values then the type will be numeric anyway.
Any help? Ideas?
Friday, March 9, 2012
Exact dynamic sql problem
The code that i want to fix and where im stuck at
Declare @.server varchar(100)
DECLARE Server_Cursor CURSOR FOR
SELECT srvname from master..sysservers
OPEN Server_Cursor
FETCH NEXT FROM Server_Cursor into @.server
WHILE @.@.FETCH_STATUS = 0
BEGIN
DECLARE Employee_Cursor CURSOR FOR
SELECT LastName, FirstName
FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
the @.Server
WHERE LastName like 'B%'
OPEN Employee_Cursor
FETCH NEXT FROM Employee_Cursor
WHILE @.@.FETCH_STATUS = 0
BEGIN
FETCH NEXT FROM Employee_Cursor
END
CLOSE Employee_Cursor
DEALLOCATE Employee_Cursor
FETCH NEXT FROM Server_Cursor into @.server
END
CLOSE Server_Cursor
DEALLOCATE Server_Cursor
This is the part within the second nested cursor where the problem is.. Can
someone help me ? Thanks
DECLARE Employee_Cursor CURSOR FOR
SELECT LastName, FirstName
FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
the @.Server
WHERE LastName like 'B%'Rather than show us a broken piece of code could you A) explain what it
is you are trying to achieve B) post enough information to reproduce
the problem. This should help:
http://www.aspfaq.com/etiquette.asp?id=5006
The best advice I can give based on what you posted is to avoid using
cursors and dynamic SQL. More on Dynamic SQL here:
http://www.sommarskog.se/dynamic_sql.html
David Portas
SQL Server MVP
--|||You don't need to use a cursor when using static sets of data. Use set
operations
SELECT srvname
into #temp
from master..sysservers
declare @.server varchar(50)
while exists (select 'x' from #temp)
begin
select top 1 @.server = srvname
from #temp
exec ('SELECT LastName, FirstName
FROM ' + @.server + '.Northwind.dbo.Employees WHERE LastName like
''B%''')
delete from #temp
where srvname = @.server
end
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eUjU1m7DFHA.2572@.tk2msftngp13.phx.gbl...
> The code that i want to fix and where im stuck at
> Declare @.server varchar(100)
> DECLARE Server_Cursor CURSOR FOR
> SELECT srvname from master..sysservers
> OPEN Server_Cursor
> FETCH NEXT FROM Server_Cursor into @.server
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> DECLARE Employee_Cursor CURSOR FOR
> SELECT LastName, FirstName
> FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
> the @.Server
> WHERE LastName like 'B%'
> OPEN Employee_Cursor
> FETCH NEXT FROM Employee_Cursor
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> FETCH NEXT FROM Employee_Cursor
> END
> CLOSE Employee_Cursor
> DEALLOCATE Employee_Cursor
> FETCH NEXT FROM Server_Cursor into @.server
> END
> CLOSE Server_Cursor
> DEALLOCATE Server_Cursor
> --
> This is the part within the second nested cursor where the problem is..
Can
> someone help me ? Thanks
> DECLARE Employee_Cursor CURSOR FOR
> SELECT LastName, FirstName
> FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
> the @.Server
> WHERE LastName like 'B%'
>
Declare @.server varchar(100)
DECLARE Server_Cursor CURSOR FOR
SELECT srvname from master..sysservers
OPEN Server_Cursor
FETCH NEXT FROM Server_Cursor into @.server
WHILE @.@.FETCH_STATUS = 0
BEGIN
DECLARE Employee_Cursor CURSOR FOR
SELECT LastName, FirstName
FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
the @.Server
WHERE LastName like 'B%'
OPEN Employee_Cursor
FETCH NEXT FROM Employee_Cursor
WHILE @.@.FETCH_STATUS = 0
BEGIN
FETCH NEXT FROM Employee_Cursor
END
CLOSE Employee_Cursor
DEALLOCATE Employee_Cursor
FETCH NEXT FROM Server_Cursor into @.server
END
CLOSE Server_Cursor
DEALLOCATE Server_Cursor
This is the part within the second nested cursor where the problem is.. Can
someone help me ? Thanks
DECLARE Employee_Cursor CURSOR FOR
SELECT LastName, FirstName
FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
the @.Server
WHERE LastName like 'B%'Rather than show us a broken piece of code could you A) explain what it
is you are trying to achieve B) post enough information to reproduce
the problem. This should help:
http://www.aspfaq.com/etiquette.asp?id=5006
The best advice I can give based on what you posted is to avoid using
cursors and dynamic SQL. More on Dynamic SQL here:
http://www.sommarskog.se/dynamic_sql.html
David Portas
SQL Server MVP
--|||You don't need to use a cursor when using static sets of data. Use set
operations
SELECT srvname
into #temp
from master..sysservers
declare @.server varchar(50)
while exists (select 'x' from #temp)
begin
select top 1 @.server = srvname
from #temp
exec ('SELECT LastName, FirstName
FROM ' + @.server + '.Northwind.dbo.Employees WHERE LastName like
''B%''')
delete from #temp
where srvname = @.server
end
"Hassan" <fatima_ja@.hotmail.com> wrote in message
news:eUjU1m7DFHA.2572@.tk2msftngp13.phx.gbl...
> The code that i want to fix and where im stuck at
> Declare @.server varchar(100)
> DECLARE Server_Cursor CURSOR FOR
> SELECT srvname from master..sysservers
> OPEN Server_Cursor
> FETCH NEXT FROM Server_Cursor into @.server
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> DECLARE Employee_Cursor CURSOR FOR
> SELECT LastName, FirstName
> FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
> the @.Server
> WHERE LastName like 'B%'
> OPEN Employee_Cursor
> FETCH NEXT FROM Employee_Cursor
> WHILE @.@.FETCH_STATUS = 0
> BEGIN
> FETCH NEXT FROM Employee_Cursor
> END
> CLOSE Employee_Cursor
> DEALLOCATE Employee_Cursor
> FETCH NEXT FROM Server_Cursor into @.server
> END
> CLOSE Server_Cursor
> DEALLOCATE Server_Cursor
> --
> This is the part within the second nested cursor where the problem is..
Can
> someone help me ? Thanks
> DECLARE Employee_Cursor CURSOR FOR
> SELECT LastName, FirstName
> FROM @.server.Northwind.dbo.Employees -- This is where the problem is with
> the @.Server
> WHERE LastName like 'B%'
>
Friday, February 24, 2012
Event ID: 19011 - Microsoft SQL Server Service
Hello,
Thanks for taking the time to look over my post ! I would appreciate
any suggestions to fix the problem I am having below:
OS: Windows 2000 Workstation
Database: Microsoft SQL Server Service v8.00.760
Event ID: 19011
Category: 8
Type: Error
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. The following is part of the event: ConnectionListen
(Shared-Memory (LPC)): Error 5.
The database does function, however, after a week or so the database
is unresponsive and the error above appears within the application
event log. I restart the machine and it's good to go again. There
are no other error messages.
Any help would be much appreciated. There isn't much on the net that
explain a resolution. I will also add that I rebuilt another machine
and the same error came up. This database is used by a commercial
application called TimeForce, so there is no way of migrating to SQL
Server 2000.
Thanks !
Chad
cwwilly wrote:
> Hello,
> Thanks for taking the time to look over my post ! I would appreciate
> any suggestions to fix the problem I am having below:
> OS: Windows 2000 Workstation
> Database: Microsoft SQL Server Service v8.00.760
> Event ID: 19011
> Category: 8
> Type: Error
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
> cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following is part of the event: ConnectionListen
> (Shared-Memory (LPC)): Error 5.
> The database does function, however, after a week or so the database
> is unresponsive and the error above appears within the application
> event log. I restart the machine and it's good to go again. There
> are no other error messages.
> Any help would be much appreciated. There isn't much on the net that
> explain a resolution. I will also add that I rebuilt another machine
> and the same error came up. This database is used by a commercial
> application called TimeForce, so there is no way of migrating to SQL
> Server 2000.
> Thanks !
> Chad
You don't need to migrate to SQL Server 200 because you are already
running SQL Server 2000. Could you be running out of disk space on the
log or data drive? Is the databaes running in simple recovery model or
is it running in full/bulk-logged. Can the data and log file auto-grow?
Is there sufficient space?
David Gugick
Imceda Software
www.imceda.com
|||I did a complete clean install on another box and immediately I was
receiving this error. I can't imagine that would have anything to do
with the logs. I have plenty of HD space and the database is set to
grow.
Does anyone have any other ideas ?
Thanks,
Chad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Chad S wrote:
> I did a complete clean install on another box and immediately I was
> receiving this error. I can't imagine that would have anything to do
> with the logs. I have plenty of HD space and the database is set to
> grow.
> Does anyone have any other ideas ?
> Thanks,
> Chad
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
What does the vendor say about the error?
David Gugick
Imceda Software
www.imceda.com
|||Hello there, I was wondering if you found any solution to this. This
exact error started for me just this last week. It has been running
fine the last 2 years. I have contacted the TimeForce support 3 times
now and they change a setting and say its ok but its not.
Thanks
jay
jay's Profile: http://unixadmintalk.com/847
View this thread: http://unixadmintalk.com/showthread.php?t=160858
Thanks for taking the time to look over my post ! I would appreciate
any suggestions to fix the problem I am having below:
OS: Windows 2000 Workstation
Database: Microsoft SQL Server Service v8.00.760
Event ID: 19011
Category: 8
Type: Error
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. The following is part of the event: ConnectionListen
(Shared-Memory (LPC)): Error 5.
The database does function, however, after a week or so the database
is unresponsive and the error above appears within the application
event log. I restart the machine and it's good to go again. There
are no other error messages.
Any help would be much appreciated. There isn't much on the net that
explain a resolution. I will also add that I rebuilt another machine
and the same error came up. This database is used by a commercial
application called TimeForce, so there is no way of migrating to SQL
Server 2000.
Thanks !
Chad
cwwilly wrote:
> Hello,
> Thanks for taking the time to look over my post ! I would appreciate
> any suggestions to fix the problem I am having below:
> OS: Windows 2000 Workstation
> Database: Microsoft SQL Server Service v8.00.760
> Event ID: 19011
> Category: 8
> Type: Error
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
> cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following is part of the event: ConnectionListen
> (Shared-Memory (LPC)): Error 5.
> The database does function, however, after a week or so the database
> is unresponsive and the error above appears within the application
> event log. I restart the machine and it's good to go again. There
> are no other error messages.
> Any help would be much appreciated. There isn't much on the net that
> explain a resolution. I will also add that I rebuilt another machine
> and the same error came up. This database is used by a commercial
> application called TimeForce, so there is no way of migrating to SQL
> Server 2000.
> Thanks !
> Chad
You don't need to migrate to SQL Server 200 because you are already
running SQL Server 2000. Could you be running out of disk space on the
log or data drive? Is the databaes running in simple recovery model or
is it running in full/bulk-logged. Can the data and log file auto-grow?
Is there sufficient space?
David Gugick
Imceda Software
www.imceda.com
|||I did a complete clean install on another box and immediately I was
receiving this error. I can't imagine that would have anything to do
with the logs. I have plenty of HD space and the database is set to
grow.
Does anyone have any other ideas ?
Thanks,
Chad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!
|||Chad S wrote:
> I did a complete clean install on another box and immediately I was
> receiving this error. I can't imagine that would have anything to do
> with the logs. I have plenty of HD space and the database is set to
> grow.
> Does anyone have any other ideas ?
> Thanks,
> Chad
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
What does the vendor say about the error?
David Gugick
Imceda Software
www.imceda.com
|||Hello there, I was wondering if you found any solution to this. This
exact error started for me just this last week. It has been running
fine the last 2 years. I have contacted the TimeForce support 3 times
now and they change a setting and say its ok but its not.
Thanks
jay
jay's Profile: http://unixadmintalk.com/847
View this thread: http://unixadmintalk.com/showthread.php?t=160858
Event ID: 19011 - Microsoft SQL Server Service
Hello,
Thanks for taking the time to look over my post ! I would appreciate
any suggestions to fix the problem I am having below:
OS: Windows 2000 Workstation
Database: Microsoft SQL Server Service v8.00.760
Event ID: 19011
Category: 8
Type: Error
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. The following is part of the event: ConnectionListen
(Shared-Memory (LPC)): Error 5.
The database does function, however, after a week or so the database
is unresponsive and the error above appears within the application
event log. I restart the machine and it's good to go again. There
are no other error messages.
Any help would be much appreciated. There isn't much on the net that
explain a resolution. I will also add that I rebuilt another machine
and the same error came up. This database is used by a commercial
application called TimeForce, so there is no way of migrating to SQL
Server 2000.
Thanks !
Chadcwwilly wrote:
> Hello,
> Thanks for taking the time to look over my post ! I would appreciate
> any suggestions to fix the problem I am having below:
> OS: Windows 2000 Workstation
> Database: Microsoft SQL Server Service v8.00.760
> Event ID: 19011
> Category: 8
> Type: Error
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
> cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following is part of the event: ConnectionListen
> (Shared-Memory (LPC)): Error 5.
> The database does function, however, after a week or so the database
> is unresponsive and the error above appears within the application
> event log. I restart the machine and it's good to go again. There
> are no other error messages.
> Any help would be much appreciated. There isn't much on the net that
> explain a resolution. I will also add that I rebuilt another machine
> and the same error came up. This database is used by a commercial
> application called TimeForce, so there is no way of migrating to SQL
> Server 2000.
> Thanks !
> Chad
You don't need to migrate to SQL Server 200 because you are already
running SQL Server 2000. Could you be running out of disk space on the
log or data drive? Is the databaes running in simple recovery model or
is it running in full/bulk-logged. Can the data and log file auto-grow?
Is there sufficient space?
--
David Gugick
Imceda Software
www.imceda.com
Thanks for taking the time to look over my post ! I would appreciate
any suggestions to fix the problem I am having below:
OS: Windows 2000 Workstation
Database: Microsoft SQL Server Service v8.00.760
Event ID: 19011
Category: 8
Type: Error
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. The following is part of the event: ConnectionListen
(Shared-Memory (LPC)): Error 5.
The database does function, however, after a week or so the database
is unresponsive and the error above appears within the application
event log. I restart the machine and it's good to go again. There
are no other error messages.
Any help would be much appreciated. There isn't much on the net that
explain a resolution. I will also add that I rebuilt another machine
and the same error came up. This database is used by a commercial
application called TimeForce, so there is no way of migrating to SQL
Server 2000.
Thanks !
Chadcwwilly wrote:
> Hello,
> Thanks for taking the time to look over my post ! I would appreciate
> any suggestions to fix the problem I am having below:
> OS: Windows 2000 Workstation
> Database: Microsoft SQL Server Service v8.00.760
> Event ID: 19011
> Category: 8
> Type: Error
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
> cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following is part of the event: ConnectionListen
> (Shared-Memory (LPC)): Error 5.
> The database does function, however, after a week or so the database
> is unresponsive and the error above appears within the application
> event log. I restart the machine and it's good to go again. There
> are no other error messages.
> Any help would be much appreciated. There isn't much on the net that
> explain a resolution. I will also add that I rebuilt another machine
> and the same error came up. This database is used by a commercial
> application called TimeForce, so there is no way of migrating to SQL
> Server 2000.
> Thanks !
> Chad
You don't need to migrate to SQL Server 200 because you are already
running SQL Server 2000. Could you be running out of disk space on the
log or data drive? Is the databaes running in simple recovery model or
is it running in full/bulk-logged. Can the data and log file auto-grow?
Is there sufficient space?
--
David Gugick
Imceda Software
www.imceda.com
Event ID: 19011 - Microsoft SQL Server Service
Hello,
Thanks for taking the time to look over my post ! I would appreciate
any suggestions to fix the problem I am having below:
OS: Windows 2000 Workstation
Database: Microsoft SQL Server Service v8.00.760
Event ID: 19011
Category: 8
Type: Error
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. The following is part of the event: ConnectionListen
(Shared-Memory (LPC)): Error 5.
The database does function, however, after a week or so the database
is unresponsive and the error above appears within the application
event log. I restart the machine and it's good to go again. There
are no other error messages.
Any help would be much appreciated. There isn't much on the net that
explain a resolution. I will also add that I rebuilt another machine
and the same error came up. This database is used by a commercial
application called TimeForce, so there is no way of migrating to SQL
Server 2000.
Thanks !
Chadcwwilly wrote:
> Hello,
> Thanks for taking the time to look over my post ! I would appreciate
> any suggestions to fix the problem I am having below:
> OS: Windows 2000 Workstation
> Database: Microsoft SQL Server Service v8.00.760
> Event ID: 19011
> Category: 8
> Type: Error
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
> cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following is part of the event: ConnectionListen
> (Shared-Memory (LPC)): Error 5.
> The database does function, however, after a week or so the database
> is unresponsive and the error above appears within the application
> event log. I restart the machine and it's good to go again. There
> are no other error messages.
> Any help would be much appreciated. There isn't much on the net that
> explain a resolution. I will also add that I rebuilt another machine
> and the same error came up. This database is used by a commercial
> application called TimeForce, so there is no way of migrating to SQL
> Server 2000.
> Thanks !
> Chad
You don't need to migrate to SQL Server 200 because you are already
running SQL Server 2000. Could you be running out of disk space on the
log or data drive? Is the databaes running in simple recovery model or
is it running in full/bulk-logged. Can the data and log file auto-grow?
Is there sufficient space?
David Gugick
Imceda Software
www.imceda.com|||I did a complete clean install on another box and immediately I was
receiving this error. I can't imagine that would have anything to do
with the logs. I have plenty of HD space and the database is set to
grow.
Does anyone have any other ideas ?
Thanks,
Chad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Chad S wrote:
> I did a complete clean install on another box and immediately I was
> receiving this error. I can't imagine that would have anything to do
> with the logs. I have plenty of HD space and the database is set to
> grow.
> Does anyone have any other ideas ?
> Thanks,
> Chad
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
What does the vendor say about the error?
David Gugick
Imceda Software
www.imceda.com|||Hello there, I was wondering if you found any solution to this. This
exact error started for me just this last week. It has been running
fine the last 2 years. I have contacted the TimeForce support 3 times
now and they change a setting and say its ok but its not.
Thanks
jay
---
jay's Profile: http://unixadmintalk.com/847
View this thread: http://unixadmintalk.com/showthread.php?t=160858
Thanks for taking the time to look over my post ! I would appreciate
any suggestions to fix the problem I am having below:
OS: Windows 2000 Workstation
Database: Microsoft SQL Server Service v8.00.760
Event ID: 19011
Category: 8
Type: Error
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
cannot be found. The local computer may not have the necessary
registry information or message DLL files to display messages from a
remote computer. The following is part of the event: ConnectionListen
(Shared-Memory (LPC)): Error 5.
The database does function, however, after a week or so the database
is unresponsive and the error above appears within the application
event log. I restart the machine and it's good to go again. There
are no other error messages.
Any help would be much appreciated. There isn't much on the net that
explain a resolution. I will also add that I rebuilt another machine
and the same error came up. This database is used by a commercial
application called TimeForce, so there is no way of migrating to SQL
Server 2000.
Thanks !
Chadcwwilly wrote:
> Hello,
> Thanks for taking the time to look over my post ! I would appreciate
> any suggestions to fix the problem I am having below:
> OS: Windows 2000 Workstation
> Database: Microsoft SQL Server Service v8.00.760
> Event ID: 19011
> Category: 8
> Type: Error
> Description:
> The description for Event ID ( 19011 ) in Source ( MSSQL$TIMEFORCE )
> cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following is part of the event: ConnectionListen
> (Shared-Memory (LPC)): Error 5.
> The database does function, however, after a week or so the database
> is unresponsive and the error above appears within the application
> event log. I restart the machine and it's good to go again. There
> are no other error messages.
> Any help would be much appreciated. There isn't much on the net that
> explain a resolution. I will also add that I rebuilt another machine
> and the same error came up. This database is used by a commercial
> application called TimeForce, so there is no way of migrating to SQL
> Server 2000.
> Thanks !
> Chad
You don't need to migrate to SQL Server 200 because you are already
running SQL Server 2000. Could you be running out of disk space on the
log or data drive? Is the databaes running in simple recovery model or
is it running in full/bulk-logged. Can the data and log file auto-grow?
Is there sufficient space?
David Gugick
Imceda Software
www.imceda.com|||I did a complete clean install on another box and immediately I was
receiving this error. I can't imagine that would have anything to do
with the logs. I have plenty of HD space and the database is set to
grow.
Does anyone have any other ideas ?
Thanks,
Chad
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!|||Chad S wrote:
> I did a complete clean install on another box and immediately I was
> receiving this error. I can't imagine that would have anything to do
> with the logs. I have plenty of HD space and the database is set to
> grow.
> Does anyone have any other ideas ?
> Thanks,
> Chad
> *** Sent via Developersdex http://www.codecomments.com ***
> Don't just participate in USENET...get rewarded for it!
What does the vendor say about the error?
David Gugick
Imceda Software
www.imceda.com|||Hello there, I was wondering if you found any solution to this. This
exact error started for me just this last week. It has been running
fine the last 2 years. I have contacted the TimeForce support 3 times
now and they change a setting and say its ok but its not.
Thanks
jay
---
jay's Profile: http://unixadmintalk.com/847
View this thread: http://unixadmintalk.com/showthread.php?t=160858
Subscribe to:
Posts (Atom)