What does the registration process expect as my screen name?

What does the registration process expect as my screen name?
i used
BILL-PC
WKYBURZ
[ email address removed by admin ]
nothing works
my conclusion : it is a bug

Trevor,
it worked
it seems that if you make a mistake the first time around .. it goes into
some strange buggy loop
doing it from scratch worked
remember that
thanks again
Bill Kyburz

Similar Messages

What does the green tick mean next to contact name

PLease what does the green tick mean next to contact name ...

In what app are you seeing a green tick next to a contact name?
In many messaging apps, that means the contact is online/available.

What does the upgrade process look like? Black screen after a few minutes o

Hello,
I just received a new Macbook Pro. I turned it on for the very first time, entered in my name and password, etc. Then I inserted the SL upgrade diskd circular arrow, then black screen again.. It started up, I acknowledged the license agreement, it said it would take 56 minutes to install. So I walked away. Came back ten minutes later to a blank screen. It would not respond to swipe or click, i.e. no wake-up. After a few more minutes the computer seemed dark, cold, silent. Holding down the power button finally started it back up.
Disk spun, Apple log and spinning arrow, then blank screen again. I was finally able to eject the upgrade disk. I had to re-install Leopard and parts of iLife.
So what is a normal looking upgrade? Should the screen go blank? Did I screw things up with lack of patience?
Any insights appreciated.
Thanks, Joe

donv (The Ghost) wrote:
The screen should not go black.
Actually, this is normal for the default installation method (IOW, not starting by running from the DVD). The installer will first run some checks & then transfer a bunch of files to the drive for later use. The screen will be normal while this happens, but eventually the installer will restart the Mac & for a while the screen will be black -- typically less than a minute but sometimes longer. After this, the screen should reappear.
So, it is best to be patient & give the process some time to continue before deciding something is wrong & forcing a shutdown or restart.

What does the "Registration" tab on the Bonjour control panel do?

?

meandpepe
Thanks for stopping by. The users manual in pdf is here
http://h10025.www1.hp.com/ewfrf/wc/manualCategory?cc=us&dlc=en&lc=en&product=75964&task=&
the Star on the top of the camera is sued to change the image quality from Good to Better to Best.
I hope the Users Guide can help you with any additional questions you have.
Jendyruth
Please click the white Kudos star on the left to say "Thanks!"
Clicking "Accept as Solution" on a reply that solves your issue makes it easier for other people to find solutions.
I work on behalf of HP.

HT201328 Why do Orange and EE blame Apple for the delays in unlocking my iPhone. 10 months now. What is the exact process that these companies have to go through to unlock an iPhone and is Apple in any way to blame for the delays. Indeed how long does Ap

Why do Orange and EE blame Apple for the delays in unlocking my iPhone. 10 months now. What is the exact process that these companies have to go through to unlock an iPhone and is Apple in any way to blame for the delays.
Indeed how long does Apple take to carry out its part of the process.
It seems to me that Orange are just trying to stall me despite the fact that I am out of contract with them now. I originally paid to have the phone unlocked back last November. This was never done.
I have phoned them numerous times over the last two months but still they haven't done it. Can anyone advise me and has anyone had similar problems with them.
Thanks

I certainly understand that only Orange can unlock my phone. My annoyance is that they blame Apple so I am keen to know what exactly is Apple's involvement.
I presume that Orange have to tell Apple that the phone has been authorised for unlocking by Orange and that Apple then notes that in some way on iTunes so that the user can then complete the process on iTunes.
What I would like to know is how much time Apples part in this process takes.
I would also like to make contact with others who have had similar problems.
Many thanks

What does the location of the peak detector mean

i would like to know what the locations of the peak detector refer to? what does the value of the location of the peak detector tell? does it tell the location of the peak and if so, what unit is it in? also, if i set a threshold value, does it mean that only one peak would be detected or any value higher than that threshold would also be detected? if i were to set the sampling rate for my peak detection to be 400 per millisecond, do i expect to see an array of values or one absolute peak value after one cycle?

Greetings!
The peak value VI gives you four outputs, actually: positive and negative peak values and the positive and negative peak "horizontal" locations. The locations are in data points, not actual time. To get the time, you have to calculate it from your sample rate. Also, the vi does indeed give you the absolute peak of a waveform, which, as you can guess, requires that the entire waveform is sampled BEFORE the calculation is made. This can slow down real-time sampling, since there is considerable processing involved in calculating the peak value...you need to keep this in mind when designing your application. To answer your last question, you will obtain ONE reading per trigger.
Hope this helps!
Eric
Eric P. Nichols
P.O. Box 56235
North Pole, AK 99705

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

What does the top level instance name "iop" mean?

What does the top level instance name "iop" mean?

Dear Humility,
In general term higher level account group means which account group is used to the higher level customers in the Customer Hierarchy process.
Or
Which of these account groups are valid for higher-level customers in the hierarchy.
I hope this will help you,
Regards,
Murali.

What does the standard program RFBIBL00    does?

what does the standard program RFBIBL00    does?

Hi Bharath
Accounting Documents: Data Transfer Workbench
Definition
Transferring FI accounting documents from an external system into the SAP System using program RFBIBL00.
Use
You use program RFBIBL00 to enter accounting documents and to clear open items.
Method
Program RFBIBL00 primarily transfers accounting documents using the batch input method. However, you can also generate documents immediately using call transaction or direct input by means of the "Data transfer type" parameter. Both of these procedures lead to improvements in system performance when transferring large quantities of data (more than 10,000 transactions).
Object-Specific Settings
With call transaction or direct input, documents are posted immediately to the SAP System. As a result, you need to ensure that if for any reason the program is terminated, it can be restarted without inconsistencies occurring in the data.
other information:
To enhance the batch input procedure, the system offers the direct input technique, especially for transferring large amounts of data. In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not process screens. 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. To maintain and start these programs, use program RBMVSHOW or Transaction BMV0.
Examples for direct input programs are:
Program        Application
RFBIBL00         FI
RMDATIND       MM
RVAFSS00       SD
RAALTD11        AM
RKEVEXT0       CO-PA
Hope this helps u
thanks and regards
suma sailaja pvn

TRFC internals - how does the async processing happen?

tRFC internals - how does the async processing happen?
Dear all,
With the document "[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694]" there is an excellent place to read about SAP RFCs (remote function calls).
Pages 94 to 96 describe in detail how tFRC (transactional RFC) works.
However, there is still something unclear for me with the following sentence on page 94:
"The truly exciting part happens when the program
issues a COMMIT WORK command. The recorded calls
are executed asynchronously in a special set of tRFC
processing sessions created for each transaction ID..."
Maybe someone can answer the following questions:
a) what does exactly trigger and execute the tRFC?
b) is it the ABAP runtime system itself, spawning the additional task in DIA?
c) if multiple tRFC LUWs have been recorded, they are all executed in parallel by this procedure!?
d) does the execution try to utilize all available DIA processes?
e) how do the rdisp/rfc_... parameter come into the game?
   are they evaluated? We have seen all DIA occupied by the tRFCs executed!
Best regards,
Peter
P.S.: if someone has answers to these ones, more related to error handling, would be great as well
f) the jobs ARFC*, do they also use parallel processing?
   or is every ARFC* job responsible only for one single LUW?
   (note https://service.sap.com/sap/support/notes/366807 did not give a perfect answer)
g) and how does the report RSARFCEX work compared to immediate execution?

That's the problem, it won't.
internal static string GetAvailabilityGroupFromConnection(SPDatabase db)
if (!UsesAvailabilityConnection(db))
return null;
string dataSource = db.ConnectionString.DataSource;
string cmdText = string.Format(CultureInfo.InvariantCulture, "\r\n SELECT name FROM sys.availability_groups g\r\n JOIN sys.availability_group_listeners l ON g.group_id = l.group_id\r\n WHERE dns_name = '{0}'\r\n ", new object[] { dataSource });
string str3 = null;
using (SqlCommand command = new SqlCommand(cmdText))
ULS.SendTraceTag(0x302263, ULSCat.msoulscat_WSS_Database, ULSTraceLevel.Medium, "Looking up availability group for listener: {0}", new object[] { cmdText });
using (SqlDataReader reader = GetSessionFromDatabase(db).ExecuteReader(command))
while (reader.Read())
str3 = reader.GetString(0);
ULS.SendTraceTag(0x302280, ULSCat.msoulscat_WSS_Database, ULSTraceLevel.Medium, "Found group {0} for listener {1}", new object[] { str3, dataSource });
This piece of code looks at the SPDatabase's connection string (the SQL alias, for example) and executes a T-SQL query looking for that name within SQL Server. Since the SQL alias does not exist within the SQL Server's configuration, it will return a null
value, and you won't be able to set up the AG config using the AG cmdlets.
Also, since mobility exists by the very nature of using an AG Listener, using a SQL Alias is redundant.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

What does the i mean in Apple products.

What does the i in Apple products, (iPod, iSight,iMac etc), signify?
Im sure this should be in a FAQ but I couldnt find it anywhere. As there is no "General area", I hope its OK to ask this here.
Thanks
Victor
Mac Pro Mac OS X (10.4.8) 6Gb Bluetooth and Airport upgrade

Thanks Jeff.
I had expected it was a bit more interesting!
Victor

How does the sync process work?

Hello all,
I want to know what will happen if both the local and network homes have been modified for a period of two weeks and then the user chooses to synch? Will the sync process ask which 'home' is the most recent or will it replace older files with newer files?
How does the sync process manage the task of keeping both sides the same?
Thanks,
-Andrew G

If a file exists on both the local and the network directory it will pop up with a conflict and ask how to resolve it.
If the file is only on the local machine and in a place you have not excluded from syncing it just syncs.
If the file has been previously synced but there has been no change to the file since last sync I think it just rewrites the file to the server homedir... (Don't quote me on this one... it might not even bother with it, I'm not sure how smart the sync service is)
You can set automatic conflict resolution within WGM but as far as I know you have to do it by clicking on preferences then switching to the details tab, then click on Home Sync....com.apple.homesync. Click on the Always drop down and click the add new key button then change the new key to either Login or Logout Non-Preference sync conflict resolution and or Background sync conflict resolution and decide if MobileHome or NetworkHome Wins...or copy. In most cases I would think that you would want the MobileHome to Win.. of course there is always potential for someone to make a huge mistake on a file and pray its still fine on the server but... your call.

After i register my imac it just goes back to the very beginning of the registration process

I lost my password and when thru the process of the whole rm var/db/.applesetupdone thing to reset my admin password. it takes me thru the registration process but when it gets to the end it just starts over completely at the beginning of the registration process. does anyone have an suggestions?

Boot up in single user mode. See if /var/db/.applesetupdone exists.
The name is:
-rw-------
1 root
wheel
1K Dec 13 2010 .AppleSetupDone
If not create one:
mac $ pwd
/var/db
mac $ sudo cat .AppleSetupDone
Password:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
        <key>Address</key>
        <dict>
                <key>AreaCode</key>
                <string>111</string>
                <key>City</key>
                <string>burg</string>
                <key>Company</key>
                <string></string>
                <key>CountryName</key>
                <string>United States</string>
                <key>ExistingEmailAddress</key>
                <string></string>
                <key>FirstName</key>
                <string>Robert</string>
                <key>LastName</key>
                <string>Last</string>
                <key>LocalPhoneNumber</key>
                <string>111111</string>
                <key>StateProv</key>
                <string>St</string>
                <key>StreetAddr1</key>
                <string>111 S Street</string>
                <key>StreetAddr2</key>
                <string></string>
                <key>ZipPostal</key>
                <string>11111</string>
        </dict>
        <key>RegistrationInfo</key>
        <dict>
                <key>AppleSpam</key>
                <string>NO</string>
                <key>Location</key>
                <string>B</string>
                <key>Occupation</key>
                <string>13</string>
                <key>OthersSpam</key>
                <string>NO</string>
        </dict>
</dict>
</plist>
mac $

I have an IPad2. I've received two different ideas on charging the battery. One person indicates I should let the battery run almost down before recharging; another person indicated I should keep it charged closer to 100% . What is the best process?

I have an IPad2. I've received two different ideas on charging the battery. One person indicates I should let the battery run almost down before recharging; another person indicated I should keep it charged closer to 100% . What is the best process for the best battery life over time?

I do exactly as Thomas Reed does. Always have from day one. Going on 15 months now and I get at least 10 hours of use out the battery every day. No matter how much juice is left on the device when I go to bed - I put the iPad on the charger - doesn't matter what the battery gauge says - I plug it in and let it charge all night.

What Does The Log Message "Rejecting update: Lease..." Mean?

I use RelicatedCache and TransactionMap on Coherence 3.4.2.
I saw "Rejecting update: Lease..." message.
What does the log message mean?
2011/10/18 06:41:57.506 [DEBUG] Logger@9263394 3.4.2/411p16 N/A NOAH Coherence 3.4.2/411p16 [D4] (thread=ReplicatedCache, member=2): Rejecting update: Lease: [-8863526970089418959, -2793231267399579492, R] (Cache=issue-code, Size=Unknown, Version=0/0, IssuerId=1, HolderId=0, Status=LEASE_AVAILABLE, Last locked at Thu Jan 01 09:00:00 JST 1970)
by member=2, Lease: [-8863526970089418959, -2793231267399579492, R] (Cache=issue-code, Size=143, Version=0/0, IssuerId=2, HolderId=0, Status=LEASE_AVAILABLE, Last locked at Tue Oct 18 06:41:51 JST 2011)
I found a Note 1065352.1, but the message is little differnt...
Note 1065352.1
"What Does The Log Message "Rejected update: Lease..." Mean?"I'd like to know following 2 points..
- What does "Rejecting update: Lease..." message mean?
Do thsese messages have same meaning?
- My application didn't catch any exceptions, and
"CacheFactory.commitTransactionCollection" returned true.
So this "Rejecting update: Lease..." is not a error message, right?
(Does the transaction commited successfully?)
Thanks in advance.
-Noriyuki

Hi
These are decoded results of the error message which u have recd in ur box..
%C4K_PKTPROCESSING-4-ERRORPACKET: [char]
The software is unable to process a packet; the packets have been forwarded to the CPU instead and the packet will be dropped.
Recommended Action: This is an informational message only. No action is required.
%C4K_HWACLMAN-4-WARNINGSTRING: [char]
A nonspecific warning message was displayed.
Recommended Action: See the message string [char] for more information.
Related documents- No specific documents apply to this error message
%C4K_HWACLMAN-4-WARNINGSTRING: [char]
A nonspecific warning message was displayed.
Recommended Action: See the message string [char] for more information.
Related documents- No specific documents apply to this error message.
regds

What does the registration process expect as my screen name?

Similar Messages

Maybe you are looking for