"The data area passed to a system call is too small." Windows 8
I am not a developer - thus many comments do not make sense to me, as I'm just a heavy user. Today, about a year and half after beginning to use Windows 8, hyperlinks in my emails return the error "The data area passed to a system call is too small."
Can you give a layperson (i.e. simple - is it fixable and can I fix it?) answer to this error? If I copy and paste the URL into my IE 10 browser, it works. However, this takes more time than I usually can afford given how often I use email links to continue
my work.
Here's a picture of the error message:
OOPS, just got big RED message: Body text cannot contain images or links until we are able to verify your account.
I seem to have one (logged in automatically as sunwalkermsdn).
Thanks for any help to this newly appearing issue.
(will I get an email if you post an answer? - due to same message above, I cannot enter my email address)
This is a developer forum. We cannot help you to fix a web site, unless you own the web site in question and you can release a fix by yourself if you just need some advise on web development.
Contact the web site's owner if you don't own the web site in question.
Visual C++ MVP
Similar Messages
-
Windows 2008 x64 TS Printing - The data area passed to a system call is too small
Hi,
I have a Windows 2008 TS using Easy Print. The server has two quad core cpu's with 16Gb of ram and is running a light processing accounting program for 80 users. The machine and easy print both work fine until the server reaches about 5Gb of memory in use. Once this happens user's documents stop printing with event id's 6161 The data area passed to a system call is too small being logged. None of the hotfixes seem to be applicable to my scenario as I am not getting the common "Access Denied" error. I have increased received and transmit buffer sizes on both NIC's to the 2048 maximum, and set the Sizreqbuf setting in the registry - to no avail.
Any help appreciated.
ThanksHi,
Thanks for the post.
The Event error 6161 is caused by one of the following conditions:
The printer is not reachable on the network
Windows cannot allocate sufficient memory
There was invalid or incomplete data received by the print spooler
A driver upgrade failed
There is a bad printer device driver
For more information, please refer to the following article:
http://technet.microsoft.com/en-us/library/cc773865(WS.10).aspx
In this case, I assume that this issue may be caused by the insufficient memory.
In Event Viewer, examine the event and look for the following text: "Win32 error code returned by the print processor: 8. Not enough storage is available to process this command".
If so, please collect system information for 60 seconds and generate a System Diagnostics Report:
Open an elevated Command Prompt window. (Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.)
At the command prompt, type perfmon /report and then press ENTER. Reliability and Performance Monitor will start collecting data to create the System Diagnostics Report.
When the report is ready for viewing, locate the Diagnostic Results section of the report, and then check for any warnings (indicated by Warnings in the report). You can follow links to additional help on resolving warnings from this section. In addition, you can expand each category in the Basic System Checks section to see more details about why warnings appear. Also, the Performance section provides process-level details about top consumers of resources. You might need to increase the size of the paging file or add physical memory.
Thanks,
Miles -
"The data area passed to a system call is too small" NFS client Windows 2008 R2 SP1
Hi
I need to map a Hyper-V virtual windows server to a UNIX folder, but when i made de mapping and tried to navigate in to the mapped unit and shows me:
"The data area passed to a system call is too small"
I tried too many things like adding a registry key (and windows 2008 r2 already has)
Use a similar account between Unix and Windows domain
I done the steps in the document:
http://technet.microsoft.com/en-us/library/cc753302(WS.10).aspx
And nothing, this is just frustrating, also I disabled the firewall in the virtual machine and the host server.
I have a Windows 2008 Domain R2 functionality and the virtual machine is Windows 2008 R2 too.
The version of unix are:
AIX6.1 x64
AIX 6.3 x64
AIX 5.1 x86
Any Idea?
Thanks!
Doc MXHi,
You may perform the following troubleshooting suggestions:
l
Change how your NFS servers export the NFS shares and make them allow connections from high ports.
l
Add UseReservedPorts DWORD value under HKLM\Software\Microsoft\Client for NFS\CurrentVersion\Default and set it to 1. Restart the Client for NFS service to allow
the change to take effect.
For more information, please refer to the following Microsoft MSDN blog:
"Network Error 53", "The data area passed to a system call is too small" or "Unknown Error"
http://blogs.msdn.com/b/sfu/archive/2011/07/14/3087987.aspx
Regards,
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. -
-4006 -The data area passed to a system call is too small.
Hi ,everybody.
I would like to add data into SQL Server with VB.net 2005 and i am using object SAPbobsCOM.Payments with BoObjectTypes.oIncomingPayments when i build program and execute then i got error like this "-4006 -The data area passed to a system call is too small." and my code is .....
Private Sub cmdPayment_Click()
On Error GoTo ErrorHandler
Dim vCompany As SAPbobsCOM.Company
'create company object
vCompany = New SAPbobsCOM.Company
'set paras for connection
vCompany.CompanyDB = "TototaData"
vCompany.Password = "acct4"
vCompany.UserName = "acct4"
vCompany.Server = "(local)"
vCompany.DbUserName = "sa"
vCompany.DbPassword = "sa"
'connect to database server
If (0 <> vCompany.Connect()) Then
MsgBox("Failed to connect")
Exit Sub
End If
Dim nErr As Long
Dim errMsg As String
'Set the object's properties
Dim vPay As SAPbobsCOM.Payments
vPay = vCompany.GetBusinessObject(BoObjectTypes.oIncomingPayments)
vPay.Address = "622-7"
vPay.ApplyVAT = 1
vPay.CardCode = "F027-HO"
vPay.CardName = "TMT(GATEWAY)-HO"""
vPay.CashAccount = "288000"
vPay.CashSum = 0 '5620.85
vPay.CheckAccount = "280001"
vPay.ContactPersonCode = 2
vPay.DocCurrency = "Eur"
vPay.DocDate = Now
vPay.DocRate = 0
vPay.DocTypte = 0
vPay.HandWritten = 0
vPay.JournalRemarks = "Incoming - D10004"
vPay.LocalCurrency = 0
'vPay.Printed = 0
vPay.Reference1 = 14
vPay.Series = 0
'vPay.SplitTransaction = 0
vPay.TaxDate = Now
vPay.TransferAccount = "10100"
vPay.TransferDate = Now
vPay.TransferSum = 0 '
vPay.Invoices.AppliedFC = 0
'vPay.Invoices.AppliedSys = ""
'start
'vPay.Invoices.Count = 1
vPay.Invoices.DiscountPercent = 20
vPay.Invoices.InstallmentId = 0
'vPay.Invoices.LinkDate = CDate("31/12/2002")
'vPay.Invoices.PaidSum = "d"
'vPay.Invoices.UserFields = "ddd"
'end
vPay.Invoices.DocEntry = 1
vPay.Invoices.DocLine = 0
'vPay.Invoices.DocRate = 0
vPay.Invoices.InvoiceType = BoRcptInvTypes.it_Invoice
'vPay.Invoices.LineNum = 0
vPay.Invoices.SumApplied = 5031.2
vPay.Checks.AccounttNum = "384838"
vPay.Checks.BankCode = "CB"
vPay.Checks.Branch = "Branch"
vPay.Checks.CheckNumber = 3838383
vPay.Checks.CheckSum = 4031.2
'vPay.Checks.Currency = "Eur"
vPay.Checks.Details = "test1"
vPay.Checks.DueDate = CDate("31/12/2002")
' vPay.Checks.LineNum = 0
vPay.Checks.Trnsfrable = 0
Call vPay.Checks.Add()
Call vPay.Checks.SetCurrentLine(1)
vPay.Checks.AccounttNum = "384838"
vPay.Checks.BankCode = "CB"
vPay.Checks.Branch = "Branch"
vPay.Checks.CheckNumber = "3838383"
vPay.Checks.CheckSum = 1000
'vPay.Checks..Currency = "EUR"
vPay.Checks.Details = "test2"
vPay.Checks.DueDate = Now
'vPay.Checks.LineNum = 1
vPay.Checks.Trnsfrable = 0
If (vPay.Add() <> 0) Then
MsgBox("Failed to add a payment")
End If
'check for errors
Call vCompany.GetLastError(nErr, errMsg)
If (0 <> nErr) Then
MsgBox("Found error:" + Str(nErr) + "," + errMsg)
Else
MsgBox("Succeed in payment.add")
End If
'disconnect the company object, and release resource
Call vCompany.Disconnect()
vCompany = Nothing
Exit Sub
ErrorHandler:
MsgBox("Exception:" + Err.Description)
End Sub
It seem when i add record by use other object such as JournalEntries.It work!!!!!
i need all of your suggestion.Anyone who have been found this error before can help me.
Thank you so much
Nuttaphon(Thailand)Hi
Your question is not clear.. Are you talking about crystal reports results area ? If it is not related to crystal, please mention the tool.
Thanks,
Sastry -
C4180 error:the data area passed to a system call is too small
C4180 Photosmart printer. Loaded official HP driver from the web site for this all in one.
OS is windows 8.1 pro 32bit.
After any print command , in my case a test print the following windows error.
"The data area passed to a system call is too small".
Removed driver and reinstalled, same problem.
Anybody had the same problem, more to the point what is the cause.
Thanks.Hi jongar47,
Welcome to the HP Support Forums! I see when you attempt using a print command with your HP Photosmart C4180 you get a "The data area passed to a system call is too small" error. You have Windows 8.1, you updated the drivers for the PS C4180, and tried uninstalling and reinstalling the driver with no success.
I would like you to run the HP Print and Scan Doctor- It was designed by HP to provide users with the troubleshooting and problem solving features needed to resolve many common problems experienced with HP print and scan products connected to Windows-based computers.
Does the PSDR find any problems with the software and drivers, any conflicts?
Please let me know the outcome, I will watch for your reply.
Thank you,
HevnLgh
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping! -
The Data Area Passed to a System Call Is Too Small
Getting this error on my Vista 64bit system. Did not have this eror with previous version of net Magic. Now running 5.5.9195.0-Pure0.
Any suggestions on how to reolve this?
JohnWow! I think you are definitely on to something
there. I switched my returns to long instead of int
and now it works about 99.5% of the time. That is the
only thing I changed and I have MUCH improvement! But
still there is something just not quite right. Can
you think of anything else along these lines that
might help?Changing to a long moves things around in memory. And if you have a memory problem (nothing to do with the type) moving things in memory can alter the behavior. -
Error - "The data area passed to a system call is too small"
When I will add the invoice, this error raise in the GetLastErrorDescription of company object... What it's wrong with my code ?
Dim sComp As New SAP.Company
With sComp
.Server = "(local)"
.CompanyDB = "SBODemo_Brazil"
.UserName = "manager"
.Password = "manager"
If .Connect <> 0 Then
MsgBox(.GetLastErrorDescription)
Me.Close()
End If
End With
Dim sPedi As SAP.Documents
sPedi = sComp.GetBusinessObject(SAP.BoObjectTypes.oInvoices)
sPedi.CardCode = "GUI"
sPedi.CardName = "f"
sPedi.DocDueDate = Now
sPedi.Lines.ItemCode = "1"
sPedi.Lines.Quantity = 3
sPedi.Lines.Usage = "3"
sPedi.Lines.Add()
sPedi.Lines.ItemCode = "2"
sPedi.Lines.Quantity = 3
sPedi.Lines.Usage = "3"
sPedi.DocTotal = 60
If sPedi.Add() <> 0 Then
MsgBox(sComp.GetLastErrorDescription)
End IfHi all,
I'm currently getting the same error when trying to add an Incoming Payment... I don't see where the error could be, it works fine on cash, but not on credit cards...
Dim sap_pay As SAPbobsCOM.Payments
sap_pay = vCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oIncomingPayments)
sap_pay.CardCode = cliente
sap_pay.Invoices.DocEntry = sap_key
sap_pay.DocDate = Now.Date
If CashTotal > 0 Then
sap_pay.CashAccount = CashAcc
sap_pay.CashSum = CashTotal
End If
If CardTotal > 0 Then
used_cards += 1
sap_pay.CreditCards.CreditType = SAPbobsCOM.BoRcptCredTypes.cr_Regular
sap_pay.CreditCards.CreditCard = 1
sap_pay.CreditCards.PaymentMethodCode = 1
sap_pay.CreditCards.CreditCardNumber = "0000000000000000"
sap_pay.CreditCards.CardValidUntil = DateTime.Now.AddYears(1)
sap_pay.CreditCards.VoucherNum = used_cards
sap_pay.CreditCards.CreditSum = CardTotal
sap_pay.CreditCards.CreditAcct = CardAcc
sap_pay.CreditCards.Add()
End If
If AmexTotal > 0 Then
used_cards += 1
sap_pay.CreditCards.CreditType = SAPbobsCOM.BoRcptCredTypes.cr_Regular
sap_pay.CreditCards.CreditCard = 1
sap_pay.CreditCards.PaymentMethodCode = 1
sap_pay.CreditCards.CreditCardNumber = "0000000000000000"
sap_pay.CreditCards.CardValidUntil = DateTime.Now.AddYears(1)
sap_pay.CreditCards.VoucherNum = used_cards
sap_pay.CreditCards.CreditSum = AmexTotal
sap_pay.CreditCards.CreditAcct = AmexAcc
sap_pay.CreditCards.Add()
used_cards += 1
End If
Dim sap_inv As SAPbobsCOM.Documents
sap_inv = vCompany.GetBusinessObject(SAPbobsCOM.BoObjectTypes.oInvoices)
sap_inv.GetByKey(sap_key)
suma_aplicada = sap_inv.DocTotal
sap_pay.Invoices.SumApplied = suma_aplicada ' CashTotal + CardTotal + AmexTotal
IRetCode = sap_pay.Add()
I hope someone can help me...
Thanks !
Alfredo Pérez
www.corponet.com.mx
SAP Developer & Consultant
alperal (at) gmail.com
+52-(81)-137-937-80 -
Exchange 2007 SP3 Install on 2008R2 Fails with "The data passed to a system call is too small"
I'm installing Exchange 2007 SP3 onto Server 2008 R2. I have run this install in compatibility mode and in normal install mode with the same results. Error code 3221684346: The data area passed to a system call is too small. I am installing directly from
the SP3 files, this is not an upgrade. What do I have to do to get this to work?
[2/15/2011 7:24:18 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[2/15/2011 7:24:18 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Processing file 'C:\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Registry file name: 'C:\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[2/15/2011 7:24:18 AM] [2] Filename = 'C:\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[2/15/2011 7:24:18 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[2/15/2011 7:24:18 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[2/15/2011 7:24:18 AM] [2] Leaving ScSetupAtom
[2/15/2011 7:24:18 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] The following 1 error(s) occurred during task execution:
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[2/15/2011 7:24:18 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[2/15/2011 7:24:18 AM] [1] Finished executing component tasks.
[2/15/2011 7:24:18 AM] [1] Ending processing.
[2/15/2011 7:42:08 AM] [0] End of Setup
[2/15/2011 7:42:08 AM] [0] **********************************************I would probably rebuild the host machine. The Exchange installation should occur without any issues, and where a problem does occur that can be an indication of a more widespread problem. Rebuild the machine, reinstall the prerequisites and try again.
Simon.
Simon Butler, Exchange MVP
Blog |
Exchange Resources | In the UK?
Hire Me.
Hello Poster.
I am having the same issue, however it is most likely NOT a host box problem. The above advice is not a fix. I have 3 servers that are cloned with the same setup. 2 were fixed by doing the Vista compatibility trick, this one gave a different error (which
happened to be the same as above). This org was a 5.5 to 2000. to 2003 coexistence with 2007 currently(because the mailbox role won't install). It has something to do with AD or permissions. Server 2008 r2 inherently has problems installing exchange.
Example, having to use vista compatibility to get the mailbox role to install. SP2 patch gives the same error to some people, and also doesn't upgrade the mailbox role properly in some cases. Some people have had luck restarting the IIS admin service, but
that did not solve my copy of this error. I will repost here if I find a solution to this issue...
Same exact setup log for me as well.
[3/4/2011 10:45:51 AM] [2] Interpreting line <OpenMachineKey:SYSTEM\CurrentControlSet\Services> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] Interpreting line <CreateSecureKey:MSExchangeIS\ParametersPrivate> -- ID:31259 --
[3/4/2011 10:45:51 AM] [2] CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:1199)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Processing file 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins', at or near line 77 (CreateSecureKey:MSExchangeIS\ParametersPrivate) -- ID:31111 -- CInsParser::ScProcessLine (f:\08.03.0083\sources\dev\admin\src\libs\exsetup\hiddenw1.cxx:488)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Registry file name: 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg.ins' CRegistryManager::ScProcessFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\tools\regmgr.cxx:125)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScRunRegistryFile (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1379)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScRunRegistryFile
[3/4/2011 10:45:51 AM] [2] Filename = 'C:\Program Files\Microsoft\Exchange Server\Setup\data\mdb_reg' CBaseAtom::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:1249)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CAtomBaseMDB::ScAddRegistryKeys (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\components\server\a_basemdb.cxx:132)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CAtomBaseMDB::ScAddRegistryKeys
[3/4/2011 10:45:51 AM] [2] CBaseAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:639)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] Service = 'MSExchangeIS' CBaseServiceAtom::ScAdd (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\basesvcatom.cxx:203)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving CBaseServiceAtom(Information Store Service)::ScAdd
[3/4/2011 10:45:51 AM] [2] mode = 'Install' (61953) CBaseAtom::ScSetup (f:\08.03.0083\sources\dev\admin\src\udog\setupbase\basecomp\baseatom.cxx:535)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] ScSetupAtom (f:\08.03.0083\sources\dev\admin\src\udog\exsetdata\exsetds.cxx:897)
Error code 0XC007007A (122): The data area passed to a system call is too small.
[3/4/2011 10:45:51 AM] [2] Leaving ScSetupAtom
[3/4/2011 10:45:51 AM] [2] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] The following 1 error(s) occurred during task execution:
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] 0. ErrorRecord: Microsoft.Exchange.Management.Deployment.ExsetdataException: An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] [ERROR] An error occurred. The error code was 3221684346. The message was The data area passed to a system call is too small..
[3/4/2011 10:45:51 AM] [1] Setup is halting task execution because of one or more errors in a critical task.
[3/4/2011 10:45:51 AM] [1] Finished executing component tasks.
[3/4/2011 10:45:51 AM] [1] Ending processing.
Just curious though, how long is your FQDN? Mine is 34 characters plus whatever exchange is adding to it during setup for this particular string. I found a post with the same error for ISA server and some buffer is only 100 characters for a system call.
ERROR_INSUFFICIENT_BUFFER 122 (0x7A) The data area passed to a system call is too small. http://msdn.microsoft.com/en-us/library/ms681382(v=vs.85).aspx Indicates a msft programming problem.
Outsource Technology Inc. MSFT Professional Consultant -
What are the major process to transfer the data from legacy to sap system.
What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?
hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null -
When we are able to see the data in Tcode RSA3(Source system)
Hi,
Please help me!
In enhancement after doing the R/3 stuff, when we are able to see the data in Tcode RSA3 in R/3 only?
Give the detail for all types of data source and for all types of loads.
eg: Std data source for deltaload, Generic data source for full load.....etc...
Regards,
Shiva.Sure...
I am doing enhancement for datasource '2LIS_05_QVUDN'.
I complited the R/3 stuff and check the data for enhanced fields in RSA3...it's giving run timeout run time error.
Then I just ignore that error and I complited BW stuff successfully....after compliting BW stuff I am able to see the data in RSA3 in R/3.
So my question is, What is the root cause for this....?
When we are able to see the data in RSA3 in source system.?
please give me details for all types of datasource and all types of loads so that it will helps a lot for me in future. -
Error while extracting the data in R/3 production system,
Hi Team,
We got the following error while extracting the data in R/3 production system,
Error 7 When Sending an IDoc R3 3
No Storage space available for extending the inter 44 R3 299
No storage space available for extending the inter R3 299
Error in Source System RSM 340
Please guide us to fix the issueIt´s very difficult to help you without knowing
- what is going to be transferred
- where you get this error
- system configuration
- actual memory usage
- operating system
- database and configuration etc. etc.etc. etc.
I suggest you open an OSS call and let the support have a look on your system. It´s much easier if one has system access to find out the cause for that problem.
Markus -
I want to give away or sell a 6500/250 running 7.6.1. How can the hard disk be erased so that the data are gone, not recoverable? thanks, LifeisRich
I'd recommend that you check for Mac User Group(s) in Orange County. That's where you'd likely find a diehard Mac fanatic who might want to add your 6500 to his/her collection. Even if you got nothing for it, it would be better than e-cycling it. I upgraded my 6500/275 with what was a "large" hard drive at the time (15 GBs), maxed the memory at 128 MBs, installed the 512K L2 cache card, a better ATI Rage Pro PCI graphics card, a USB PCI card, and an internal 56K modem. With it running OS 9.1, it did all of the pre-OS X stuff I needed it to do. As I previously mentioned, it's a nice-sounding MP3 player. Internet Explorer 5.1.7 (the final release from 2001) kept it useful for surfing the web up until 2005, when it became too outdated/incompatible with many web sites. Unfortunately, the demands of the internet and the need for a modern browser, as well as faster processing to digest it all, are what retired many older Macs from active duty. So my (2) 6500s and (3) 6400s (same tower design) sit in storage. There is one concern that I'll pass along: The motherboard has a 4.5-volt alkaline battery, that's a small, black plastic cube, secured in place by velcro. If your 6500 has been disconnected from electricity for a long time, the battery will undoubtedly be dead. Unlike the many Apple computers that used a small ½AA lithium battery (that I've never seen leak when completely dead), the 6500's battery can and usually does start leaking. Because the motherboard sits vertically oriented on its side edge when installed, the leaking battery will drip alkaline solution down the board, corroding any components in it path. I've seen motherboards ruined from this. If you're going to give it away or sell it, you might want to pull the motherboard (remove the two machine screws on the rear I/O panel, next to the pull tabs). Slide out the board and unplug the battery's small connector (has red & black wires), then lift up on the battery, while holding down the "toothed" velcro mount with something non-conductive, like a popsicle stick. Once it's free, dispose of the battery. If you're interested, a replacement can be purchased for about $5-$7 from battery specialty retailers - it's a Rayovac 870 or 871. Even if you don't replace it, removing one that will eventually leak is a good idea, (hopefully) before any damage is done.
-
Process the result so that the dates are ordered by date
I am retrieving a query result from a sql database of which
one column contains a string of this format:
09/08/2008
How can I process this result so that the dates are ordered
by date?
Thanks for anu help :)what's your db and version?
pretty much all dbs have built-in string and date functions,
a
combinations of which will let you update your field to be
date/datetime.
you will probably want to create a new field in the table to
store the
converted dates, then check that they all have been converted
correctly,
then delete the current date field and rename the new field
to the old
date field's name.
using your db's string functions you will need to extract
day, month and
year parts of your date text, and pass them to your db's date
creation
function.
if your db is MySQL, it has a very handy STR_TO_DATE(str,
format)
function... check details in mysql ref manual.
Azadi Saryev
Sabai-dee.com
http://www.sabai-dee.com/ -
Why does my mac mini's mouse show a pinwheel every time I hover over the date area? Also, sometimes the date/time shows up incorrectly. It started happening after I updated to OS X Mountain Lion.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Click the Clear Display icon in the toolbar. Try the action that you're having trouble with again. Post any messages that appear in the Console window – the text, please, not a screenshot.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into a message.
Important: Some private information, such as your name, may appear in the log. Edit it out by search-and-replace in a text editor before posting. -
IPhoto imports photos with wrong dates even if the dates are fine on the camera
Hi!
When I import photos with iPhoto, sometimes it imports them with wrong dates, even the dates are fine on the camera. It puts dates such as 2032. Does anyone know how can I fix that. As far as I know there is no way to change dates of the photos.
Thanks!well that is very confusing since if the date is correct on the camera it will be correct in iPhoto
and as to
As far as I know there is no way to change dates of the photos.
Try looking through your iPhto menus - two commands - adjust time and date and batch change time and date - asjust is used to correct incorrect dates like a comera setting - Batch change for missing dates like with scans
LN
Maybe you are looking for
-
Adobe Photoshop CS6 won't run, problem with Application Manager
I've now got three Adobo Photoshop CS products on my MacBook Pro, the latest is CS6 which won't run. I own Photoshop CS3, I just happen to install the CS5.x suite today, which runs during the trial period (30 day, today is day #1). I then see that PS
-
PO Print when mark a Delete option for a Line Item
Hi Friends, I am in a Fix, I have changed a PO line item by giving a header text and then Marked the line item as deleted, when I tried to take a PO Print It does not show me the Header text, Please help me out with problem.
-
I was wondering which of you are using the new html 5 specifications, beginning with the doctype declaration. The implementation of video appears to be a major pain, having to specify different file types for different browsers. Am not at all sure ho
-
Using OBI answers report as source in BIP report
All, I am creating a BIP report using OBI answers request as source. I defined the data set, created RTF template from MS word and uploaded the same into BIP. I am using dashboard prompts for this reports. I have 2 issues with this. 1. When I embed t
-
How do I delete or clear my browsing history?
I can't clear my history is there a simple way to do this?